[mpls] RFC 7506 on IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance (OAM)
rfc-editor@rfc-editor.org Fri, 17 April 2015 20:39 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD3A1A88D5; Fri, 17 Apr 2015 13:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LLRku1LVSj0q; Fri, 17 Apr 2015 13:39:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id E14F21A9070; Fri, 17 Apr 2015 13:39:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5A84F180209; Fri, 17 Apr 2015 13:38:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150417203854.5A84F180209@rfc-editor.org>
Date: Fri, 17 Apr 2015 13:38:54 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/5VyokWdVPxdPA66NvNVfQOCWYvI>
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 7506 on IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance (OAM)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 20:39:49 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7506
Title: IPv6 Router Alert Option for
MPLS Operations, Administration, and Maintenance (OAM)
Author: K. Raza, N. Akiya, C. Pignataro
Status: Standards Track
Stream: IETF
Date: April 2015
Mailbox: skraza@cisco.com,
nobo.akiya.dev@gmail.com,
cpignata@cisco.com
Pages: 6
Characters: 11322
Updates: RFC 4379
I-D Tag: draft-ietf-mpls-oam-ipv6-rao-03.txt
URL: https://www.rfc-editor.org/info/rfc7506
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.
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/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC