RFC 9703 on Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane

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

        RFC 9703

        Title:      Label Switched Path (LSP) Ping/Traceroute 
                    for Segment Routing (SR) Egress Peer 
                    Engineering (EPE) Segment Identifiers (SIDs) with 
                    MPLS Data Plane 
        Author:     S. Hegde,
                    M. Srivastava,
                    K. Arora,
                    S. Ninan,
                    X. Xu
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2024
        Mailbox:    shraddha@juniper.net,
                    msri@juniper.net,
                    kapil.it@gmail.com,
                    samson.cse@gmail.com,
                    xuxiaohu_ietf@hotmail.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-sr-epe-oam-19.txt

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

        DOI:        10.17487/RFC9703

Egress Peer Engineering (EPE) is an application of Segment Routing
(SR) that solves the problem of egress peer selection.  The SR-based
BGP-EPE solution allows a centralized controller, e.g., a
Software-Defined Network (SDN) controller, to program any egress
peer. The EPE solution requires the node or the SDN controller to
program 1) the PeerNode Segment Identifier (SID) describing a session
between two nodes, 2) the PeerAdj SID describing the link or links
that are used by the sessions between peer nodes, and 3) the PeerSet
SID describing any connected interface to any peer in the related
group. This document provides new sub-TLVs for EPE-SIDs that are used
in the Target FEC Stack TLV (Type 1) in MPLS Ping and Traceroute
procedures.

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
Association Management Solutions, LLC