Egress Validation in Label Switched Path Ping and Traceroute Mechanisms
RFC 9655
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['FEC', 'OAM', 'OSPF', 'IS-IS', 'SPRING']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "N. Nainar": changed name from "Nagendra Nainar" to "N. Nainar" |
|
2026-05-20
|
(System) | Changed author "Z. Ali": changed name from "Zafar Ali" to "Z. Ali" |
|
2026-05-20
|
(System) | Changed author "K. Arora": changed name from "Kapil Arora" to "K. Arora" |
|
2026-05-20
|
(System) | Changed author "S. Hegde": changed name from "Shraddha Hegde" to "S. Hegde", changed is_editor from "False" to "True", cleared country (was "India") |
|
2026-05-20
|
(System) | Changed author "D. Rathi": changed name from "Deepti Rathi" to "D. Rathi", changed is_editor from "False" to "True", cleared country (was "India") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2024-11-19
|
(System) | Received changes through RFC Editor sync (created document RFC 9655, created became rfc relationship between draft-ietf-mpls-egress-tlv-for-nil-fec and RFC 9655, set abstract to 'The … Received changes through RFC Editor sync (created document RFC 9655, created became rfc relationship between draft-ietf-mpls-egress-tlv-for-nil-fec and RFC 9655, set abstract to '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.', set pages to 10, set standardization level to Proposed Standard, added RFC published event at 2024-11-19) |
|
2024-11-19
|
(System) | RFC published |