RFC 9716: Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing Networks

The Segment Routing (SR) architecture leverages source routing and can be directly applied to the use of an MPLS data plane. A Segment Routing over MPLS…

Read RFC 9716 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 8029: Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
Normative reference — RFC 8287: Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
Normative reference — RFC 7110: Return Path Specified Label Switched Path (LSP) Ping
Informative reference — RFC 3032: MPLS Label Stack Encoding
Informative reference — RFC 8402: Segment Routing Architecture
Informative reference — RFC 9256: Segment Routing Policy Architecture
Informative reference — RFC 8660: Segment Routing with the MPLS Data Plane
Informative reference — RFC 8277: Using BGP to Bind MPLS Labels to Address Prefixes
Informative reference — RFC 9350: IGP Flexible Algorithm
Informative reference — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Informative reference — RFC 9086: Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer Engineering
Informative reference — RFC 8403: A Scalable and Topology-Aware MPLS Data-Plane Monitoring System
Informative reference — RFC 9087: Segment Routing Centralized BGP Egress Peer Engineering
Informative reference — RFC 7743: Relayed Echo Reply Mechanism for Label Switched Path (LSP) Ping
Informative reference — RFC 8604: Interconnecting Millions of Endpoints with Segment Routing