RFC 9655: Egress Validation in Label Switched Path Ping and Traceroute Mechanisms
In plain English — editorial summary, not part of the RFC
The MPLS ping and traceroute mechanisms described in RFC 8029 and the related extensions for Segment Routing (SR) defined in RFC 8287 are highly valuable for validating control plane and data plane synchronization. In certain environments, only some intermediate or transit nodes may have been upgraded to support these validation procedures. A straightforward MPLS ping and traceroute mechanism allows traversal of any path without validation of the control plane state. RFC 8029 supports this mechanism with the Nil Forwarding Equivalence Class (FEC). The procedures outlined in RFC 8029 are primarily applicable when the Nil FEC is used as an intermediate FEC in the FEC stack. However, challenges arise when all labels in the label stack are represented using the Nil FEC. This document introduces a new Type-Length-Value (TLV) as an extension to the existing Nil FEC. It describes MPLS ping and traceroute procedures using the Nil FEC with this extension to address and overcome these challenges.
Document record
- Document ID
- RFC9655
- Published
- November 2024
- Authors
- D. Rathi; S. Hegde; K. Arora; Z. Ali; N. Nainar
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9703Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data PlaneCurrent
December 2024
- RFC 9716Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing NetworksCurrent
February 2025
- RFC 9351Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm AdvertisementCurrent
February 2023
- RFC 9314YANG Data Model for Bidirectional Forwarding Detection (BFD)Current
September 2022
- RFC 9294Application-Specific Link Attributes Advertisement Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2022
- RFC 9247BGP - Link State (BGP-LS) Extensions for Seamless Bidirectional Forwarding Detection (S-BFD)Current
June 2022
- RFC 9127YANG Data Model for Bidirectional Forwarding Detection (BFD)Updated
October 2021
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
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?