<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ospf-segment-routing-msd" target="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-segment-routing-msd-25">
   <front>
      <title>Signaling Maximum SID Depth (MSD) Using OSPF</title>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Apstra, Inc.</organization>
      </author>
      <author initials="U." surname="Chunduri" fullname="Uma Chunduri">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="S." surname="Aldrin" fullname="Sam Aldrin">
         <organization>Google, Inc</organization>
      </author>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         <organization>Cisco Systems</organization>
      </author>
      <date month="October" day="18" year="2018" />
      <abstract>
	 <t>This document defines a way for an Open Shortest Path First (OSPF) router to advertise multiple types of supported Maximum SID Depths (MSDs) at node and/or link granularity.  Such advertisements allow entities (e.g., centralized controllers) to determine whether a particular Segment Identifier (SID) stack can be supported in a given network.  This document only refers to the Signaling MSD as defined in RFC 8491, but it defines an encoding that can support other MSD types.  Here, the term &quot;OSPF&quot; means both OSPFv2 and OSPFv3.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ospf-segment-routing-msd-25" />
   
</reference>
