A new Request for Comments is now available in online RFC libraries.
RFC 9655
Title: Egress Validation in Label Switched
Path Ping and Traceroute Mechanisms
Author: D. Rathi, Ed.,
S. Hegde, Ed.,
K. Arora,
Z. Ali,
N. Nainar
Status: Standards Track
Stream: IETF
Date: November 2024
Mailbox: [email protected],
[email protected],
[email protected],
[email protected],
[email protected]
Pages: 10
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-egress-tlv-for-nil-fec-15.txt
URL: https://www.rfc-editor.org/info/rfc9655
DOI: 10.17487/RFC9655
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.
This document is a product of the Multiprotocol Label Switching Working Group
of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
