[mpls] RFC 9716 on Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing Networks

A new Request for Comments is now available in online RFC libraries.

        RFC 9716

        Title:      Mechanisms for MPLS Ping and Traceroute Procedures
                    in Inter-Domain Segment Routing Networks
        Author:     S. Hegde,
                    K. Arora,
                    M. Srivastava,
                    S. Ninan,
                    N. Kumar
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2025
        Mailbox:    shraddha@juniper.net,
                    kapil.it@gmail.com,
                    msri@juniper.net,
                    samson.cse@gmail.com,
                    nagendrakumar.nainar@gmail.com
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-spring-inter-domain-oam-20.txt

        URL:        https://www.rfc-editor.org/info/rfc9716

        DOI:        10.17487/RFC9716

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.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team