--- 1/draft-ietf-idr-bgp-flowspec-oid-00.txt 2013-01-22 16:00:15.687840716 +0100 +++ 2/draft-ietf-idr-bgp-flowspec-oid-01.txt 2013-01-22 16:00:15.703791337 +0100 @@ -1,20 +1,20 @@ Network Working Group James Uttaro Internet Draft AT&T Updates: 5575 Clarence Filsfils Intended Status: Proposed Standard Pradosh Mohapatra -Expiration Date: December 2012 David Smith +Expiration Date: July 2013 David Smith Cisco - June 25, 2012 + January 22, 2013 Revised Validation Procedure for BGP Flow Specifications - draft-ietf-idr-bgp-flowspec-oid-00 + draft-ietf-idr-bgp-flowspec-oid-01 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 @@ -39,25 +39,25 @@ 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 December 1, 2012. + This Internet-Draft will expire on July 1, 2013. Copyright Notice - Copyright (c) 2012 IETF Trust and the persons identified as the + Copyright (c) 2013 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