Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing Networks
RFC 9716
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2025-02-07
|
(System) | IANA registries were updated to include RFC9716 |
|
2025-02-07
|
(System) | Received changes through RFC Editor sync (created document RFC 9716, created became rfc relationship between draft-ietf-mpls-spring-inter-domain-oam and RFC 9716, set title to 'Mechanisms … Received changes through RFC Editor sync (created document RFC 9716, created became rfc relationship between draft-ietf-mpls-spring-inter-domain-oam and RFC 9716, set title to 'Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing Networks', set abstract to '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 (SR-MPLS) network may consist of multiple IGP domains or multiple Autonomous Systems (ASes) under the control of the same organization. It is useful to have the Label Switched Path (LSP) ping and traceroute procedures when an SR end-to-end path traverses multiple ASes or IGP domains. This document outlines mechanisms to enable efficient LSP ping and traceroute procedures in inter-AS and inter-domain SR-MPLS networks. This is achieved through a straightforward extension to the Operations, Administration, and Maintenance (OAM) protocol, relying solely on data plane forwarding for handling echo replies on transit nodes.', set pages to 22, set standardization level to Proposed Standard, added RFC published event at 2025-02-07) |
|
2025-02-07
|
(System) | RFC published |