<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.djsmith-bgp-flowspec-oid" target="https://datatracker.ietf.org/doc/html/draft-djsmith-bgp-flowspec-oid-01">
   <front>
      <title>Revised Validation Procedure for BGP Flow Specifications</title>
      <author initials="J." surname="Uttaro" fullname="Jim Uttaro">
         <organization>AT&amp;T</organization>
      </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco</organization>
      </author>
      <author initials="P." surname="Mohapatra" fullname="Prodosh Mohapatra">
         <organization>Cisco</organization>
      </author>
      <author initials="D." surname="Smith" fullname="David Smith">
         <organization>Cisco</organization>
      </author>
      <date month="May" day="15" year="2012" />
      <abstract>
	 <t>   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
   it is possible to disseminate such flow specifications directly from
   border routers, it may be operationally cumbersome in an autonomous
   system with a large number of border routers having complex BGP
   policies. The modification proposed herein enables flow
   specifications to be originated from a centralized BGP route
   controller.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-djsmith-bgp-flowspec-oid-01" />
   
</reference>
