Skip to main content

Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering Segment Identifiers (SIDs) with MPLS Data Planes

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Shraddha Hegde , Mukul Srivastava , Kapil Arora , Samson Ninan , Xiaohu Xu
Last updated 2023-08-13 (Latest revision 2023-02-09)
Replaces draft-hegde-mpls-spring-epe-oam
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Loa Andersson
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to Loa Andersson <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Shraddha Hegde
Mukul Srivastava
Kapil Arora
Samson Ninan
Xiaohu Xu

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)