--- 1/draft-ietf-6man-ipv6-subnet-model-05.txt 2009-11-14 22:12:14.000000000 +0100 +++ 2/draft-ietf-6man-ipv6-subnet-model-06.txt 2009-11-14 22:12:14.000000000 +0100 @@ -1,74 +1,80 @@ Network Working Group H. Singh Internet-Draft W. Beebee -Intended status: Standards Track Cisco Systems, Inc. -Expires: November 16, 2009 E. Nordmark - Sun Microsystems - May 15, 2009 +Updates: 4861 (if approved) Cisco Systems, Inc. +Intended status: Standards Track E. Nordmark +Expires: May 18, 2010 Sun Microsystems + November 14, 2009 IPv6 Subnet Model: the Relationship between Links and Subnet Prefixes - draft-ietf-6man-ipv6-subnet-model-05 + draft-ietf-6man-ipv6-subnet-model-06 + +Abstract + + 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]. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the - provisions of BCP 78 and BCP 79. This document may contain material - from IETF Documents or IETF Contributions published or made publicly - available before November 10, 2008. The person(s) controlling the - copyright in some of this material may not have granted the IETF - Trust the right to allow modifications of such material outside the - IETF Standards Process. Without obtaining an adequate license from - the person(s) controlling the copyright in such materials, this - document may not be modified outside the IETF Standards Process, and - derivative works of it may not be created outside the IETF Standards - Process, except to format it for publication as an RFC or to - translate it into languages other than English. + provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on November 16, 2009. + This Internet-Draft will expire on May 18, 2010. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal - Provisions Relating to IETF Documents in effect on the date of - publication of this document (http://trustee.ietf.org/license-info). - Please review these documents carefully, as they describe your rights - and restrictions with respect to this document. - -Abstract + Provisions Relating to IETF Documents + (http://trustee.ietf.org/license-info) in effect on the date of + publication of this document. Please review these documents + carefully, as they describe your rights and restrictions with respect + to this document. Code Components extracted from this document must + include Simplified BSD License text as described in Section 4.e of + the Trust Legal Provisions and are provided without warranty as + described in the BSD License. - 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]. + This document may contain material from IETF Documents or IETF + Contributions published or made publicly available before November + 10, 2008. The person(s) controlling the copyright in some of this + material may not have granted the IETF Trust the right to allow + modifications of such material outside the IETF Standards Process. + Without obtaining an adequate license from the person(s) controlling + the copyright in such materials, this document may not be modified + outside the IETF Standards Process, and derivative works of it may + not be created outside the IETF Standards Process, except to format + it for publication as an RFC or to translate it into languages other + than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Host Behavior . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Host Rules . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Observed Incorrect Implementation Behavior . . . . . . . . . . 9 5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9