Protocol Action: 'Significance of IPv6 Interface Identifiers' to Proposed Standard (draft-ietf-6man-ug-06.txt)

The IESG <iesg-secretary@ietf.org> Mon, 23 December 2013 17:26 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 636831ADF6E; Mon, 23 Dec 2013 09:26:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level:
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6] autolearn=no
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 smYghxXtZApd; Mon, 23 Dec 2013 09:26:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C89F41AE19A; Mon, 23 Dec 2013 09:26:18 -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: 'Significance of IPv6 Interface Identifiers' to Proposed Standard (draft-ietf-6man-ug-06.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131223172618.25132.25038.idtracker@ietfa.amsl.com>
Date: Mon, 23 Dec 2013 09:26:18 -0800
Cc: 6man chair <6man-chairs@tools.ietf.org>, 6man mailing list <ipv6@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 Dec 2013 17:26:22 -0000

The IESG has approved the following document:
- 'Significance of IPv6 Interface Identifiers'
  (draft-ietf-6man-ug-06.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

OLD:
   This section describes clarifications to the IPv6 specifications that
   result from the above discussion.  Their aim is to reduce confusion
   while retaining the useful aspects of the "u" and "g" bits in IIDs.

NEW:
   This section describes clarifications to the IPv6 specifications that
   result from the above discussion.

OLD:
      In an IID, this bit is in position 6, i.e., position 70 in the
      complete IPv6 address.

NEW:
      In an IID, this bit is in position 6, i.e., position 70 in the
      complete IPv6 address (when counting from 0).

OLD:
      In an IID, this bit is in position 7, i.e., position 71 in the
      complete IPv6 address.

NEW:
      In an IID, this bit is in position 7, i.e., position 71 in the
      complete IPv6 address(when counting from 0).