<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-bgp-ls-segment-routing-ext" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-segment-routing-ext-12">
   <front>
      <title>BGP Link-State extensions for Segment Routing</title>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="H." surname="Gredler" fullname="Hannes Gredler">
         <organization>RtBrick Inc.</organization>
      </author>
      <author initials="M." surname="Chen" fullname="Mach Chen">
         <organization>Huawei Technologies</organization>
      </author>
      <date month="March" day="8" year="2019" />
      <abstract>
	 <t>   Segment Routing (SR) allows for a flexible definition of end-to-end
   paths by encoding paths as sequences of topological sub-paths, called
   &quot;segments&quot;.  These segments are advertised by routing protocols e.g.
   by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within
   IGP topologies.

   This draft defines extensions to the BGP Link-state address-family in
   order to carry segment routing information via BGP.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-ls-segment-routing-ext-12" />
   
</reference>
