< draft-huston-ipv6-documentation-prefix-02.txt		draft-huston-ipv6-documentation-prefix-03.txt >
	Individual Submission G. Huston		Individual Submission G. Huston
	Internet-Draft Telstra		Internet-Draft Telstra
	Expires: July 24, 2004 A. Lord		Expires: July 31, 2004 A. Lord
	APNIC		APNIC
	P. Smith		P. Smith
	Cisco		Cisco
	January 24, 2004		January 31, 2004
	IPv6 Documentation Address		IPv6 Address Prefix reserved for Documentation
	draft-huston-ipv6-documentation-prefix-02.txt		draft-huston-ipv6-documentation-prefix-03.txt
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	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 other		Task Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.		groups may also distribute working documents as Internet-Drafts.
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 http://		The list of current Internet-Drafts can be accessed at http://
	www.ietf.org/ietf/1id-abstracts.txt.		www.ietf.org/ietf/1id-abstracts.txt.
	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 will expire on July 24, 2004.		This Internet-Draft will expire on July 31, 2004.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2004). All Rights Reserved.		Copyright (C) The Internet Society (2004). All Rights Reserved.
	Abstract		Abstract
	To reduce the likelihood of conflict and confusion when relating		To reduce the likelihood of conflict and confusion when relating
	documented examples to deployed systems, an IPv6 unicast prefix is		documented examples to deployed systems, an IPv6 unicast address
	reserved for use in examples in RFCs, books, documentation, and the		prefix is reserved for use in examples in RFCs, books, documentation,
	like. Since site-local and link- local unicast addresses have special		and the like. Since site-local and link- local unicast addresses have
	meaning in IPv6, these addresses cannot be used in many example		special meaning in IPv6, these addresses cannot be used in many
	situations. The document describes the use of the IPv6 address prefix		example situations. The document describes the use of the IPv6
	2001:0DB8::/32 as a reserved prefix for use in documentation.		address prefix 2001:DB8::/32 as a reserved prefix for use in
			documentation.
	1. Introduction		1. Introduction
	The address architecture for IPv6 [1] does not specifically allocate		The address architecture for IPv6 [1] does not specifically allocate
	an IPv6 address prefix for use for documentation purposes.		an IPv6 address prefix for use for documentation purposes.
	Documentation material is currently using address prefixes drawn from		Documentation material is currently using address prefixes drawn from
	address blocks already allocated or assigned to existing		address blocks already allocated or assigned to existing
	organizations or to well known ISPs, or drawn from the currently		organizations or to well known ISPs, or drawn from the currently
	unallocated address pool. Such use conflicts with existing or future		unallocated address pool. Such use conflicts with existing or future
	allocations or assignments of IPv6 address space.		allocations or assignments of IPv6 address space.
	skipping to change at page 2, line 27 ¶		skipping to change at page 2, line 27 ¶
	environment causes address and routing conflicts with existing		environment causes address and routing conflicts with existing
	services. In making an explicit allocation of a documentation address		services. In making an explicit allocation of a documentation address
	prefix, it is intended that such operational problems may be avoided		prefix, it is intended that such operational problems may be avoided
	for IPv6.		for IPv6.
	Similar, but different, discussion also applies to top level domain		Similar, but different, discussion also applies to top level domain
	names and some have been reserved for similar purposes. [2]		names and some have been reserved for similar purposes. [2]
	2. Documentation IPv6 Address Prefix		2. Documentation IPv6 Address Prefix
	To allow documentation to accurately describe deployment examples the		To allow documentation to accurately describe deployment examples,
	use of site local or link local addresses is inappropriate, and a		the use of site local or link local addresses is inappropriate, and a
	unicast address block is required. All IPv6 unicast address space is		unicast address block is required. All IPv6 unicast address space is
	currently marked as reserved, unassigned or has been assigned to IANA		currently marked as reserved, unassigned or has been assigned to the
	for further redistribution to RIRs [1], but no unicast address space		Internet Assigned Numbers Authority (IANA) for further redistribution
	has been specifically nominated for the purposes of use in documented		to the Regional Internet Registries (RIRs) [1], but no unicast
	examples.		address space has been specifically nominated for the purposes of use
			in documented examples.
	Following acceptance within APNIC's addressing community of a		Following acceptance within the Asia Pacific regional addressing
	proposal for a block of IPv6 address space to be created for		community of a proposal for a block of IPv6 address space to be
	documentation purposes, APNIC allocated a unicast address prefix for		reserved for documentation purposes, the Asia Pacific Network
			Information Centre (APNIC) allocated a unicast address prefix for
	documentation purposes. The address block is within the range of a		documentation purposes. The address block is within the range of a
	conventional allocation size, so that documentation can accurately		conventional allocation size, so that documentation can accurately
	match deployment scenarios.		match deployment scenarios.
	Multicast addresses can also be reserved for documentation using this		The documentation prefix described in this memo can also be used to
	document reserved address space together with the Unicast		generate multicast addresses for documentation, using the Unicast
	prefix-based proposal [3] for multicast addresses.		prefix-based proposal [3]. Representing other kinds of multicast
			addresses in documentation is outside the scope of this memo.
	The prefix allocated for documentation purposes is 2001:0DB8::/32		The prefix allocated for documentation purposes is 2001:DB8::/32
	3. Operational Implications		3. Operational Implications
	This assignment implies that IPv6 network operators should add this		This assignment implies that IPv6 network operators should add this
	address block to the list of non-routeable IPv6 address space, and if		address prefix to the list of non-routeable IPv6 address space, and
	packet filters are deployed, then this address should be added to		if packet filters are deployed, then this address prefix should be
	packet filters.		added to packet filters.
	This not a local-use address block, and the filters may be used in		This not a local-use address prefix, and the filters may be used in
	both local and public contexts.		both local and public contexts.
	4. IANA Considerations		4. IANA Considerations
	IANA is to record the allocation of the IPv6 global unicast address		IANA is to record the allocation of the IPv6 global unicast address
	prefix 2001:0DB8::/32 as a documentation-only prefix in the IPv6		prefix 2001:DB8::/32 as a documentation-only prefix in the IPv6
	address registry. No end party is to be assigned this address.		address registry. No end party is to be assigned this address.
	5. Security Considerations		5. 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.
	in [4].
	6. Acknowledgements		6. Acknowledgements
	The authors acknowledge the work of Marc Blanchet, assisted by Alain		The authors acknowledge the work of Marc Blanchet, assisted by Alain
	Durand, Robert Elz, Bob Fink and Dave Thaler, in authoring a previous		Durand, Robert Elz, Bob Fink and Dave Thaler, in authoring a previous
	proposal for a V6 documentation prefix.		proposal for a V6 documentation prefix.
	Normative References		Normative References
	[1] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)		[1] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
	Addressing Architecture", RFC 3513, April 2003.		Addressing Architecture", RFC 3513, April 2003.
	Informative References		Informative References
	[2] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", BCP		[2] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", BCP
	32, RFC 2606, June 1999.		32, RFC 2606, June 1999.
	[3] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast		[3] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast
	Addresses", RFC 3306, August 2002.		Addresses", RFC 3306, August 2002.
	[4] Kent, S. and R. Atkinson, "IP Authentication Header", RFC 2402,
	November 1998.
	Authors' Addresses		Authors' Addresses
	Geoff Huston		Geoff Huston
	Telstra		Telstra
	Anne Lord		Anne Lord
	Asia Pacific Network Information Centre		Asia Pacific Network Information Centre
	Philip Smith		Philip Smith
	Cisco Systems		Cisco Systems
	Intellectual Property Statement		Intellectual Property Statement
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	intellectual property or other rights that might be claimed to		intellectual property or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; neither does it represent that it		might or might not be available; neither does it represent that it
End of changes. 18 change blocks.
	36 lines changed or deleted		35 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/