3849
INFORMATIONAL
IPv6 Address Prefix Reserved for Documentation
Authors: G. Huston, A. Lord, P. Smith
Date: July 2004
Working Group: NON WORKING GROUP
Stream: IETF
Updated by:
RFC 9637
Abstract
To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, an IPv6 unicast address prefix is reserved for use in examples in RFCs, books, documentation, and the like. Since site-local and link-local unicast addresses have special meaning in IPv6, these addresses cannot be used in many example situations. The document describes the use of the IPv6 address prefix 2001:DB8::/32 as a reserved prefix for use in documentation. This memo provides information for the Internet community.
RFC 3849
INFORMATIONAL
Updated by: 9637
Network Working Group G. Huston
Request for Comments: 3849 Telstra
Category: Informational A. Lord
APNIC
P. Smith
Cisco
July 2004
<span class="h1">IPv6 Address Prefix Reserved for Documentation</span>
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004).
Abstract
To reduce the likelihood of conflict and confusion when relating
documented examples to deployed systems, an IPv6 unicast address
prefix is reserved for use in examples in RFCs, books, documentation,
and the like. Since site-local and link-local unicast addresses have
special meaning in IPv6, these addresses cannot be used in many
example situations. The document describes the use of the IPv6
address prefix 2001:DB8::/32 as a reserved prefix for use in
documentation.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The address architecture for IPv6 [<a href="#ref-1" title=""Internet Protocol Version 6 (IPv6) Addressing Architecture"">1</a>] does not specifically allocate
an IPv6 address prefix for use for documentation purposes.
Documentation material is currently using address prefixes drawn from
address blocks already allocated or assigned to existing
organizations or to well known ISPs, or drawn from the currently
unallocated address pool. Such use conflicts with existing or future
allocations or assignments of IPv6 address space.
The problems such conflicts may cause have already been encountered
with IPv4 where literal use of documented examples in a production
environment causes address and routing conflicts with existing
services. In making an explicit allocation of a documentation
address prefix, it is intended that such operational problems may be
avoided for IPv6.
<span class="grey">Huston, et al. Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc3849">RFC 3849</a> IPv6 Documentation Address July 2004</span>
Similar, but different, discussion also applies to top level domain
names and some have been reserved for similar purposes [<a href="#ref-2" title=""Reserved Top Level DNS Names"">2</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Documentation IPv6 Address Prefix</span>
To allow documentation to accurately describe deployment examples,
the use of site local or link local addresses is inappropriate, and a
unicast address block is required. All IPv6 unicast address space is
currently marked as reserved, unassigned or has been assigned to the
Internet Assigned Numbers Authority (IANA) for further redistribution
to the Regional Internet Registries (RIRs) [<a href="#ref-1" title=""Internet Protocol Version 6 (IPv6) Addressing Architecture"">1</a>], but no unicast
address space has been specifically nominated for the purposes of use
in documented examples.
Following acceptance within the Asia Pacific regional addressing
community of a proposal for a block of IPv6 address space to be
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
conventional allocation size, so that documentation can accurately
match deployment scenarios.
The documentation prefix described in this memo can also be used to
generate multicast addresses for documentation, using the Unicast
prefix-based proposal [<a href="#ref-3" title=""Unicast-Prefix-based IPv6 Multicast Addresses"">3</a>]. Representing other kinds of multicast
addresses in documentation is outside the scope of this memo.
The prefix allocated for documentation purposes is 2001:DB8::/32
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Operational Implications</span>
This assignment implies that IPv6 network operators should add this
address prefix to the list of non-routeable IPv6 address space, and
if packet filters are deployed, then this address prefix should be
added to packet filters.
This is not a local-use address prefix, and the filters may be used
in both local and public contexts.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
IANA is to record the allocation of the IPv6 global unicast address
prefix 2001:DB8::/32 as a documentation-only prefix in the IPv6
address registry. No end party is to be assigned this address.
<span class="grey">Huston, et al. Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc3849">RFC 3849</a> IPv6 Documentation Address July 2004</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
IPv6 addressing documents do not have any direct impact on Internet
infrastructure security.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
The authors acknowledge the work of Marc Blanchet, assisted by Alain
Durand, Robert Elz, Bob Fink, and Dave Thaler, in authoring a
previous proposal for a V6 documentation prefix.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
Addressing Architecture", <a href="./rfc3513">RFC 3513</a>, April 2003.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-2">2</a>] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS Names",
<a href="https://www.rfc-editor.org/bcp/bcp32">BCP 32</a>, <a href="./rfc2606">RFC 2606</a>, June 1999.
[<a id="ref-3">3</a>] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast
Addresses", <a href="./rfc3306">RFC 3306</a>, August 2002.
Authors' Addresses
Geoff Huston
Telstra
EMail: [email protected]
Anne Lord
Asia Pacific Network Information Centre
EMail: [email protected]
Philip Smith
Cisco Systems
EMail: [email protected]
<span class="grey">Huston, et al. Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc3849">RFC 3849</a> IPv6 Documentation Address July 2004</span>
Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
[email protected].
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Huston, et al. Informational [Page 4]
Annotations
Select text to annotate