<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ospf-ospfv3-segment-routing-extensions" target="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-ospfv3-segment-routing-extensions-09">
   <front>
      <title>OSPFv3 Extensions for Segment Routing</title>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         </author>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         </author>
      <author initials="H." surname="Gredler" fullname="Hannes Gredler">
         </author>
      <author initials="R." surname="Shakir" fullname="Rob Shakir">
         </author>
      <author initials="W." surname="Henderickx" fullname="Wim Henderickx">
         </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         </author>
      <date month="March" day="8" 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).

   This draft describes the OSPFv3 extensions that are required for
   Segment Routing.


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