<?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-27">
   <front>
      <title>Segment Routing Prefix Segment Identifier 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="June" day="26" year="2018" />
      <abstract>
	 <t>Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through an ordered list of instructions called &quot;segments&quot;. A segment can represent any instruction, topological or service based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SIDs). Each SID represents a topological or service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An &quot;SR domain&quot; is defined as a single administrative domain for global SID assignment.

 This document defines an optional, transitive BGP attribute for announcing information about BGP Prefix Segment Identifiers (BGP Prefix-SIDs) and the specification for SR-MPLS SIDs.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-prefix-sid-27" />
   
</reference>
