--- 1/draft-ietf-6man-rfc4291bis-05.txt 2016-11-14 23:13:07.635178196 -0800 +++ 2/draft-ietf-6man-rfc4291bis-06.txt 2016-11-14 23:13:07.695179679 -0800 @@ -1,19 +1,19 @@ Network Working Group R. Hinden Internet-Draft Check Point Software Obsoletes: 4291 (if approved) S. Deering Intended status: Standards Track Retired -Expires: April 7, 2017 October 4, 2016 +Expires: May 19, 2017 November 15, 2016 IP Version 6 Addressing Architecture - draft-ietf-6man-rfc4291bis-05 + draft-ietf-6man-rfc4291bis-06 Abstract This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. This document obsoletes RFC 4291, "IP Version 6 Addressing @@ -27,21 +27,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." - This Internet-Draft will expire on April 7, 2017. + This Internet-Draft will expire on May 19, 2017. Copyright Notice Copyright (c) 2016 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -448,21 +448,21 @@ Interface ID as an opaque bit string without any internal structure. Note that the uniqueness of interface identifiers is independent of the uniqueness of IPv6 addresses. For example, a Global Unicast address may be created with an interface identifier that is only unique on a single subnet, and a Link-Local address may be created with interface identifier that is unique over multiple subnets. For all unicast addresses, except those that start with the binary value 000, Interface IDs are required to be 64 bits long. Background - on the 64 bit boundary can be bound in [RFC7421]. + on the 64 bit boundary in IPv6 addresses can be found in [RFC7421]. The details of forming interface identifiers are defined in other specifications, such as "Privacy Extensions for Stateless Address Autoconfiguration in IPv6" [RFC4941] or "A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)"[RFC7217]. Specific cases are described in appropriate "IPv6 over " specifications, such as "IPv6 over Ethernet" [RFC2464] and "Transmission of IPv6 Packets over ITU-T G.9959 Networks" [RFC7428]. The security and privacy considerations for IPv6 address generation is described in [RFC7721]. @@ -1274,20 +1274,22 @@ and that it doesn't cause any problems in practice. Appendix B. CHANGES SINCE RFC 4291 This document has the following changes from RFC4291, "IP Version 6 Addressing Architecture". Numbers identify the Internet-Draft version that the change was made.: Working Group Internet Drafts + 06) Editorial changes. + 05) Expanded Security Considerations Section to discuss privacy issues related to using stable interface identifiers to create IPv6 addresses, and reference solutions that mitigate these issues such as RFC7721, RFC4941, RFC7271. 05) Added instructions in IANA Considerations to update references in the IANA registries that currently point to RFC4291 to point to this document. 05) Rename Section 2.4.7 to "Other Local Unicast Addresses" and