Skip to main content

Segment Routing Generic TLV for MPLS Label Switched Path (LSP) Ping/Traceroute

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Nagendra Kumar Nainar , Carlos Pignataro , Zafar Ali , Clarence Filsfils , Tarek Saad
Last updated 2022-05-28 (Latest revision 2021-11-24)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

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


RFC8402 introduces Segment Routing architecture that leverages source routing and tunneling paradigms and can be directly applied to the Multi Protocol Label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called segments, by prepending the packet with Segment Routing header. SR architecture defines different types of segments with different forwarding semantics associated. SR can be applied to the MPLS directly and to IPv6 dataplane using a new routing header. RFC8287 defines the extensions to MPLS LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifier (SIDs) with an MPLS data plane. Various SIDs are proposed as part of SR architecture with different associated instructions that raises a need to come up with new Target FEC Stack Sub-TLV for each such SIDs. This document defines a new Target FEC Stack Sub-TLV that is used to validate the instruction associated with any SID.


Nagendra Kumar Nainar
Carlos Pignataro
Zafar Ali
Clarence Filsfils
Tarek Saad

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