%% You should probably cite draft-ietf-mpls-sr-epe-oam-13 instead of this revision. @techreport{ietf-mpls-sr-epe-oam-08, number = {draft-ietf-mpls-sr-epe-oam-08}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-mpls-sr-epe-oam/08/}, author = {Shraddha Hegde and Mukul Srivastava and Kapil Arora and Samson Ninan and Xiaohu Xu}, title = {{Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data Planes}}, pagetotal = 16, year = 2023, month = feb, day = 9, abstract = {Egress Peer Engineering (EPE) is an application of Segment Routing to solve the problem of egress peer selection. The Segment Routing 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 a node to program the PeerNode Segment Identifier(SID) describing a session between two nodes, the PeerAdj SID describing the link (one or more) that is used by sessions between peer nodes, and the PeerSet SID describing an arbitrary set of sessions or links between a local node and its peers. This document provides new sub-TLVs for EPE Segment Identifiers (SID) that would be used in the MPLS Target stack TLV (Type 1), in MPLS Ping and Traceroute procedures.}, }