IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance
RFC 7506, “IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance”, is a Historic document published in April 2015 by K. Raza, N. Akiya, C. Pignataro. It updates RFC 4379. The canonical text is published by the RFC Editor.
Abstract
RFC 4379 defines the MPLS Label Switched Path (LSP) Ping/Traceroute mechanism in which the Router Alert Option (RAO) MUST be set in the IP header of the MPLS Echo Request messages and may conditionally be set in the IP header of the MPLS Echo Reply messages depending on the Reply Mode used. While a generic "Router shall examine packet" Option Value is used for the IPv4 RAO, there is no generic RAO value defined 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 Echo Request 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 OAM comes from the MPLS LSP Ping/Traceroute. However, this value is applicable to all MPLS OAM and not limited to MPLS LSP Ping/ Traceroute.
What “Historic” means
A specification that has been superseded or is otherwise no longer recommended for use.
The canonical text of RFC 7506 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7505 A "Null MX" No Service Resource Record for Domains That Accept No Mail
- RFC 7507 TLS Fallback Signaling Cipher Suite Value for Preventing Protocol Downgrade Attacks
- RFC 7504 SMTP 521 and 556 Reply Codes
- RFC 7508 Securing Header Fields with S/MIME
- RFC 7503 OSPFv3 Autoconfiguration
- RFC 7509 RTP Control Protocol Extended Report for Post-Repair Loss Count Metrics
- RFC 7502 Methodology for Benchmarking Session Initiation Protocol Devices: Basic Session Setup and Registration
- RFC 7510 Encapsulating MPLS in UDP