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

        
        RFC 9884

        Title:      Label Switched Path Ping for 
                    Segment Routing Path Segment Identifier with 
                    MPLS Data Plane 
        Author:     X. Min,
                    S. Peng,
                    L. Gong,
                    R. Gandhi,
                    C. Pignataro
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2025
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      19
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-spring-lsp-ping-path-sid-13.txt

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

        DOI:        10.17487/RFC9884

Segment Routing (SR) leverages source routing to steer packets
through an ordered list of instructions called "segments". SR can be
instantiated over the MPLS data plane. Path Segment Identifiers
(PSIDs) are used to identify and correlate bidirectional or
end-to-end paths in SR networks. This document defines procedures
(i.e., six new Target Forwarding Equivalence Class (FEC) Stack
sub-TLVs) for the use of LSP Ping to support connectivity
verification and fault isolation for SR paths that include PSIDs. The
mechanisms described enable the validation and tracing of SR paths
with Path SIDs in MPLS networks, complementing existing SR-MPLS
Operations, Administration, and Maintenance (OAM) capabilities.

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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team


_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org

Reply via email to