@misc{rfc9703,
    series =    {Request for Comments},
    number =    9703,
    howpublished =  {RFC 9703},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC9703},
    url =       {https://www.rfc-editor.org/info/rfc9703},
    author =    {Shraddha Hegde and Mukul Kumar Srivastava and Kapil Arora and Samson Ninan and Xiaohu Xu},
    title =     {{Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane}},
    pagetotal = 15,
    year =      2024,
    month =     dec,
    abstract =  {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.},
}