Subject: [IANA #729629] Evaluation: <draft-ietf-6man-ug-06.txt> to Proposed Standard

From: "Pearl Liang via RT" <[email-masked]>
Date: Tue, 3 Dec 2013 19:28:18 +0000

(BEGIN IANA COMMENTS)

IESG:

IANA OK. Comments in tracker.
IANA Actions - YES

Upon approval of this document, we understand that we need to update 
the registry "Reserved IPv6 Interface Identifiers registry" located
at:

http://www.iana.org/assignments/ipv6-interface-ids/

as follows:

Reference: [RFC5453][RFC-to-be]
Note:
   Full deployment of a new reserved IID value would require updates to
   IID generation code in every deployed IPv6 stack, so the technical
   justification for such a Standards Action would need to be extremely
   strong.

These are the only IANA Actions that need completion. 

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.

Thanks,

Pearl Liang
ICANN/IANA

(END IANA COMMENTS)

On Tue Dec 03 05:08:31 2013, [email-masked] wrote:
> Evaluation for <draft-ietf-6man-ug-06.txt> can be found at
> http://datatracker.ietf.org/doc/draft-ietf-6man-ug/
> 
> Last call to expire on: 2013-11-28 00:00
> 
> 
>         Please return the full line with your position.
> 
>                       Yes  No-Objection  Discuss  Abstain
> Brian Haberman       [ X ]     [   ]      [   ]    [   ]
> 
> 
> "Yes" or "No-Objection" positions from 2/3 of non-recused ADs,
> with no "Discuss" positions, are needed for approval.
> 
> DISCUSSES AND COMMENTS
> ======================
> 
> ---- following is a DRAFT of message to be sent AFTER approval ---
> From: The IESG <[email-masked]>
> To: IETF-Announce <[email-masked]>
> Cc: RFC Editor <[email-masked]>,
>     6man mailing list <[email-masked]>,
>     6man chair <[email-masked]>
> Subject: Protocol Action: 'Significance of IPv6 Interface Identifiers'
> to Proposed Standard (draft-ietf-6man-ug-05.txt)
> 
> The IESG has approved the following document:
> - 'Significance of IPv6 Interface Identifiers'
>   (draft-ietf-6man-ug-05.txt) as Proposed Standard
> 
> This document is the product of the IPv6 Maintenance Working Group.
> 
> The IESG contact persons are Brian Haberman and Ted Lemon.
> 
> A URL of this Internet Draft is:
> http://datatracker.ietf.org/doc/draft-ietf-6man-ug/
> 
> 
> 
> 
> Technical Summary:
> 
>    The IPv6 addressing architecture includes a unicast interface
>    identifier that is used in the creation of many IPv6 addresses.
>    Interface identifiers are formed by a variety of methods.  This
>    document clarifies that the bits in an interface identifier have no
>    generic meaning and that the identifier should be treated as an
>    opaque value.  In particular, RFC 4291 defines a method by which
> the
>    Universal and Group bits of an IEEE link-layer address are mapped
>    into an IPv6 unicast interface identifier.  This document clarifies
>    that those two bits are significant only in interface identifiers
>    that are derived from an IEEE link-layer address, and updates RFC
>    4291 accordingly.
> 
> Working Group Summary:
> 
> This document is the product of the IPv6 WG. The final version
> reflects strong WG consensus.
> 
> Document Quality:
> 
> In the 6man working group, the chairs do a detailed review
> and also ask one or two volunteers (or hand picked experts) to
> do a thorough review of documents before the are being
> advanced to the IESG.
> 
> Fernando Gont performed a detailed review of the final version.
> 
> Personnel:
> 
> Ole Troan is the document Shepherd.
> Brian Haberman is the Area Director.
> 
> RFC Editor Note
> 
>   (Insert RFC Editor Note here or remove section)
> 
> IRTF Note
> 
>   (Insert IRTF Note here or remove section)
> 
> IESG Note
> 
>   (Insert IESG Note here or remove section)
> 
> IANA Note
> 
>   (Insert IANA Note here or remove section)
> 
> 
> 
>