<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-isis-segment-routing-extensions" target="https://datatracker.ietf.org/doc/html/draft-ietf-isis-segment-routing-extensions-08">
   <front>
      <title>IS-IS Extensions for Segment Routing</title>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         </author>
      <author initials="A." surname="Bashandy" fullname="Ahmed Bashandy">
         </author>
      <author initials="H." surname="Gredler" fullname="Hannes Gredler">
         </author>
      <author initials="S." surname="Litkowski" fullname="Stephane Litkowski">
         </author>
      <author initials="B." surname="Decraene" fullname="Bruno Decraene">
         </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         </author>
      <date month="October" day="13" year="2016" />
      <abstract>
	 <t>   Segment Routing (SR) allows for a flexible definition of end-to-end
   paths within IGP topologies by encoding paths as sequences of
   topological sub-paths, called &quot;segments&quot;.  These segments are
   advertised by the link-state routing protocols (IS-IS and OSPF).

   This draft describes the necessary IS-IS extensions that need to be
   introduced for Segment Routing.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-isis-segment-routing-extensions-08" />
   
</reference>
