< draft-ietf-ipv6-addr-arch-v4-01.txt		draft-ietf-ipv6-addr-arch-v4-02.txt >
	INTERNET-DRAFT R. Hinden, Nokia		INTERNET-DRAFT R. Hinden, Nokia
	February 17, 2005 S. Deering, Cisco Systems		March 23, 2005 S. Deering, Cisco Systems
	IP Version 6 Addressing Architecture		IP Version 6 Addressing Architecture
	<draft-ietf-ipv6-addr-arch-v4-01.txt>		<draft-ietf-ipv6-addr-arch-v4-02.txt>
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, I certify that any applicable		By submitting this Internet-Draft, I certify that any applicable
	patent or other IPR claims of which I am aware have been disclosed,		patent or other IPR claims of which I am aware have been disclosed,
	or will be disclosed, and any of which I become aware will be		or will be disclosed, and any of which I become aware will be
	disclosed, in accordance with RFC 3668.		disclosed, in accordance with RFC 3668.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 33 ¶		skipping to change at page 1, line 33 ¶
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/1id-abstracts.html		http://www.ietf.org/1id-abstracts.html
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet Draft expires August 22, 2005.		This Internet Draft expires September 28, 2005.
	Abstract		Abstract
	This specification defines the addressing architecture of the IP		This specification defines the addressing architecture of the IP
	Version 6 protocol [IPV6]. The document includes the IPv6 addressing		Version 6 protocol [IPV6]. 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-3513 "IP Version 6 Addressing		This document obsoletes RFC-3513 "IP Version 6 Addressing
	skipping to change at page 2, line 22 ¶		skipping to change at page 2, line 22 ¶
	2.3 Text Representation of Address Prefixes..................5		2.3 Text Representation of Address Prefixes..................5
	2.4 Address Type Identification..............................7		2.4 Address Type Identification..............................7
	2.5 Unicast Addresses........................................7		2.5 Unicast Addresses........................................7
	2.5.1 Interface Identifiers................................8		2.5.1 Interface Identifiers................................8
	2.5.2 The Unspecified Address.............................10		2.5.2 The Unspecified Address.............................10
	2.5.3 The Loopback Address................................10		2.5.3 The Loopback Address................................10
	2.5.4 Global Unicast Addresses............................10		2.5.4 Global Unicast Addresses............................10
	2.5.5 IPv6 Addresses with Embedded IPv4 Addresses.........11		2.5.5 IPv6 Addresses with Embedded IPv4 Addresses.........11
	2.5.6 Link-Local IPv6 Unicast Addresses...................12		2.5.6 Link-Local IPv6 Unicast Addresses...................12
	2.5.7 Site-Local IPv6 Unicast Addresses...................12		2.5.7 Site-Local IPv6 Unicast Addresses...................12
	2.6 Anycast Addresses.......................................12		2.6 Anycast Addresses.......................................13
	2.6.1 Required Anycast Address............................14		2.6.1 Required Anycast Address............................14
	2.7 Multicast Addresses.....................................14		2.7 Multicast Addresses.....................................14
	2.7.1 Pre-Defined Multicast Addresses.....................16		2.7.1 Pre-Defined Multicast Addresses.....................17
	2.8 A Node's Required Addresses.............................18		2.8 A Node's Required Addresses.............................18
	3. Security Considerations.....................................18		3. Security Considerations.....................................19
	4. IANA Considerations.........................................19		4. IANA Considerations.........................................19
	5. References..................................................19		5. References..................................................19
	6. Author's Addresses..........................................20		6. Author's Addresses..........................................20
	7. Disclaimer of Validity......................................20		7. Disclaimer of Validity......................................21
	8. Copyright Statement.........................................20		8. Copyright Statement.........................................21
	9. Intellectual Property.......................................21		9. Intellectual Property.......................................21
	APPENDIX A: Creating Modified EUI-64 format Interface IDs......22		APPENDIX A: Creating Modified EUI-64 format Interface IDs......22
	APPENDIX B: Changes from RFC-3513..............................25		APPENDIX B: Changes from RFC-3513..............................25
	1.0 INTRODUCTION		1.0 INTRODUCTION
	This specification defines the addressing architecture of the IP		This specification defines the addressing architecture of the IP
	skipping to change at page 11, line 19 ¶		skipping to change at page 11, line 19 ¶
	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 Section		the IPv6 address with embedded IPv4 addresses described in Section
	2.5.5. An example of global addresses starting with a binary value		2.5.5. An example of global addresses starting with a binary value
	other than 000 (and therefore having a 64-bit interface ID field) can		other than 000 (and therefore having a 64-bit interface ID field) can
	be found in [GLOBAL].		be found in [GLOBAL].
	2.5.5 IPv6 Addresses with Embedded IPv4 Addresses		2.5.5 IPv6 Addresses with Embedded IPv4 Addresses
	The IPv6 transition mechanisms [TRAN] include a technique for hosts		Two types of IPv6 addresses are defined that carry an IPv4 address in
	and routers to dynamically tunnel IPv6 packets over IPv4 routing		the low-order 32 bits of the address. These are the "IPv4-Compatible
	infrastructure. IPv6 nodes that use this technique are assigned		IPv6 Address" and the "IPv4-Mapped IPv6 Address".
	special IPv6 unicast addresses that carry a global IPv4 address in
	the low-order 32 bits. This type of address is termed an		2.5.5.1 IPv4-Compatible IPv6 Address
	"IPv4-compatible IPv6 address" and has the format:
			The "IPv4-compatible IPv6 address", was defined to assist in the IPv6
			transition. The format of the "IPv4-compatible IPv6 address" is:
	| 80 bits | 16 | 32 bits |		| 80 bits | 16 | 32 bits |
	+--------------------------------------+--------------------------+		+--------------------------------------+--------------------------+
	|0000..............................0000|0000| IPv4 address |		|0000..............................0000|0000| IPv4 address |
	+--------------------------------------+----+---------------------+		+--------------------------------------+----+---------------------+
	Note: The IPv4 address used in the "IPv4-compatible IPv6 address"		Note: The IPv4 address used in the "IPv4-compatible IPv6 address"
	must be a globally-unique IPv4 unicast address.		must be a globally-unique IPv4 unicast address.
	A second type of IPv6 address which holds an embedded IPv4 address is		The "IPv4-compatible IPv6 address" is now deprecated because the
	also defined. This address type is used to represent the addresses		current IPv6 transition mechanisms no longer use these addresses.
	of IPv4 nodes as IPv6 addresses. This type of address is termed an		New or updated implementations are not required to support this
	"IPv4-mapped IPv6 address" and has the format:		address type.
			2.5.5.2 IPv4-Mapped IPv6 Address
			A second type of IPv6 address that holds an embedded IPv4 address is
			defined. This address type is used to represent the addresses of
			IPv4 nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6
			address" is:
	| 80 bits | 16 | 32 bits |		| 80 bits | 16 | 32 bits |
	+--------------------------------------+--------------------------+		+--------------------------------------+--------------------------+
	|0000..............................0000|FFFF| IPv4 address |		|0000..............................0000|FFFF| IPv4 address |
	+--------------------------------------+----+---------------------+		+--------------------------------------+----+---------------------+
			See [RFC4038] for background on the usage of the "IPv4-mapped IPv6
			address".
	2.5.6 Link-Local IPv6 Unicast Addresses		2.5.6 Link-Local IPv6 Unicast Addresses
	Link-Local addresses are for use on a single link. Link-Local		Link-Local addresses are for use on a single link. Link-Local
	addresses have the following format:		addresses have the following format:
	| 10 |		| 10 |
	| bits | 54 bits | 64 bits |		| bits | 54 bits | 64 bits |
	+----------+-------------------------+----------------------------+		+----------+-------------------------+----------------------------+
	|1111111010| 0 | interface ID |		|1111111010| 0 | interface ID |
	+----------+-------------------------+----------------------------+		+----------+-------------------------+----------------------------+
	skipping to change at page 15, line 36 ¶		skipping to change at page 15, line 43 ¶
	B (unassigned)		B (unassigned)
	C (unassigned)		C (unassigned)
	D (unassigned)		D (unassigned)
	E global scope		E global scope
	F reserved		F reserved
	interface-local scope spans only a single interface on a		interface-local scope spans only a single interface on a
	node, and is useful only for loopback transmission of		node, and is useful only for loopback transmission of
	multicast.		multicast.
	link-local and site-local multicast scopes span the same		link-local multicast scope spans the same
	topological regions as the corresponding unicast scopes.		topological region as the corresponding unicast scope.
	admin-local scope is the smallest scope that must be		admin-local scope is the smallest scope that must be
	administratively configured, i.e., not automatically		administratively configured, i.e., not automatically
	derived from physical connectivity or other, non-		derived from physical connectivity or other, non-
	multicast-related configuration.		multicast-related configuration.
			site-local scope is intended to span a single site.
	organization-local scope is intended to span multiple		organization-local scope is intended to span multiple
	sites belonging to a single organization.		sites belonging to a single organization.
	scopes labeled "(unassigned)" are available for		scopes labeled "(unassigned)" are available for
	administrators to define additional multicast regions.		administrators to define additional multicast regions.
	group ID identifies the multicast group, either permanent or		group ID identifies the multicast group, either permanent or
	transient, within the given scope.		transient, within the given scope.
	The "meaning" of a permanently-assigned multicast address is		The "meaning" of a permanently-assigned multicast address is
	skipping to change at page 19, line 7 ¶		skipping to change at page 19, line 13 ¶
	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. Security Considerations		3. 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 [AUTH].		in [AUTH].
	4. IANA Considerations		4. IANA Considerations
	None.		The "IPv4-compatible IPv6 address" is deprecated by this document.
			The IANA should continue to list the address block containing this
			address as "Reserved by IETF" and not reassign it for any other
			purpose.
			The IANA should update the references for the IPv6 Address
			Architecture in the IANA registries to this RFC when it is published.
	5. References		5. References
	5.1 Normative References		5.1 Normative References
	[IPV6] Deering, S., R. Hinden, "Internet Protocol, Version 6		[IPV6] Deering, S. and R. Hinden, "Internet Protocol, Version 6
	(IPv6) Specification", RFC2460, December 1998.		(IPv6) Specification", RFC2460, December 1998.
	[RFC2026] Bradner, S., "The Internet Standards Process -- Revision		[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
	3", RFC2026, BCP00009, October 1996.		3", RFC2026, BCP00009, October 1996.
	[SLDEP] C. Huitema, B. Carpenter, "Deprecating Site Local
	Addresses", RFC3879, September 2004.
	5.2 Non-Normative References		5.2 Non-Normative References
	[ANYCST] Partridge, C., T. Mendez, and W. Milliken, "Host Anycasting		[ANYCST] Partridge, C., Mendez, T., and W. Milliken, "Host
	Service", RFC1546, November 1993.		Anycasting Service", RFC1546, November 1993.
	[AUTH] Kent, S., R. Atkinson, "IP Authentication Header", RFC2402,		[AUTH] Kent, S., and R. Atkinson, "IP Authentication Header",
	November 1998.		RFC2402, November 1998.
	[CIDR] Fuller, V., Li, T., Yu, J., Varadhan, K., "Classless Inter-		[CIDR] Fuller, V., Li, T., Yu, J., and K. Varadhan, "Classless
	Domain Routing (CIDR): An Address Assignment and		Inter-Domain Routing (CIDR): An Address Assignment and
	Aggregation Strategy", RFC1519, September 1993.		Aggregation Strategy", RFC1519, September 1993.
	[ETHER] Crawford, M., "Transmission of IPv6 Packets over Ethernet		[ETHER] Crawford, M., "Transmission of IPv6 Packets over Ethernet
	Networks", RFC2464, December 1998.		Networks", RFC2464, December 1998.
	[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)		[EUI64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
	Registration Authority",		Registration Authority",
	http://standards.ieee.org/regauth/oui/tutorials/EUI64.html		http://standards.ieee.org/regauth/oui/tutorials/EUI64.html
	, March 1997.		, March 1997.
	[FDDI] Crawford, M., "Transmission of IPv6 Packets over FDDI		[FDDI] Crawford, M., "Transmission of IPv6 Packets over FDDI
	Networks", RFC2467, December 1998.		Networks", RFC2467, December 1998.
	[GLOBAL] Hinden, R., S. Deering, E. Nordmark, "IPv6 Global Unicast		[GLOBAL] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global
	Address Format", RFC3587, August 2003.		Unicast Address Format", RFC3587, August 2003.
	[MASGN] Hinden, R., "IPv6 Multicast Address Assignments", RFC2375,		[MASGN] Hinden, R., "IPv6 Multicast Address Assignments", RFC2375,
	July 1998.		July 1998.
	[PRIV] Narten, T., R. Draves, "Privacy Extensions for Stateless		[PRIV] Narten, T. and R. Draves, "Privacy Extensions for Stateless
	Address Autoconfiguration in IPv6", RFC3041, January 2001.		Address Autoconfiguration in IPv6", RFC3041, January 2001.
	[TOKEN] Crawford, M., T. Narten, S. Thomas, "Transmission of IPv6		[RFC4038] Shin, M-K., et. al., "Application Aspects of IPv6
	Packets over Token Ring Networks", RFC2470, December 1998.		Transition", RFC4038, March 2005.
	[TRAN] Gilligan, R., E. Nordmark, "Transition Mechanisms for IPv6		[SLDEP] Huitema, C. and B. Carpenter, "Deprecating Site Local
	Hosts and Routers", RFC2893, August 2000.		Addresses", RFC3879, September 2004.
			[TOKEN] Crawford, M., Narten, T., and S. Thomas, "Transmission of
			IPv6 Packets over Token Ring Networks", RFC2470, December
			1998.
			[TRAN] Gilligan, R. and E. Nordmark, "Transition Mechanisms for
			IPv6 Hosts and Routers", RFC2893, August 2000.
	6. Author's Addresses		6. Author's Addresses
	Robert M. Hinden		Robert M. Hinden
	Nokia		Nokia
	313 Fairchild Drive		313 Fairchild Drive
	Mountain View, CA 94043		Mountain View, CA 94043
	USA		USA
	phone: +1 650 625-2004		phone: +1 650 625-2004
	skipping to change at page 25, line 11 ¶		skipping to change at page 25, line 11 ¶
	in the appropriate "IPv6 over <link>" specification. It is strongly		in the appropriate "IPv6 over <link>" specification. It is strongly
	recommended that a collision detection algorithm be implemented as		recommended that a collision detection algorithm be implemented as
	part of any automatic algorithm.		part of any automatic algorithm.
	APPENDIX B: Changes from RFC-3513		APPENDIX B: Changes from RFC-3513
	---------------------------------		---------------------------------
	The following changes were made from RFC-3513 "IP Version 6		The following changes were made from RFC-3513 "IP Version 6
	Addressing Architecture":		Addressing Architecture":
	o Deprecated the Site-Local prefix. Changes included		o Deprecated the Site-Local unicast prefix. Changes included
	- Removed Site-Local from special list of prefixes in Section		- Removed Site-Local from special list of prefixes in Section
	2.4.		2.4.
	- Split section titled "Local-use IPv6 Unicast Addresses" into		- Split section titled "Local-use IPv6 Unicast Addresses" into
	two sections, "Link-Local IPv6 Unicast Addresses" and "Site-		two sections, "Link-Local IPv6 Unicast Addresses" and "Site-
	Local IPv6 Unicast Addresses".		Local IPv6 Unicast Addresses".
	- Added text to new section describing Site-Local deprecation.		- Added text to new section describing Site-Local deprecation.
	o Changes to resolve issues raised in IAB response to Robert Elz		o Changes to resolve issues raised in IAB response to Robert Elz
	appeal. Changes include:		appeal. Changes include:
	- Added clarification to Section 2.5 that nodes should make no		- Added clarification to Section 2.5 that nodes should make no
	skipping to change at page 25, line 38 ¶		skipping to change at page 25, line 38 ¶
	modified EUI-64 format with the "u" bit set to one are unique.		modified EUI-64 format with the "u" bit set to one are unique.
	o Changed the reference indicated in Section 2.5.4 "Global Unicast		o Changed the reference indicated in Section 2.5.4 "Global Unicast
	Addresses" to RFC3587.		Addresses" to RFC3587.
	o Removed mention of NSAP addresses in examples.		o Removed mention of NSAP addresses in examples.
	o Clarified that the "x" in the textual representation can be one to		o Clarified that the "x" in the textual representation can be one to
	four digits.		four digits.
			o Deprecated the "IPv6 Compatible Address" because it is not being
			used in the IPv6 transition mechanisms.
	o Editorial changes.		o Editorial changes.
End of changes. 25 change blocks.
	39 lines changed or deleted		66 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/