--- 1/draft-ietf-idr-bgp-flowspec-oid-02.txt 2016-03-21 09:17:30.970843064 -0700 +++ 2/draft-ietf-idr-bgp-flowspec-oid-03.txt 2016-03-21 09:17:30.998843762 -0700 @@ -1,22 +1,22 @@ Network Working Group James Uttaro Internet Draft AT&T Updates: 5575 Clarence Filsfils Intended Status: Proposed Standard David Smith -Expiration Date: July 31, 2014 Juan Alcaide +Expiration Date: September 21, 2016 Juan Alcaide Cisco Pradosh Mohapatra - Cumulus Networks - January 17, 2014 + Sproute Networks + March 21, 2016 Revised Validation Procedure for BGP Flow Specifications - draft-ietf-idr-bgp-flowspec-oid-02 + draft-ietf-idr-bgp-flowspec-oid-03 Abstract This document describes a modification to the validation procedure defined in RFC 5575 for the dissemination of BGP flow specifications. RFC 5575 requires that the originator of the flow specification matches the originator of the best-match unicast route for the destination prefix embedded in the flow specification. This allows only BGP speakers within the data forwarding path (such as autonomous system border routers) to originate BGP flow specifications. Though @@ -40,25 +40,25 @@ Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on July 31, 2014. + This Internet-Draft will expire on September 21, 2016. Copyright Notice - Copyright (c) 2014 IETF Trust and the persons identified as the + Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -275,21 +275,21 @@ 6. IANA Considerations This document has no actions for IANA. 7. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4271] Rekhter, Y., Li, T., and Hares, S., "A Border Gateway - Protocol 4 (BGP-4)", RFC 4271, January 2006. + Protocol 4 (BGP-4)", RFC 4271, March 2006. [RFC4456] Bates, T., Chen, E., and Chandra, R., "BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)", RFC 4456, April 2006. [RFC5065] Traina, P., McPherson, D., and Scudder, J., "Autonomous System Confederations for BGP", August 2007. [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., and McPherson, D., "Dissemination of Flow Specification Rules", RFC @@ -327,16 +327,13 @@ Email: cf@cisco.com David Smith Cisco 111 Wood Avenue South Iselin, NJ 08830 USA Email: djsmith@cisco.com Pradosh Mohapatra - Cumulus Networks - 185 E. Dana Street - Mountain View, CA 94041 - USA + Sproute Networks Email: mpradosh@yahoo.com