draft-ietf-6man-rfc4291bis-03.txt   draft-ietf-6man-rfc4291bis-04.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: December 30, 2016 June 28, 2016 Expires: March 17, 2017 September 13, 2016
IP Version 6 Addressing Architecture IP Version 6 Addressing Architecture
draft-ietf-6man-rfc4291bis-03 draft-ietf-6man-rfc4291bis-04
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 December 30, 2016. This Internet-Draft will expire on March 17, 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 48 skipping to change at page 2, line 48
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. Site-Local IPv6 Unicast 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 . . . . . . . . . . . 19
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 . . . . . . . . . . . . . . . . . . . . . . . 21
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 . . 24
Appendix B. CHANGES SINCE RFC 4291 . . . . . . . . . . . . . . . 28 Appendix B. CHANGES SINCE RFC 4291 . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 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
skipping to change at page 14, line 44 skipping to change at page 14, line 44
|1111111011| subnet ID | interface ID | |1111111011| subnet ID | interface ID |
+----------+-------------------------+----------------------------+ +----------+-------------------------+----------------------------+
The special behavior of this prefix defined in [RFC3513] must no The special behavior of this prefix 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 Existing implementations and deployments may continue to use this
prefix. 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
any of the defined unicast address formats. Thus, anycast addresses any of the defined unicast address formats. Thus, anycast addresses
skipping to change at page 21, line 22 skipping to change at page 21, line 25
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.7.1.
3. IANA Considerations 3. IANA Considerations
The "IPv4-Compatible IPv6 address" is deprecated by this document. This document does not contain any IANA Considerations.
The IANA should continue to list the address block containing these
addresses at http://www.iana.org/assignments/ipv6-address-space as
"Reserved by IETF" and not reassign it for any other purpose. For
example:
0000::/8 Reserved by IETF [RFC3513] [1]
The IANA has added the following note and link to this address block.
[5] 0000::/96 was previously defined as the "IPv4-Compatible IPv6
address" prefix. This definition has been deprecated by
[RFC4291].
The IANA has updated the references for the IPv6 Address Architecture
in the IANA registries accordingly.
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].
5. Acknowledgments 5. Acknowledgments
The authors would like to acknowledge the contributions of Paul The authors would like to acknowledge the contributions of Paul
skipping to change at page 22, line 27 skipping to change at page 22, line 10
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, S. and R. Hinden, "Internet Protocol, Version 6 Deering, D. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", draft-ietf-6man-rfc2460bis-04 (work (IPv6) Specification", draft-ietf-6man-rfc2460bis-05 (work
in progress), March 2016. in progress), June 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-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-
skipping to change at page 23, line 33 skipping to change at page 23, line 20
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, DOI B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, DOI
10.17487/RFC4007, March 2005, 10.17487/RFC4007, March 2005,
<http://www.rfc-editor.org/info/rfc4007>. <http://www.rfc-editor.org/info/rfc4007>.
[RFC4038] Shin, M-K., Ed., Hong, Y-G., Hagino, J., Savola, P., and [RFC4038] Shin, M-K., Ed., Hong, Y-G., Hagino, J., Savola, P., and
E. Castro, "Application Aspects of IPv6 Transition", RFC E. Castro, "Application Aspects of IPv6 Transition", RFC
4038, DOI 10.17487/RFC4038, March 2005, 4038, DOI 10.17487/RFC4038, March 2005,
<http://www.rfc-editor.org/info/rfc4038>. <http://www.rfc-editor.org/info/rfc4038>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Architecture", RFC 4291, DOI 10.17487/RFC4291, February Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005,
2006, <http://www.rfc-editor.org/info/rfc4291>. <http://www.rfc-editor.org/info/rfc4193>.
[RFC4302] Kent, S., "IP Authentication Header", RFC 4302, DOI [RFC4302] Kent, S., "IP Authentication Header", RFC 4302, DOI
10.17487/RFC4302, December 2005, 10.17487/RFC4302, December 2005,
<http://www.rfc-editor.org/info/rfc4302>. <http://www.rfc-editor.org/info/rfc4302>.
[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>.
skipping to change at page 28, line 13 skipping to change at page 27, line 41
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
04) Added text and a pointer to the ULA specification in
Section 2.4.7
04) Removed old IANA Considerations text, this was left from the
baseline text from RFC4291 and should have been removed
earlier.
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
details of forming IIDs to RFC7271 and RFC7721. 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.
 End of changes. 10 change blocks. 
28 lines changed or deleted 26 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/