draft-ietf-6man-rfc4291bis-02.txt   draft-ietf-6man-rfc4291bis-03.txt 
Network Working Group R. Hinden Network Working Group R. Hinden
Internet-Draft Check Point Software Internet-Draft Check Point Software
Obsoletes: 4291 (if approved) S. Deering Obsoletes: 4291 (if approved) S. Deering
Intended status: Standards Track Retired Intended status: Standards Track Retired
Expires: October 29, 2016 April 27, 2016 Expires: December 30, 2016 June 28, 2016
IP Version 6 Addressing Architecture IP Version 6 Addressing Architecture
draft-ietf-6man-rfc4291bis-02 draft-ietf-6man-rfc4291bis-03
Abstract Abstract
This specification defines the addressing architecture of the IP This specification defines the addressing architecture of the IP
Version 6 (IPv6) protocol. The document includes the IPv6 addressing Version 6 (IPv6) protocol. The document includes the IPv6 addressing
model, text representations of IPv6 addresses, definition of IPv6 model, text representations of IPv6 addresses, definition of IPv6
unicast addresses, anycast addresses, and multicast addresses, and an unicast addresses, anycast addresses, and multicast addresses, and an
IPv6 node's required addresses. IPv6 node's required addresses.
This document obsoletes RFC 4291, "IP Version 6 Addressing This document obsoletes RFC 4291, "IP Version 6 Addressing
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 29, 2016. This Internet-Draft will expire on December 30, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 3, line 7
2.7. A Node's Required Addresses . . . . . . . . . . . . . . . 20 2.7. A Node's Required Addresses . . . . . . . . . . . . . . . 20
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
4. Security Considerations . . . . . . . . . . . . . . . . . . . 21 4. Security Considerations . . . . . . . . . . . . . . . . . . . 21
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Normative References . . . . . . . . . . . . . . . . . . 22 6.1. Normative References . . . . . . . . . . . . . . . . . . 22
6.2. Informative References . . . . . . . . . . . . . . . . . 22 6.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Modified EUI-64 Format Interface Identifiers . . . . 24 Appendix A. Modified EUI-64 Format Interface Identifiers . . . . 24
A.1. Creating Modified EUI-64 Format Interface Identifiers . . 25 A.1. Creating Modified EUI-64 Format Interface Identifiers . . 25
Appendix B. CHANGES SINCE RFC 4291 . . . . . . . . . . . . . . . 27 Appendix B. CHANGES SINCE RFC 4291 . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
This specification defines the addressing architecture of the IP This specification defines the addressing architecture of the IP
Version 6 protocol. It includes the basic formats for the various Version 6 protocol. It includes the basic formats for the various
types of IPv6 addresses (unicast, anycast, and multicast). types of IPv6 addresses (unicast, anycast, and multicast).
2. IPv6 Addressing 2. IPv6 Addressing
IPv6 addresses are 128-bit identifiers for interfaces and sets of IPv6 addresses are 128-bit identifiers for interfaces and sets of
skipping to change at page 11, line 39 skipping to change at page 11, line 39
the uniqueness of IPv6 addresses. For example, a Global Unicast the uniqueness of IPv6 addresses. For example, a Global Unicast
address may be created with an interface identifier that is only address may be created with an interface identifier that is only
unique on a single subnet, and a Link-Local address may be created unique on a single subnet, and a Link-Local address may be created
with interface identifier that is unique over multiple subnets. with interface identifier that is unique over multiple subnets.
For all unicast addresses, except those that start with the binary For all unicast addresses, except those that start with the binary
value 000, Interface IDs are required to be 64 bits long. value 000, Interface IDs are required to be 64 bits long.
The details of forming interface identifiers are defined in other The details of forming interface identifiers are defined in other
specifications, such as "Privacy Extensions for Stateless Address specifications, such as "Privacy Extensions for Stateless Address
Autoconfiguration in IPv6" [RFC4941] and "Recommendation on Stable Autoconfiguration in IPv6" [RFC4941] or "A Method for Generating
IPv6 Interface Identifiers" [I-D.ietf-6man-default-iids]. Specific Semantically Opaque Interface Identifiers with IPv6 Stateless Address
cases are described in appropriate "IPv6 over <link>" specifications, Autoconfiguration (SLAAC)"[RFC7217]. Specific cases are described in
such as "IPv6 over Ethernet" [RFC2464] and "Transmission of IPv6 appropriate "IPv6 over <link>" specifications, such as "IPv6 over
Packets over ITU-T G.9959 Networks" [RFC7428]. 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].
Earlier versions of this document described a method of forming Earlier versions of this document described a method of forming
interface identifiers derived from IEEE MAC-layer addresses call interface identifiers derived from IEEE MAC-layer addresses call
Modified EUI-64 format. These are described in Appendix A and are no Modified EUI-64 format. These are described in Appendix A and are no
longer recommended. longer recommended.
2.4.2. The Unspecified Address 2.4.2. The Unspecified Address
The address 0:0:0:0:0:0:0:0 is called the unspecified address. It The address 0:0:0:0:0:0:0:0 is called the unspecified address. It
must never be assigned to any node. It indicates the absence of an must never be assigned to any node. It indicates the absence of an
skipping to change at page 22, line 38 skipping to change at page 22, line 38
(IPv6) Specification", draft-ietf-6man-rfc2460bis-04 (work (IPv6) Specification", draft-ietf-6man-rfc2460bis-04 (work
in progress), March 2016. in progress), March 2016.
6.2. Informative References 6.2. Informative References
[EUI64] "IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) [EUI64] "IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
Registration Authority"", March 1997, Registration Authority"", March 1997,
<http://standards.ieee.org/regauth/oui/tutorials/ <http://standards.ieee.org/regauth/oui/tutorials/
EUI64.html>. EUI64.html>.
[I-D.ietf-6man-default-iids]
Gont, F., Cooper, A., Thaler, D., and S. LIU,
"Recommendation on Stable IPv6 Interface Identifiers",
draft-ietf-6man-default-iids-10 (work in progress),
February 2016.
[IANA-AD] "Internet Protocol Version 6 Address Space", [IANA-AD] "Internet Protocol Version 6 Address Space",
<https://www.iana.org/assignments/ipv6-address-space/ipv6- <https://www.iana.org/assignments/ipv6-address-space/ipv6-
address-space.xhtml>. address-space.xhtml>.
[IANA-SP] "IANA IPv6 Special-Purpose Address Registry", [IANA-SP] "IANA IPv6 Special-Purpose Address Registry",
<https://www.iana.org/assignments/iana-ipv6-special- <https://www.iana.org/assignments/iana-ipv6-special-
registry/iana-ipv6-special-registry.xhtml>. registry/iana-ipv6-special-registry.xhtml>.
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998, Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998,
skipping to change at page 24, line 10 skipping to change at page 24, line 5
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing
(CIDR): The Internet Address Assignment and Aggregation (CIDR): The Internet Address Assignment and Aggregation
Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August
2006, <http://www.rfc-editor.org/info/rfc4632>. 2006, <http://www.rfc-editor.org/info/rfc4632>.
[RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy
Extensions for Stateless Address Autoconfiguration in Extensions for Stateless Address Autoconfiguration in
IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007, IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007,
<http://www.rfc-editor.org/info/rfc4941>. <http://www.rfc-editor.org/info/rfc4941>.
[RFC7217] Gont, F., "A Method for Generating Semantically Opaque
Interface Identifiers with IPv6 Stateless Address
Autoconfiguration (SLAAC)", RFC 7217, DOI 10.17487/
RFC7217, April 2014,
<http://www.rfc-editor.org/info/rfc7217>.
[RFC7428] Brandt, A. and J. Buron, "Transmission of IPv6 Packets [RFC7428] Brandt, A. and J. Buron, "Transmission of IPv6 Packets
over ITU-T G.9959 Networks", RFC 7428, DOI 10.17487/ over ITU-T G.9959 Networks", RFC 7428, DOI 10.17487/
RFC7428, February 2015, RFC7428, February 2015,
<http://www.rfc-editor.org/info/rfc7428>. <http://www.rfc-editor.org/info/rfc7428>.
[RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy
Considerations for IPv6 Address Generation Mechanisms",
RFC 7721, DOI 10.17487/RFC7721, March 2016,
<http://www.rfc-editor.org/info/rfc7721>.
Appendix A. Modified EUI-64 Format Interface Identifiers Appendix A. Modified EUI-64 Format Interface Identifiers
Modified EUI-64 format-based interface identifiers may have universal Modified EUI-64 format-based interface identifiers may have universal
scope when derived from a universal token (e.g., IEEE 802 48-bit MAC scope when derived from a universal token (e.g., IEEE 802 48-bit MAC
or IEEE EUI-64 identifiers [EUI64]) or may have local scope where a or IEEE EUI-64 identifiers [EUI64]) or may have local scope where a
global token is not being used (e.g., serial links, tunnel end- global token is not being used (e.g., serial links, tunnel end-
points) or where global tokens are undesirable (e.g., temporary points) or where global tokens are undesirable (e.g., temporary
tokens for privacy [RFC4941]. tokens for privacy [RFC4941].
Modified EUI-64 format interface identifiers are formed by inverting Modified EUI-64 format interface identifiers are formed by inverting
skipping to change at page 28, line 4 skipping to change at page 28, line 12
EUI-48 and MAC-48 identifiers are syntactically equivalent, EUI-48 and MAC-48 identifiers are syntactically equivalent,
and that it doesn't cause any problems in practice. and that it doesn't cause any problems in practice.
Appendix B. CHANGES SINCE RFC 4291 Appendix B. CHANGES SINCE RFC 4291
This document has the following changes from RFC4291, "IP Version 6 This document has the following changes from RFC4291, "IP Version 6
Addressing Architecture". Numbers identify the Internet-Draft Addressing Architecture". Numbers identify the Internet-Draft
version that the change was made.: version that the change was made.:
Working Group Internet Drafts Working Group Internet Drafts
03) Changes references in Section 2.4.1 that describes the
details of forming IIDs to RFC7271 and RFC7721.
02) Remove changes made by RFC7371 because there isn't any known 02) Remove changes made by RFC7371 because there isn't any known
implementation experience. implementation experience.
01) Revised Section 2.4.1 on Interface Identifiers to reflect 01) Revised Section 2.4.1 on Interface Identifiers to reflect
current approach, this included saying Modified EUI-64 current approach, this included saying Modified EUI-64
identifiers not recommended and moved the text describing the identifiers not recommended and moved the text describing the
format to Appendix A. format to Appendix A.
01) Editorial changes. 01) Editorial changes.
 End of changes. 9 change blocks. 
16 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/