<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-bgp-prefix-sid" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-prefix-sid-20">
   <front>
      <title>Segment Routing Prefix SID extensions for BGP</title>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Lindem" fullname="Acee Lindem">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Sreekantiah" fullname="Arjun Sreekantiah">
         </author>
      <author initials="H." surname="Gredler" fullname="Hannes Gredler">
         <organization>RtBrick Inc.</organization>
      </author>
      <date month="May" day="8" year="2018" />
      <abstract>
	 <t>   The Segment Routing (SR) architecture allows a node to steer a packet
   flow through any topological path and service chain by leveraging
   source routing.  The ingress node prepends an SR header to a packet
   containing a set of segment identifiers (SID).  Each SID represents a
   topological or a service-based instruction.  Per-flow state is
   maintained only on the ingress node of the SR domain.  Ah SR domain
   is defined as a single administrative domain for global SID
   assignment.

   This document defines an optional, transitive BGP attribute for
   announcing BGP Prefix Segment Identifiers (BGP Prefix-SID)
   information.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-prefix-sid-20" />
   
</reference>
