IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance (OAM)
RFC 7506
| Document | Type |
RFC - Proposed Standard
(April 2015; No errata)
Updates RFC 4379
|
|
|---|---|---|---|
| Authors | Kamran Raza , Nobo Akiya , Carlos Pignataro | ||
| Last updated | 2018-12-20 | ||
| Replaces | draft-raza-mpls-oam-ipv6-rao | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Loa Andersson | ||
| Shepherd write-up | Show (last changed 2015-01-04) | ||
| IESG | IESG state | RFC 7506 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Deborah Brungard | ||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) K. Raza
Request for Comments: 7506 Cisco Systems, Inc.
Updates: 4379 N. Akiya
Category: Standards Track Big Switch Networks
ISSN: 2070-1721 C. Pignataro
Cisco Systems, Inc.
April 2015
IPv6 Router Alert Option
for MPLS Operations, Administration, and Maintenance (OAM)
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7506.
Raza, et al. Standards Track [Page 1]
RFC 7506 MPLS OAM IPv6 Router Alert April 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Specification of Requirements . . . . . . . . . . . . . . . . 3
3. IPv6 RAO Value for MPLS OAM . . . . . . . . . . . . . . . . . 3
4. Updates to RFC 4379 . . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
A commonly deployed MPLS OAM tool is specified in [RFC4379],
"Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures",
which is used to diagnose MPLS network data planes. This
specification, often referred to as "MPLS LSP Ping/Traceroute"
[RFC4379], requires the use of the Router Alert Option (RAO) in the
IP header. For example, Section 4.3 of [RFC4379] states that the IP
RAO MUST be set in the IP header of an MPLS Echo Request message.
Similarly, Section 4.5 of [RFC4379] states that the IP RAO MUST be
set in the IP header of an MPLS Echo Reply message if the Reply Mode
in the Echo Request is set to "Reply via an IPv4/IPv6 UDP packet with
Router Alert".
[RFC2113] defines a generic Option Value 0x0 for IPv4 RAO that is
used in LSP Ping and LSP Traceroute for MPLS in IPv4 environments.
This IPv4 RAO value of 0x0 is assigned to "Router shall examine
packet". However, currently there is no generic IPV6 RAO value
defined that can be used in LSP Ping and LSP Traceroute for MPLS in
Raza, et al. Standards Track [Page 2]
Show full document text