RFC 9703: Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9703
- Published
- December 2024
- Authors
- S. Hegde; M. Srivastava; K. Arora; S. Ninan; X. Xu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9716Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing NetworksCurrent
February 2025
- RFC 9655Egress Validation in Label Switched Path Ping and Traceroute MechanismsCurrent
November 2024
- RFC 9857Advertisement of Segment Routing Policies Using BGP - Link StateCurrent
October 2025
- RFC 9514Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6)Current
December 2023
- RFC 9086Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer EngineeringCurrent
August 2021
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 8814Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link StateCurrent
August 2020
- RFC 8491Signaling Maximum SID Depth (MSD) Using IS-ISCurrent
November 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?