--- 1/draft-ietf-idr-bgp-flowspec-oid-01.txt 2014-01-17 11:14:35.133743145 -0800 +++ 2/draft-ietf-idr-bgp-flowspec-oid-02.txt 2014-01-17 11:14:35.157743756 -0800 @@ -1,20 +1,22 @@ Network Working Group James Uttaro Internet Draft AT&T Updates: 5575 Clarence Filsfils -Intended Status: Proposed Standard Pradosh Mohapatra -Expiration Date: July 2013 David Smith +Intended Status: Proposed Standard David Smith +Expiration Date: July 31, 2014 Juan Alcaide Cisco - January 22, 2013 + Pradosh Mohapatra + Cumulus Networks + January 17, 2014 Revised Validation Procedure for BGP Flow Specifications - draft-ietf-idr-bgp-flowspec-oid-01 + draft-ietf-idr-bgp-flowspec-oid-02 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 @@ -32,47 +34,46 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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 1, 2013. + This Internet-Draft will expire on July 31, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + Copyright (c) 2014 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 described in the Simplified BSD License. Table of Contents - 1 Specification of Requirements ...................... 2 + 1 Specification of Requirements ...................... 3 2 Motivation ......................................... 3 3 Introduction ....................................... 5 4 Revised Validation Procedure ....................... 6 5 Security Considerations ............................ 7 6 IANA Considerations ................................ 7 7 Normative References ............................... 7 8 Acknowledgements ................................... 8 9 Authors' Addresses ................................. 8 1. Specification of Requirements @@ -302,31 +304,39 @@ 9. Authors' Addresses James Uttaro AT&T 200 S. Laurel Avenue Middletown, NJ 07748 USA Email: ju1738@att.com + Juan Alcaide + Cisco + 7100 Kit Creek Road + Research Triangle Park, NC 27709 + USA + + Email: jalcaide@cisco.com + Clarence Filsfils Cisco Brussels 1000 BE Email: cf@cisco.com - - Pradosh Mohapatra - Cisco - 170 W. Tasman Drive - San Jose, CA 95134 - USA - - Email: pmohapat@cisco.com - David J. Smith + David Smith Cisco 111 Wood Avenue South Iselin, NJ 08830 USA - E-mail: djsmith@cisco.com + Email: djsmith@cisco.com + + Pradosh Mohapatra + Cumulus Networks + 185 E. Dana Street + Mountain View, CA 94041 + USA + + Email: mpradosh@yahoo.com