Search RFCs

RFC Editor

File formats:

Status:

HISTORIC (changed from PROPOSED STANDARD)

Updates:

RFC 4379

Authors:

K. Raza
N. Akiya
C. Pignataro

Stream:

IETF

Source:

mpls (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7506

Discuss this RFC: Send questions or comments to the mailing listmpls@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7506

Abstract

RFC 4379 defines the MPLS Label Switched Path (LSP) Ping/Traceroutemechanism in which the Router Alert Option (RAO) MUST be set in theIP header of the MPLS Echo Request messages and may conditionally beset in the IP header of the MPLS Echo Reply messages depending on theReply Mode used. While a generic "Router shall examine packet"Option Value is used for the IPv4 RAO, there is no generic RAO valuedefined for IPv6 that can be used. This document allocates a new,generic IPv6 RAO value that can be used by MPLS Operations,Administration, and Maintenance (OAM) tools, including the MPLS EchoRequest and MPLS Echo Reply messages for MPLS in IPv6 environments.Consequently, it updates RFC 4379.

The initial motivation to request an IPv6 RAO value for MPLS OAMcomes from the MPLS LSP Ping/Traceroute. However, this value isapplicable to all MPLS OAM and not limited to MPLS LSP Ping/Traceroute.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.