< draft-ietf-ipv6-addr-arch-v4-02.txt		draft-ietf-ipv6-addr-arch-v4-03.txt >
	INTERNET-DRAFT R. Hinden, Nokia		INTERNET-DRAFT R. Hinden, Nokia
	March 23, 2005 S. Deering, Cisco Systems		April 29, 2005 S. Deering, Cisco Systems
	IP Version 6 Addressing Architecture		IP Version 6 Addressing Architecture
	<draft-ietf-ipv6-addr-arch-v4-02.txt>		<draft-ietf-ipv6-addr-arch-v4-03.txt>
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, I certify that any applicable		By submitting this Internet-Draft, each author represents that any
	patent or other IPR claims of which I am aware have been disclosed,		applicable patent or other IPR claims of which he or she is aware
	or will be disclosed, and any of which I become aware will be		have been or will be disclosed, and any of which he or she becomes
	disclosed, in accordance with RFC 3668.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	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."
	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 September 28, 2005.		This Internet Draft expires November 3, 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 23 ¶		skipping to change at page 2, line 23 ¶
	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.......................................13		2.6 Anycast Addresses.......................................13
	2.6.1 Required Anycast Address............................14		2.6.1 Required Anycast Address............................13
	2.7 Multicast Addresses.....................................14		2.7 Multicast Addresses.....................................14
	2.7.1 Pre-Defined Multicast Addresses.....................17		2.7.1 Pre-Defined Multicast Addresses.....................16
	2.8 A Node's Required Addresses.............................18		2.8 A Node's Required Addresses.............................18
	3. Security Considerations.....................................19		3. Security Considerations.....................................18
	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......................................21		7. Disclaimer of Validity......................................20
	8. Copyright Statement.........................................21		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
	skipping to change at page 13, line 47 ¶		skipping to change at page 13, line 47 ¶
	One expected use of anycast addresses is to identify the set of		One expected use of anycast addresses is to identify the set of
	routers belonging to an organization providing Internet service.		routers belonging to an organization providing Internet service.
	Such addresses could be used as intermediate addresses in an IPv6		Such addresses could be used as intermediate addresses in an IPv6
	Routing header, to cause a packet to be delivered via a particular		Routing header, to cause a packet to be delivered via a particular
	service provider or sequence of service providers.		service provider or sequence of service providers.
	Some other possible uses are to identify the set of routers attached		Some other possible uses are to identify the set of routers attached
	to a particular subnet, or the set of routers providing entry into a		to a particular subnet, or the set of routers providing entry into a
	particular routing domain.		particular routing domain.
	There is little experience with widespread, arbitrary use of Internet
	anycast addresses, and some known complications and hazards when
	using them in their full generality [ANYCST]. Until more experience
	has been gained and solutions are specified, the following
	restrictions are imposed on IPv6 anycast addresses:
	o An anycast address must not be used as the source address of an
	IPv6 packet.
	o An anycast address must not be assigned to an IPv6 host, that
	is, it may be assigned to an IPv6 router only.
	2.6.1 Required Anycast Address		2.6.1 Required Anycast Address
	The Subnet-Router anycast address is predefined. Its format is as		The Subnet-Router anycast address is predefined. Its format is as
	follows:		follows:
	| n bits | 128-n bits |		| n bits | 128-n bits |
	+------------------------------------------------+----------------+		+------------------------------------------------+----------------+
	| subnet prefix | 00000000000000 |		| subnet prefix | 00000000000000 |
	+------------------------------------------------+----------------+		+------------------------------------------------+----------------+
	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 The restrictions on using IPv6 anycast addresses were removed
			because there is now sufficient experience with the use of anycast
			addresses, the issues are not specific to IPv6, and the GROW
			working group is working in this area.
	o Deprecated the Site-Local unicast 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:
End of changes. 10 change blocks.
	23 lines changed or deleted		16 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/