RFC 8491: Signaling Maximum SID Depth (MSD) Using IS-IS
In plain English — editorial summary, not part of the RFC
This document defines a way for an Intermediate System to Intermediate System (IS-IS) 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 ID (SID) stack can be supported in a given network. This document only defines one type of MSD: Base MPLS Imposition. However, it defines an encoding that can support other MSD types. This document focuses on MSD use in a network that is Segment Routing (SR) enabled, but MSD may also be useful when SR is not enabled.
Document record
- Document ID
- RFC8491
- Published
- November 2018
- Authors
- J. Tantsura; U. Chunduri; S. Aldrin; L. Ginsberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8476Signaling Maximum SID Depth (MSD) Using OSPFCurrent
December 2018
- RFC 8814Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link StateCurrent
August 2020
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 8667IS-IS Extensions for Segment RoutingCurrent
December 2019
- RFC 9247BGP - Link State (BGP-LS) Extensions for Seamless Bidirectional Forwarding Detection (S-BFD)Current
June 2022
- RFC 9294Application-Specific Link Attributes Advertisement Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2022
- RFC 9351Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm AdvertisementCurrent
February 2023
- RFC 9703Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data PlaneCurrent
December 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?