Protocol Action: 'IPv6 Subnet Model: the Relationship between Links and Subnet Prefixes' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 05 May 2010 14:59 UTC
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id F27C73A6D43; Wed, 5 May 2010 07:59:43 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'IPv6 Subnet Model: the Relationship between Links and Subnet Prefixes' to Proposed Standard
Message-Id: <20100505145943.F27C73A6D43@core3.amsl.com>
Date: Wed, 05 May 2010 07:59:43 -0700
Cc: 6man chair <6man-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.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.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 05 May 2010 14:59:44 -0000
The IESG has approved the following document: - 'IPv6 Subnet Model: the Relationship between Links and Subnet Prefixes ' <draft-ietf-6man-ipv6-subnet-model-12.txt> as a Proposed Standard This document is the product of the IPv6 Maintenance Working Group. The IESG contact persons are Jari Arkko and Ralph Droms. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-6man-ipv6-subnet-model-12.txt Technical Summary IPv6 specifies a model of a subnet that is different than the IPv4 subnet model. The subtlety of the differences has resulted in incorrect implementations that do not interoperate. This document spells out the most important difference; that an IPv6 address isn't automatically associated with an IPv6 on-link prefix. This document also updates (partially due to security concerns caused by incorrect implementations) a part of the definition of on-link from [RFC4861]. Working Group Summary This document represents the consensus of the 6MAN Working Group. Document Quality This document has been reviewed by members of the 6MAN Working Group. Personnel Document Shepherd is Brian Haberman. Responsible Area Director is Jari Arkko.