<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.filsfils-spring-sr-recursing-info" target="https://datatracker.ietf.org/doc/html/draft-filsfils-spring-sr-recursing-info-05">
   <front>
      <title>Segment Routing Recursive Information</title>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="L." surname="Ginsberg" fullname="Les Ginsberg">
         <organization>Cisco Systems</organization>
      </author>
      <date month="June" day="20" year="2017" />
      <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).

   There are use cases where it is desirable to utilize a SID associated
   with a given node in order to transport traffic destined to different
   local services supported by such node.  This document defines the
   mechanism to do so and illustrates it.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-filsfils-spring-sr-recursing-info-05" />
   
</reference>
