Protocol Action: 'IPv6 Router Alert Option for MPLS OAM' to Proposed Standard (draft-ietf-mpls-oam-ipv6-rao-03.txt)
The IESG <iesg-secretary@ietf.org> Mon, 23 February 2015 19:21 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF591A6EDA; Mon, 23 Feb 2015 11:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2BgTem-OvMPr; Mon, 23 Feb 2015 11:21:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6660D1A6EDB; Mon, 23 Feb 2015 11:21:31 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'IPv6 Router Alert Option for MPLS OAM' to Proposed Standard (draft-ietf-mpls-oam-ipv6-rao-03.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150223192131.25612.22046.idtracker@ietfa.amsl.com>
Date: Mon, 23 Feb 2015 11:21:31 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/ApEB7YoCSJq_JTsc57DxRZBgGQI>
Cc: mpls mailing list <mpls@ietf.org>, mpls chair <mpls-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2015 19:21:34 -0000
The IESG has approved the following document: - 'IPv6 Router Alert Option for MPLS OAM' (draft-ietf-mpls-oam-ipv6-rao-03.txt) as Proposed Standard This document is the product of the Multiprotocol Label Switching Working Group. The IESG contact persons are Alia Atlas and Adrian Farrel. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-mpls-oam-ipv6-rao/ Technical Summary This document updates RFC 4379 This document fixes a gap in MPLS/IPv6, in RFC 4379 that defines the MPLS LSP Ping/Traceroute mechanism, a Router Alert Option 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. A generic "Router shall examine packet" Option Value is used for the IPv4 Router Alert Option (RAO). There is no corresponding generic Router Alert Option Value defined for IPv6. This document allocates this new generic IPv6 RAO Value. The RAO value can be used by the entire set of MPLS OAM functions as needed, but the initial motivation comes from using RFC 4379 with IPv6. The document defines the RAO that will be used in the MPLS Echo Request and MPLS Echo Reply messages in IPv6 environments. Consequently, it updates RFC 4379. Working Group Summary This document is generally accepted by the working group, there are several implementations of RFC 4379 for IPv6 going on or planned and this gap is widely recognized. Document Quality No expert reviews necessary! The RAO Value is necessary to correctly implement LSP Ping and Traceroute for IPv6 networks. Personnel Document Shepherd: Loa ANdersson Responsible Area Director: Adrian Farrel