Last Call: <draft-ietf-mpls-oam-ipv6-rao-02.txt> (IPv6 Router Alert Option for MPLS OAM) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 21 January 2015 23:22 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 F25901A8A78; Wed, 21 Jan 2015 15:22:45 -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 TerNGLkoOf4S; Wed, 21 Jan 2015 15:22:41 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8811A19F8; Wed, 21 Jan 2015 15:22:41 -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: Last Call: <draft-ietf-mpls-oam-ipv6-rao-02.txt> (IPv6 Router Alert Option for MPLS OAM) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20150121232241.12288.98926.idtracker@ietfa.amsl.com>
Date: Wed, 21 Jan 2015 15:22:41 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/oXS0ezoGgqo8kOhqlTsbNOTiYaQ>
Cc: mpls@ietf.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: Wed, 21 Jan 2015 23:22:46 -0000
The IESG has received a request from the Multiprotocol Label Switching WG (mpls) to consider the following document: - 'IPv6 Router Alert Option for MPLS OAM' <draft-ietf-mpls-oam-ipv6-rao-02.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-02-04. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract RFC 4379 defines the MPLS LSP Ping/Traceroute mechanism, in which the 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 depending on the Reply Mode used. While a generic "Router shall examine packet" Option Value is used for the IPv4 Router Alert Option (RAO), there is no generic Router Alert Option Value defined for IPv6 that can be used. This document allocates a new generic IPv6 Router Alert Option Value that can be used by MPLS 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 Router Alert Option (RAO) code point for MPLS OAM comes from MPLS LSP Ping/Traceroute. However, this code point is applicable to all MPLS OAM and not limited to MPLS LSP Ping/Traceroute. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-mpls-oam-ipv6-rao/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-mpls-oam-ipv6-rao/ballot/ No IPR declarations have been submitted directly on this I-D.