Skip to main content

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

Document Type Replaced Internet-Draft (mpls WG)
Authors Shraddha Hegde , Kapil Arora , Mukul Srivastava , Samson Ninan , Xiaohu Xu
Last updated 2020-06-06 (Latest revision 2020-06-03)
Replaced by draft-ietf-mpls-sr-epe-oam
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text xml htmlized pdfized bibtex
Stream WG state Adopted by a WG
Document shepherd Loa Andersson
IESG IESG state Replaced by draft-ietf-mpls-sr-epe-oam
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 can be found at:


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
Kapil Arora
Mukul Srivastava
Samson Ninan
Xiaohu Xu

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