RFC 5942 on IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes
rfc-editor@rfc-editor.org Sat, 17 July 2010 01:33 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E60D83A6979; Fri, 16 Jul 2010 18:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[AWL=-0.109, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ba5yazhehJN7; Fri, 16 Jul 2010 18:33:35 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id F095D3A6982; Fri, 16 Jul 2010 18:33:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5F2D1E06BA; Fri, 16 Jul 2010 18:33:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5942 on IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes
From: rfc-editor@rfc-editor.org
Message-Id: <20100717013347.5F2D1E06BA@rfc-editor.org>
Date: Fri, 16 Jul 2010 18:33:47 -0700
Cc: ipv6@ietf.org, 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: Sat, 17 Jul 2010 01:33:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5942
Title: IPv6 Subnet Model: The Relationship
between Links and Subnet Prefixes
Author: H. Singh, W. Beebee,
E. Nordmark
Status: Standards Track
Stream: IETF
Date: July 2010
Mailbox: shemant@cisco.com,
wbeebee@cisco.com,
erik.nordmark@oracle.com
Pages: 11
Characters: 27035
Updates: RFC4861
I-D Tag: draft-ietf-6man-ipv6-subnet-model-12.txt
URL: http://www.rfc-editor.org/rfc/rfc5942.txt
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 RFC 4861.
[STANDARDS TRACK]
This document is a product of the IPv6 Maintenance Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC