Subject: [mpls] [IANA #805002] Last Call: <draft-ietf-mpls-oam-ipv6-rao-02.txt> (IPv6 Router Alert Option for MPLS OAM) to Proposed Standard

From: "Pearl Liang via RT" <[email-masked]>
Date: Tue, 27 Jan 2015 23:40:25 +0000

(BEGIN IANA LAST CALL COMMENTS)

IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-mpls-oam-ipv6-rao-02.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

We received the following comments/questions from the IANA's reviewer:

IANA understands that, upon approval of this document, there is a single action which IANA must complete.

In the IPv6 Router Alert Option Values registry located at:

http://www.iana.org/assignments/ipv6-routeralert-values/

a new option value is to be registered as follows:

Value: [ TBD-at-registration ]
Description: MPLS OAM
Reference: [ RFC-to-be ]

IANA understands that this is the only action that needs to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.  

Please note that IANA cannot reserve specific values. However, early allocation is available for some types of registrations. For more information, please see RFC 7120. 

Thanks,

Pearl Liang
ICANN

(END IANA LAST CALL COMMENTS)

On Wed Jan 21 23:23:08 2015, [email-masked] wrote:
> 
> 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
> [email-masked] mailing lists by 2015-02-04. Exceptionally, comments may be
> sent to [email-masked] 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.
>