<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-bgp-ls-segment-routing-msd" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-segment-routing-msd-18">
   <front>
      <title>Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State</title>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Apstra, Inc.</organization>
      </author>
      <author initials="U." surname="Chunduri" fullname="Uma Chunduri">
         <organization>Futurewei Technologies</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="G." surname="Mirsky" fullname="Greg Mirsky">
         <organization>ZTE Corp.</organization>
      </author>
      <author initials="N." surname="Triantafillis" fullname="Nikos Triantafillis">
         <organization>Amazon Web Services</organization>
      </author>
      <date month="May" day="8" year="2020" />
      <abstract>
	 <t>This document defines a way for a Border Gateway Protocol - Link
State (BGP-LS) speaker 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-ls-segment-routing-msd-18" />
   
</reference>
