draft-ietf-6man-rfc4291bis-04.txt   draft-ietf-6man-rfc4291bis-05.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: March 17, 2017 September 13, 2016 Expires: April 7, 2017 October 4, 2016
IP Version 6 Addressing Architecture IP Version 6 Addressing Architecture
draft-ietf-6man-rfc4291bis-04 draft-ietf-6man-rfc4291bis-05
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 March 17, 2017. This Internet-Draft will expire on April 7, 2017.
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 2, line 40 skipping to change at page 2, line 40
2.3. Address Type Identification . . . . . . . . . . . . . . . 9 2.3. Address Type Identification . . . . . . . . . . . . . . . 9
2.4. Unicast Addresses . . . . . . . . . . . . . . . . . . . . 10 2.4. Unicast Addresses . . . . . . . . . . . . . . . . . . . . 10
2.4.1. Interface Identifiers . . . . . . . . . . . . . . . . 11 2.4.1. Interface Identifiers . . . . . . . . . . . . . . . . 11
2.4.2. The Unspecified Address . . . . . . . . . . . . . . . 12 2.4.2. The Unspecified Address . . . . . . . . . . . . . . . 12
2.4.3. The Loopback Address . . . . . . . . . . . . . . . . 12 2.4.3. The Loopback Address . . . . . . . . . . . . . . . . 12
2.4.4. Global Unicast Addresses . . . . . . . . . . . . . . 12 2.4.4. Global Unicast Addresses . . . . . . . . . . . . . . 12
2.4.5. IPv6 Addresses with Embedded IPv4 Addresses . . . . . 13 2.4.5. IPv6 Addresses with Embedded IPv4 Addresses . . . . . 13
2.4.5.1. IPv4-Compatible IPv6 Address . . . . . . . . . . 13 2.4.5.1. IPv4-Compatible IPv6 Address . . . . . . . . . . 13
2.4.5.2. IPv4-Mapped IPv6 Address . . . . . . . . . . . . 13 2.4.5.2. IPv4-Mapped IPv6 Address . . . . . . . . . . . . 13
2.4.6. Link-Local IPv6 Unicast Addresses . . . . . . . . . . 14 2.4.6. Link-Local IPv6 Unicast Addresses . . . . . . . . . . 14
2.4.7. Site-Local IPv6 Unicast Addresses . . . . . . . . . . 14 2.4.7. Other Local Unicast IPv6 Addresses . . . . . . . . . 14
2.5. Anycast Addresses . . . . . . . . . . . . . . . . . . . . 14 2.5. Anycast Addresses . . . . . . . . . . . . . . . . . . . . 14
2.5.1. Required Anycast Address . . . . . . . . . . . . . . 15 2.5.1. Required Anycast Address . . . . . . . . . . . . . . 15
2.6. Multicast Addresses . . . . . . . . . . . . . . . . . . . 16 2.6. Multicast Addresses . . . . . . . . . . . . . . . . . . . 16
2.6.1. Pre-Defined Multicast Addresses . . . . . . . . . . . 19 2.6.1. Pre-Defined Multicast Addresses . . . . . . . . . . . 18
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 . . . . . . . . . . . . . . . . . . . 22
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21 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 . . . . . . . . . . . . . . . . . 23
Appendix A. Modified EUI-64 Format Interface Identifiers . . . . 24 Appendix A. Modified EUI-64 Format Interface Identifiers . . . . 25
A.1. Creating Modified EUI-64 Format Interface Identifiers . . 24 A.1. Creating Modified EUI-64 Format Interface Identifiers . . 26
Appendix B. CHANGES SINCE RFC 4291 . . . . . . . . . . . . . . . 27 Appendix B. CHANGES SINCE RFC 4291 . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
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 4, line 13 skipping to change at page 4, line 13
end with, zero-valued fields. end with, zero-valued fields.
2.1. Addressing Model 2.1. Addressing Model
IPv6 addresses of all types are assigned to interfaces, not nodes. IPv6 addresses of all types are assigned to interfaces, not nodes.
An IPv6 unicast address refers to a single interface. Since each An IPv6 unicast address refers to a single interface. Since each
interface belongs to a single node, any of that node's interfaces' interface belongs to a single node, any of that node's interfaces'
unicast addresses may be used as an identifier for the node. unicast addresses may be used as an identifier for the node.
All interfaces are required to have at least one Link-Local unicast All interfaces are required to have at least one Link-Local unicast
address (see Section 2.8 for additional required addresses). A address (see Section 2.7 for additional required addresses). A
single interface may also have multiple IPv6 addresses of any type single interface may also have multiple IPv6 addresses of any type
(unicast, anycast, and multicast) or scope. Unicast addresses with a (unicast, anycast, and multicast) or scope. Unicast addresses with a
scope greater than link-scope are not needed for interfaces that are scope greater than link-scope are not needed for interfaces that are
not used as the origin or destination of any IPv6 packets to or from not used as the origin or destination of any IPv6 packets to or from
non-neighbors. This is sometimes convenient for point-to-point non-neighbors. This is sometimes convenient for point-to-point
interfaces. There is one exception to this addressing model: interfaces. There is one exception to this addressing model:
A unicast address or a set of unicast addresses may be assigned to A unicast address or a set of unicast addresses may be assigned to
multiple physical interfaces if the implementation treats the multiple physical interfaces if the implementation treats the
multiple physical interfaces as one interface when presenting it multiple physical interfaces as one interface when presenting it
skipping to change at page 9, line 32 skipping to change at page 9, line 32
2001:0db8:0:cd30::/60 2001:0db8:0:cd30::/60
2.3. Address Type Identification 2.3. Address Type Identification
The type of an IPv6 address is identified by the high-order bits of The type of an IPv6 address is identified by the high-order bits of
the address, as follows: the address, as follows:
Address type Binary prefix IPv6 notation Section Address type Binary prefix IPv6 notation Section
------------ ------------- ------------- ------- ------------ ------------- ------------- -------
Unspecified 00...0 (128 bits) ::/128 2.5.2 Unspecified 00...0 (128 bits) ::/128 2.4.2
Loopback 00...1 (128 bits) ::1/128 2.5.3 Loopback 00...1 (128 bits) ::1/128 2.4.3
Multicast 11111111 ff00::/8 2.7 Multicast 11111111 ff00::/8 2.6
Link-Local unicast 1111111010 fe80::/10 2.5.6 Link-Local unicast 1111111010 fe80::/10 2.4.6
Global Unicast (everything else) Global Unicast (everything else)
Anycast addresses are taken from the unicast address spaces (of any Anycast addresses are taken from the unicast address spaces (of any
scope) and are not syntactically distinguishable from unicast scope) and are not syntactically distinguishable from unicast
addresses. addresses.
The general format of Global Unicast addresses is described in The general format of Global Unicast addresses is described in
Section 2.5.4. Some special-purpose subtypes of Global Unicast Section 2.4.4. Some special-purpose subtypes of Global Unicast
addresses that contain embedded IPv4 addresses (for the purposes of addresses that contain embedded IPv4 addresses (for the purposes of
IPv4-IPv6 interoperation) are described in Section 2.5.5. IPv4-IPv6 interoperation) are described in Section 2.4.5.
Future specifications may redefine one or more sub-ranges of the Future specifications may redefine one or more sub-ranges of the
Global Unicast space for other purposes, but unless and until that Global Unicast space for other purposes, but unless and until that
happens, implementations must treat all addresses that do not start happens, implementations must treat all addresses that do not start
with any of the above-listed prefixes as Global Unicast addresses. with any of the above-listed prefixes as Global Unicast addresses.
The current assigned IPv6 prefixes and references to their usage can The current assigned IPv6 prefixes and references to their usage can
be found in the IANA Internet Protocol Version 6 Address Space be found in the IANA Internet Protocol Version 6 Address Space
registry [IANA-AD] and the IANA IPv6 Special-Purpose Address Registry registry [IANA-AD] and the IANA IPv6 Special-Purpose Address Registry
[IANA-SP]. [IANA-SP].
2.4. Unicast Addresses 2.4. Unicast Addresses
IPv6 unicast addresses are aggregatable with prefixes of arbitrary IPv6 unicast addresses are aggregatable with prefixes of arbitrary
bit-length, similar to IPv4 addresses under Classless Inter-Domain bit-length, similar to IPv4 addresses under Classless Inter-Domain
Routing. Routing.
There are several types of unicast addresses in IPv6, in particular, There are several types of unicast addresses in IPv6, in particular,
Global Unicast, site-local unicast (deprecated, see Section 2.5.7), Global Unicast, Local unicast, and Link-Local unicast. There are
and Link-Local unicast. There are also some special-purpose subtypes also some special-purpose subtypes of Global Unicast, such as IPv6
of Global Unicast, such as IPv6 addresses with embedded IPv4 addresses with embedded IPv4 addresses. Additional address types or
addresses. Additional address types or subtypes can be defined in subtypes can be defined in the future.
the future.
IPv6 nodes may have considerable or little knowledge of the internal IPv6 nodes may have considerable or little knowledge of the internal
structure of the IPv6 address, depending on the role the node plays structure of the IPv6 address, depending on the role the node plays
(for instance, host versus router). At a minimum, a node may (for instance, host versus router). At a minimum, a node may
consider that unicast addresses (including its own) have no internal consider that unicast addresses (including its own) have no internal
structure: structure:
| 128 bits | | 128 bits |
+-----------------------------------------------------------------+ +-----------------------------------------------------------------+
| node address | | node address |
skipping to change at page 11, line 35 skipping to change at page 11, line 33
Interface IDs must be viewed outside of the node that created Interface IDs must be viewed outside of the node that created
Interface ID as an opaque bit string without any internal structure. Interface ID as an opaque bit string without any internal structure.
Note that the uniqueness of interface identifiers is independent of Note that the uniqueness of interface identifiers is independent of
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. Background
on the 64 bit boundary can be bound in [RFC7421].
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] or "A Method for Generating Autoconfiguration in IPv6" [RFC4941] or "A Method for Generating
Semantically Opaque Interface Identifiers with IPv6 Stateless Address Semantically Opaque Interface Identifiers with IPv6 Stateless Address
Autoconfiguration (SLAAC)"[RFC7217]. Specific cases are described in Autoconfiguration (SLAAC)"[RFC7217]. Specific cases are described in
appropriate "IPv6 over <link>" specifications, such as "IPv6 over appropriate "IPv6 over <link>" specifications, such as "IPv6 over
Ethernet" [RFC2464] and "Transmission of IPv6 Packets over ITU-T Ethernet" [RFC2464] and "Transmission of IPv6 Packets over ITU-T
G.9959 Networks" [RFC7428]. The security and privacy considerations G.9959 Networks" [RFC7428]. The security and privacy considerations
for IPv6 address generation is described in [RFC7721]. for IPv6 address generation is described in [RFC7721].
skipping to change at page 12, line 46 skipping to change at page 12, line 46
The general format for IPv6 Global Unicast addresses is as follows: The general format for IPv6 Global Unicast addresses is as follows:
| n bits | m bits | 128-n-m bits | | n bits | m bits | 128-n-m bits |
+------------------------+-----------+----------------------------+ +------------------------+-----------+----------------------------+
| global routing prefix | subnet ID | interface ID | | global routing prefix | subnet ID | interface ID |
+------------------------+-----------+----------------------------+ +------------------------+-----------+----------------------------+
where the global routing prefix is a (typically hierarchically- where the global routing prefix is a (typically hierarchically-
structured) value assigned to a site (a cluster of subnets/links), structured) value assigned to a site (a cluster of subnets/links),
the subnet ID is an identifier of a link within the site, and the the subnet ID is an identifier of a link within the site, and the
interface ID is as defined in Section 2.5.1. interface ID is as defined in Section 2.4.1.
All Global Unicast addresses other than those that start with binary All Global Unicast addresses other than those that start with binary
000 have a 64-bit interface ID field (i.e., n + m = 64), formatted as 000 have a 64-bit interface ID field (i.e., n + m = 64), formatted as
described in Section 2.5.1. Global Unicast addresses that start with described in Section 2.4.1. Global Unicast addresses that start with
binary 000 have no such constraint on the size or structure of the binary 000 have no such constraint on the size or structure of the
interface ID field. interface ID field.
Examples of Global Unicast addresses that start with binary 000 are Examples of Global Unicast addresses that start with binary 000 are
the IPv6 address with embedded IPv4 addresses described in the IPv6 address with embedded IPv4 addresses described in
Section 2.5.5. An example of global addresses starting with a binary Section 2.4.5. An example of global addresses starting with a binary
value other than 000 (and therefore having a 64-bit interface ID value other than 000 (and therefore having a 64-bit interface ID
field) can be found in [RFC3587]. field) can be found in [RFC3587].
2.4.5. IPv6 Addresses with Embedded IPv4 Addresses 2.4.5. IPv6 Addresses with Embedded IPv4 Addresses
Two types of IPv6 addresses are defined that carry an IPv4 address in Two types of IPv6 addresses are defined that carry an IPv4 address in
the low-order 32 bits of the address. These are the "IPv4-Compatible the low-order 32 bits of the address. These are the "IPv4-Compatible
IPv6 address" and the "IPv4-mapped IPv6 address". IPv6 address" and the "IPv4-mapped IPv6 address".
2.4.5.1. IPv4-Compatible IPv6 Address 2.4.5.1. IPv4-Compatible IPv6 Address
skipping to change at page 14, line 23 skipping to change at page 14, line 23
|1111111010| 0 | interface ID | |1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+ +----------+-------------------------+----------------------------+
Link-Local addresses are designed to be used for addressing on a Link-Local addresses are designed to be used for addressing on a
single link for purposes such as automatic address configuration, single link for purposes such as automatic address configuration,
neighbor discovery, or when no routers are present. neighbor discovery, or when no routers are present.
Routers must not forward any packets with Link-Local source or Routers must not forward any packets with Link-Local source or
destination addresses to other links. destination addresses to other links.
2.4.7. Site-Local IPv6 Unicast Addresses 2.4.7. Other Local Unicast IPv6 Addresses
Site-Local addresses were originally designed to be used for
addressing inside of a site without the need for a global prefix.
Site-local addresses are now deprecated as defined in [RFC3879].
Site-Local addresses have the following format: Unique Local Addresses (ULA) [RFC4193], the current form of Local
IPv6 Addresses, are intended to be used for local communications,
have global unicast scope, and are not expected to be routable on the
global Internet.
| 10 | Site-Local addresses, deprecated by [RFC3879], the previous form of
| bits | 54 bits | 64 bits | Local IPv6 Addresses, were originally designed to be used for
+----------+-------------------------+----------------------------+ addressing inside of a site without the need for a global prefix.
|1111111011| subnet ID | interface ID |
+----------+-------------------------+----------------------------+
The special behavior of this prefix defined in [RFC3513] must no The special behavior of Site-Local defined in [RFC3513] must no
longer be supported in new implementations (i.e., new implementations longer be supported in new implementations (i.e., new implementations
must treat this prefix as Global Unicast). must treat this prefix as Global Unicast). Existing implementations
and deployments may continue to use this prefix.
Existing implementations and deployments may continue to use this
prefix.
A new type of address has been defined that can be generated locally
and is intended to be used as an alternative to Site-Local addresses.
These are called Unique Local Addresses (ULA) [RFC4193].
2.5. Anycast Addresses 2.5. Anycast Addresses
An IPv6 anycast address is an address that is assigned to more than An IPv6 anycast address is an address that is assigned to more than
one interface (typically belonging to different nodes), with the one interface (typically belonging to different nodes), with the
property that a packet sent to an anycast address is routed to the property that a packet sent to an anycast address is routed to the
"nearest" interface having that address, according to the routing "nearest" interface having that address, according to the routing
protocols' measure of distance. protocols' measure of distance.
Anycast addresses are allocated from the unicast address space, using Anycast addresses are allocated from the unicast address space, using
skipping to change at page 20, line 48 skipping to change at page 20, line 40
identifying itself: identifying itself:
o Its required Link-Local address for each interface. o Its required Link-Local address for each interface.
o Any additional Unicast and Anycast addresses that have been o Any additional Unicast and Anycast addresses that have been
configured for the node's interfaces (manually or configured for the node's interfaces (manually or
automatically). automatically).
o The loopback address. o The loopback address.
o The All-Nodes multicast addresses defined in Section 2.7.1. o The All-Nodes multicast addresses defined in Section 2.6.1.
o The Solicited-Node multicast address for each of its unicast o The Solicited-Node multicast address for each of its unicast
and anycast addresses. and anycast addresses.
o Multicast addresses of all other groups to which the node o Multicast addresses of all other groups to which the node
belongs. belongs.
A router is required to recognize all addresses that a host is A router is required to recognize all addresses that a host is
required to recognize, plus the following addresses as identifying required to recognize, plus the following addresses as identifying
itself: itself:
o The Subnet-Router Anycast addresses for all interfaces for o The Subnet-Router Anycast addresses for all interfaces for
which it is configured to act as a router. which it is configured to act as a router.
o All other Anycast addresses with which the router has been o All other Anycast addresses with which the router has been
configured. configured.
o The All-Routers multicast addresses defined in Section 2.7.1. o The All-Routers multicast addresses defined in Section 2.6.1.
3. IANA Considerations 3. IANA Considerations
This document does not contain any IANA Considerations. RFC4291 is referenced in a number of IANA registries. These include:
o Internet Protocol Version 6 Address Space [IANA-AD]
o IPv6 Global Unicast Address Assignments [IANA-GU]
o IPv6 Multicast Address Space Registry [IANA-MC]
o Application for an IPv6 Multicast Address [IANA-MA]
o Internet Protocol Version 6 (IPv6) Anycast Addresses [IANA-AC]
o IANA IPv6 Special-Purpose Address Registry [IANA-SP]
o Reserved IPv6 Interface Identifiers [IANA-ID]
o Number Resources [IANA-NR]
o Protocol Registries [IANA-PR]
o Technical requirements for authoritative name servers [IANA-NS]
o IP Flow Information Export (IPFIX) Entities [IANA-FE]
The IANA should update these references to point to this document.
There is a reference to RFC4291 (and RFC3307) that appears to be
incorrect and should be removed in:
o Modify a Port Number assignment [IANA-PN]
There are also other references in IANA procedures documents that the
IANA should investigate to see if they should be updated.
4. Security Considerations 4. Security Considerations
IPv6 addressing documents do not have any direct impact on Internet IPv6 addressing documents do not have any direct impact on Internet
infrastructure security. Authentication of IPv6 packets is defined infrastructure security. Authentication of IPv6 packets is defined
in [RFC4302]. in [RFC4302].
One area relavant to IPv6 addressing is privacy. IPv6 addresses can
be created using interface identifiers constructed with unique stable
tokens. The addresses created in this manner can be used to track
the movement of devices across the Internet. Since earlier versions
of this document were published, several approaches have been
developed that mitigate these problems. These are described in
"Security and Privacy Considerations for IPv6 Address Generation
Mechanisms" [RFC7721], "Privacy Extensions for Stateless Address
Autoconfiguration in IPv6" [RFC4941], and "A Method for Generating
Semantically Opaque Interface Identifiers with IPv6 Stateless Address
Autoconfiguration (SLAAC)"[RFC7217].
5. Acknowledgments 5. Acknowledgments
The authors would like to acknowledge the contributions of Paul The authors would like to acknowledge the contributions of Paul
Francis, Scott Bradner, Jim Bound, Brian Carpenter, Matt Crawford, Francis, Scott Bradner, Jim Bound, Brian Carpenter, Matt Crawford,
Deborah Estrin, Roger Fajman, Bob Fink, Peter Ford, Bob Gilligan, Deborah Estrin, Roger Fajman, Bob Fink, Peter Ford, Bob Gilligan,
Dimitry Haskin, Tom Harsch, Christian Huitema, Tony Li, Greg Dimitry Haskin, Tom Harsch, Christian Huitema, Tony Li, Greg
Minshall, Thomas Narten, Erik Nordmark, Yakov Rekhter, Bill Simpson, Minshall, Thomas Narten, Erik Nordmark, Yakov Rekhter, Bill Simpson,
Sue Thomson, Markku Savela, Larry Masinter, Jun-ichiro Itojun Hagino, Sue Thomson, Markku Savela, Larry Masinter, Jun-ichiro Itojun Hagino,
Tatuya Jinmei, Suresh Krishnan, and Mahmood Ali. Tatuya Jinmei, Suresh Krishnan, and Mahmood Ali.
skipping to change at page 22, line 10 skipping to change at page 22, line 50
to move IPv6 to Internet Standard. This includes Marcelo Bagnulo, to move IPv6 to Internet Standard. This includes Marcelo Bagnulo,
Congxiao Bao, Mohamed Boucadair, Brian Carpenter, Ralph Droms, Congxiao Bao, Mohamed Boucadair, Brian Carpenter, Ralph Droms,
Christian Huitema, Sheng Jiang, Seiichi Kawamura, Masanobu Kawashima, Christian Huitema, Sheng Jiang, Seiichi Kawamura, Masanobu Kawashima,
Xing Li, and Stig Venaas. Xing Li, and Stig Venaas.
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-6man-rfc2460bis] [I-D.ietf-6man-rfc2460bis]
Deering, D. and R. Hinden, "Internet Protocol, Version 6 Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", draft-ietf-6man-rfc2460bis-05 (work (IPv6) Specification", draft-ietf-6man-rfc2460bis-07 (work
in progress), June 2016. in progress), October 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>.
[IANA-AC] "Internet Protocol Version 6 (IPv6) Anycast Addresses",
<http://www.iana.org/assignments/ipv6-anycast-addresses/
ipv6-anycast-addresses.xhtml>.
[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-FE] "IP Flow Information Export (IPFIX) Entities",
<http://www.iana.org/assignments/ipfix/ipfix.xhtml>.
[IANA-GU] "IPv6 Global Unicast Address Assignments",
<http://www.iana.org/assignments/ipv6-unicast-address-
assignments/ipv6-unicast-address-assignments.xhtml>.
[IANA-ID] "IANA IPv6 Special-Purpose Address Registry",
<http://www.iana.org/assignments/ipv6-interface-ids/
ipv6-interface-ids.xhtml>.
[IANA-MA] "Application for an IPv6 Multicast Address",
<https://www.iana.org/form/multicast-ipv6>.
[IANA-MC] "IPv6 Multicast Address Space Registry",
<http://www.iana.org/assignments/ipv6-multicast-addresses/
ipv6-multicast-addresses.xhtml>.
[IANA-NR] "Number Resources", <http://https://www.iana.org/numbers>.
[IANA-NS] "Technical requirements for authoritative name servers",
<https://www.iana.org/help/nameserver-requirements>.
[IANA-PN] "Modify a Port Number assignment",
<https://www.iana.org/form/port-modification>.
[IANA-PR] "Protocol Registries", <https://www.iana.org/protocols>.
[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,
<http://www.rfc-editor.org/info/rfc2464>. <http://www.rfc-editor.org/info/rfc2464>.
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6
Multicast Addresses", RFC 3306, DOI 10.17487/RFC3306, Multicast Addresses", RFC 3306, DOI 10.17487/RFC3306,
skipping to change at page 23, line 44 skipping to change at page 25, line 16
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 [RFC7217] Gont, F., "A Method for Generating Semantically Opaque
Interface Identifiers with IPv6 Stateless Address Interface Identifiers with IPv6 Stateless Address
Autoconfiguration (SLAAC)", RFC 7217, DOI 10.17487/ Autoconfiguration (SLAAC)", RFC 7217, DOI 10.17487/
RFC7217, April 2014, RFC7217, April 2014,
<http://www.rfc-editor.org/info/rfc7217>. <http://www.rfc-editor.org/info/rfc7217>.
[RFC7421] Carpenter, B., Ed., Chown, T., Gont, F., Jiang, S.,
Petrescu, A., and A. Yourtchenko, "Analysis of the 64-bit
Boundary in IPv6 Addressing", RFC 7421, DOI 10.17487/
RFC7421, January 2015,
<http://www.rfc-editor.org/info/rfc7421>.
[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 [RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy
Considerations for IPv6 Address Generation Mechanisms", Considerations for IPv6 Address Generation Mechanisms",
RFC 7721, DOI 10.17487/RFC7721, March 2016, RFC 7721, DOI 10.17487/RFC7721, March 2016,
<http://www.rfc-editor.org/info/rfc7721>. <http://www.rfc-editor.org/info/rfc7721>.
skipping to change at page 27, line 41 skipping to change at page 29, line 21
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
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
rewrote the text to point to ULAs and say that Site-Local
addresses were deprecated by RFC3879. The format of Site-
Local was removed.
05) Added to Section 2.4.1 a reference to RFC7421 regarding the
background on the 64 bit boundary in Interface Identifiers.
05) Editorial changes.
04) Added text and a pointer to the ULA specification in 04) Added text and a pointer to the ULA specification in
Section 2.4.7 Section 2.4.7
04) Removed old IANA Considerations text, this was left from the 04) Removed old IANA Considerations text, this was left from the
baseline text from RFC4291 and should have been removed baseline text from RFC4291 and should have been removed
earlier. earlier.
04) Editorial changes. 04) Editorial changes.
03) Changes references in Section 2.4.1 that describes the 03) Changes references in Section 2.4.1 that describes the
 End of changes. 31 change blocks. 
54 lines changed or deleted 145 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/