rfc9637xml2.original.xml   rfc9637.xml 
<?xml version="1.0" encoding="UTF-8"?> <?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.33 (Ruby 2.
6.10) -->
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<rfc ipr="trust200902" docName="draft-ietf-v6ops-rfc3849-update-05" category="in <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
fo" submissionType="IETF" updates="3849" tocInclude="true" sortRefs="true" symRe -ietf-v6ops-rfc3849-update-05" number="9637" consensus="true" category="info" su
fs="true"> bmissionType="IETF" updates="3849" obsoletes="" tocInclude="true" sortRefs="true
" symRefs="true" version="3" xml:lang="en">
<front> <front>
<title abbrev="Expanding the IPv6 Documentation Space">Expanding the IPv6 Do cumentation Space</title> <title abbrev="Expanding the IPv6 Documentation Space">Expanding the IPv6 Do cumentation Space</title>
<seriesInfo name="RFC" value="9637"/>
<author initials="G." surname="Huston" fullname="Geoff Huston"> <author initials="G." surname="Huston" fullname="Geoff Huston">
<organization>APNIC</organization> <organization>APNIC</organization>
<address> <address>
<email>gih@apnic.net</email> <email>gih@apnic.net</email>
</address> </address>
</author> </author>
<author initials="N." surname="Buraglio" fullname="Nick Buraglio"> <author initials="N." surname="Buraglio" fullname="Nick Buraglio">
<organization>Energy Sciences Network</organization> <organization>Energy Sciences Network</organization>
<address> <address>
<email>buraglio@forwardingplane.net</email> <email>buraglio@forwardingplane.net</email>
</address> </address>
</author> </author>
<date year="2024" month="August"/>
<date year="2024" month="June" day="29"/> <area>OPS</area>
<workgroup>v6ops</workgroup>
<area>Operations and Management</area>
<workgroup>V6OPS</workgroup>
<keyword>Internet-Draft</keyword>
<abstract> <abstract>
<t>The document describes the reservation of an additional IPv6 address
<?line 42?> prefix for use in documentation. This update to RFC 3849 expands on the
existing 2001:db8::/32 address block with the reservation of an
<t>The document describes the reservation of an additional IPv6 address prefix additional, larger prefix. The addition of a /20 prefix allows
for use in documentation. This update to RFC 3849 expands on the existing 2001:d documented examples to more closely reflect a broader range of
b8::/32 realistic, current deployment scenarios and more closely aligns with
address block with the reservation of an additional, larger prefix. contemporary allocation models for large networks.
The addition of a /20 allows documented examples to more closely reflect </t>
a broader range of realistic, current deployment scenarios and more closely alig
ns with
contemporary allocation models for large networks.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<?line 51?> <section anchor="introduction">
<name>Introduction</name>
<section anchor="introduction"><name>Introduction</name>
<t><xref target="RFC3849"/> introduced 2001:db8::/32, describing the use of the
IPv6 address
prefix 2001:db8::/32 as a reserved prefix for use in documentation. The
rationale for this reservation was to reduce the likelihood of conflict and
confusion when relating documented examples to deployed systems.</t>
<t>As the global deployment of IPv6 expands and evolves, individual IPv6 <t><xref target="RFC3849"/> introduced the IPv6 address prefix
network deployment scenarios have also increased is size and diversity, and 2001:db8::/32 as a reserved prefix for use in documentation. The
rationale for this reservation was to reduce the likelihood of conflict
and confusion when relating documented examples to deployed systems.</t>
<t>As the global deployment of IPv6 expands and evolves, individual IPv6
network deployment scenarios have also increased in size and diversity, and
there is a requirement for documentation to reflect this increased diversity there is a requirement for documentation to reflect this increased diversity
and scope. The original 2001:db8::/32 reservation is inadequate to describe and scope. The original 2001:db8::/32 reservation is inadequate to describe
many realistic current deployment scenarios.</t> many realistic, current deployment scenarios.</t>
<t>Without this additional address allocation, documentation address prefixes <t>Without this additional address allocation, documentation prefixes
are drawn from address blocks already allocated or assigned to existing are drawn from address blocks already allocated or assigned to existing
organizations or to well known ISPs, or drawn from the currently unallocated organizations or well-known ISPs, or they are drawn from the currently unallocat ed
address pool. Such use conflicts with existing or future allocations or address pool. Such use conflicts with existing or future allocations or
assignments of IPv6 address space. The reservation of a further /20 IPv6 assignments of IPv6 address space. The reservation of a /20 IPv6
address prefix from the Global Unicast Address pool <xref target="RFC4291"/> for address prefix from the Global Unicast Address pool <xref target="RFC4291"/> for
documentation purposes avoids such conflicts.</t> documentation purposes allows such conflicts to be avoided.</t>
</section>
<section anchor="current-assignment-and-allocation-data"><name>Current Assignmen
t and Allocation Data</name>
<t>According to the allocation and assignment data published by the Regional
Internet Registries,
<xref target="NROStatsReport"/>,
in August 2023 some 25.9% of all 62,770 recorded IPv6 unicast allocations and
assignments are larger than a /32 in size. The most common allocation or
assignment size is a /29, used in 24.8% of cases.</t>
<t>The four largest assignments made to end users have been /19s, but these
allocations were made before the RIRs' address allocation policies moved
away from the use of a fixed /48 site address prefix IPv6 address assignment
policies, and in the foreseeable future its unlikely that individual
networks require more than a /20. It is believed that a reservation of a /20
would cover the documentation needs as they relate the broad range of
realistic network deployments.</t>
</section>
<section anchor="filtering-and-appropriate-use"><name>Filtering and appropriate
use</name>
<t>Documentation prefixes are for the use or relaying configuration and document
ation examples and as such
MUST NOT be used for actual traffic, MUST NOT be globally advertised, and SHOUL
D NOT be used internally for routed production traffic or other connectivity.
Documentation prefixes should be considered bogon and filtered in routing advert
isements as appropriate.</t>
</section>
<section anchor="conventions-and-definitions"><name>Conventions and Definitions<
/name>
<t>None.</t>
</section> </section>
<section anchor="security-considerations"><name>Security Considerations</name>
<t>This special use prefix should be marked as and considered <xref target="BOGO
N"/>. As is appropriate with bogon prefixes,
packets whose src/dst belongs to this prefix should be dropped and disallowed ov
er the public Internet.</t>
<section anchor="term2119">
<name>Requirements Language</name>
<t>
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
"<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
"<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are
to be interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/>
<xref target="RFC8174"/> when, and only when, they appear in all capitals,
as shown here.
</t>
</section> </section>
<section anchor="iana-considerations"><name>IANA Considerations</name> <section anchor="current-assignment-and-allocation-data">
<name>Current Assignment and Allocation Data</name>
<t>IANA is to record the reservation of TBD::/20 in the IANA IPv6 Special-Purpos
e Address Registry;
<xref target="IANAIPv6SPAR"/>. The Source, Destination, Forwardable,
Globally Reachable and Reserved-by-Protocol fields should be recorded as
False. There is no Termination Date for this entry.
The name of the reservation is “Documentation".</t>
</section> <t>According to the allocation and assignment data published by the Region
al
Internet Registries (RIRs) (see
<xref target="NROStatsReport"/>),
in August 2023, 25.9% of the 62,770 recorded IPv6 unicast allocations and
assignments were larger than a /32 in size. The most common allocation or
assignment size was a /29, used in 24.8% of cases.</t>
<t>The four largest assignments made to end users have been /19s, but these
allocations were made before the RIRs moved away from the use of a fixed /48
site address prefix in IPv6 address assignment policies, and in the
foreseeable future, it is unlikely that individual networks will require more
than a /20. It is believed that reservation of a /20 will cover the
documentation needs as they relate to the broad range of realistic network
deployments.</t>
</section>
<section anchor="filtering-and-appropriate-use">
<name>Filtering and Appropriate Use</name>
<t>Documentation prefixes are for the use of relaying configuration and
documentation examples, and as such, they <bcp14>MUST NOT</bcp14> be
used for actual traffic, <bcp14>MUST NOT</bcp14> be globally advertised,
and <bcp14>SHOULD NOT</bcp14> be used internally for routed production
traffic or other connectivity. Documentation prefixes should be
considered bogon <xref target="BOGON"/> and filtered in routing
advertisements as appropriate.</t>
</section>
<section anchor="security-considerations">
<name>Security Considerations</name>
<t>This special-use prefix should be marked as and considered bogon
<xref target="BOGON"/>. As is appropriate with bogon prefixes, packets
whose source or destination belongs to this prefix should be dropped and
disallowed over the public Internet.
</t>
</section>
<section anchor="iana-considerations">
<name>IANA Considerations</name>
<t>IANA has registered the following in the "IANA IPv6 Special-Purpose Add
ress Registry"
<xref target="IANA-IPv6-SPAR"/>.</t>
<dl spacing="compact">
<dt>Address Block:</dt><dd>3fff::/20</dd>
<dt>Name:</dt><dd>Documentation</dd>
<dt>RFC:</dt><dd>RFC 9637</dd>
<dt>Allocation Date</dt><dd>2024-07</dd>
<dt>Termination Date:</dt><dd>N/A</dd>
<dt>Source:</dt><dd>False</dd>
<dt>Destination:</dt><dd>False</dd>
<dt>Forwardable:</dt><dd>False</dd>
<dt>Globally Reachable :</dt><dd>False</dd>
<dt>Reserved-by-Protocol:</dt><dd>False</dd>
</dl>
</section>
</middle> </middle>
<back> <back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<references title='Normative References'> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
119.xml"/>
<reference anchor="IANAIPv6SPAR" target="https://www.iana.org/assignments/iana-i <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
pv6-special-registry/iana-ipv6-special-registry.xhtml"> 174.xml"/>
<front>
<title>IANA IPv6 Special-Purpose Address Registry</title>
<author >
<organization></organization>
</author>
<date year="n.d."/>
</front>
</reference>
</references>
<references title='Informative References'> <reference anchor="IANA-IPv6-SPAR" target="https://www.iana.org/assignme
nts/iana-ipv6-special-registry">
<front>
<title>IANA IPv6 Special-Purpose Address Registry</title>
<author>
<organization>IANA</organization>
</author>
</front>
</reference>
<reference anchor='RFC3849'> </references>
<front> <references>
<title>IPv6 Address Prefix Reserved for Documentation</title> <name>Informative References</name>
<author fullname='G. Huston' initials='G.' surname='Huston'/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
<author fullname='A. Lord' initials='A.' surname='Lord'/> 849.xml"/>
<author fullname='P. Smith' initials='P.' surname='Smith'/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
<date month='July' year='2004'/> 291.xml"/>
<abstract>
<t>To reduce the likelihood of conflict and confusion when relating docume
nted examples to deployed systems, an IPv6 unicast address prefix is reserved fo
r 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 c
annot 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.</t>
</abstract>
</front>
<seriesInfo name='RFC' value='3849'/>
<seriesInfo name='DOI' value='10.17487/RFC3849'/>
</reference>
<reference anchor='RFC4291'> <reference anchor="NROStatsReport" target="https://ftp.ripe.net/pub/stats/ripenc
<front> c/nro-stats">
<title>IP Version 6 Addressing Architecture</title> <front>
<author fullname='R. Hinden' initials='R.' surname='Hinden'/> <title>NRO Stats Reports</title>
<author fullname='S. Deering' initials='S.' surname='Deering'/> <author>
<date month='February' year='2006'/> <organization/>
<abstract> </author>
<t>This specification defines the addressing architecture of the IP Versio </front>
n 6 (IPv6) protocol. The document includes the IPv6 addressing model, text repre </reference>
sentations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addr
esses, and multicast addresses, and an IPv6 node's required addresses.</t>
<t>This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture
". [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name='RFC' value='4291'/>
<seriesInfo name='DOI' value='10.17487/RFC4291'/>
</reference>
<reference anchor="NROStatsReport" target="https://ftp.ripe.net/pub/stats/ripenc <reference anchor="BOGON" target="https://www.team-cymru.com/post/unrave
c/nro-stats/latest/nro-delegated-stats"> lling-the-mystery-of-bogons-a-senior-stakeholder-and-it-professional-guide">
<front> <front>
<title>NRO Stats Report</title> <title>Unravelling the Mystery of Bogons: A senior stakeholder and
<author > IT professional guide</title>
<organization></organization> <author>
</author> <organization>Team Cymru</organization>
<date year="n.d."/> </author>
</front> <date month="July" year="2023"/>
</reference> </front>
<reference anchor="BOGON" target="https://www.team-cymru.com/post/unravelling-th </reference>
e-mystery-of-bogons-a-senior-stakeholder-and-it-professional-guide">
<front>
<title>Team Cymru Bogon Guide</title>
<author >
<organization></organization>
</author>
<date year="n.d."/>
</front>
</reference>
</references>
</references> </references>
<?line 115?> <section numbered="false" anchor="acknowledgments">
<name>Acknowledgments</name>
<section numbered="false" anchor="acknowledgments"><name>Acknowledgments</name> <t>The authors would like to acknowledge the valuable input from <contact
<t>The authors would like to acknowledge the valuable input from XiPeng Xiao, Ch fullname="XiPeng
ris Cummings, Russ White, Kevin Myers, Ed Horley, Tom Coffeen, and Scott Hogg.</ Xiao"/>, <contact fullname="Chris Cummings"/>, <contact fullname="Russ Whi
t> te"/>, <contact fullname="Kevin Myers"/>, <contact fullname="Ed Horley"/>, <cont
act fullname="Tom Coffeen"/>,
</section> and <contact fullname="Scott Hogg"/>.</t>
</section>
</back> </back>
<!-- ##markdown-source:
H4sIAJAdgGYAA41YXW/byBV9n18xcFH0RZQcJ/XGKgqsYieO0cY2LKe7QNGH
ITmkBiY53JmhFK1hoD9kf93+kp57h5Qox0k3DxstP+7ce865514mSRIRTKj0
XL7/0qomN00pw0rLq9v1qbywWVfrJqhgbCOXrcq0UGnq9PoPP57brFE1wudO
FSExOhTJ+tS2PnFF9vrtm7Oka3MVdFLhPz4IRH4tfJfWxntECdsW7169v/8g
MhXm0jSFFaZ1cxlc58PJ8fHZ8YlQTqu5PLppteOzvURq8pNqVKkpoSOxKefy
X6c3t0vxsEG8JmjX6JBcUFKiNXP572CzifTWBacLj1/bmn78R8T0PNJCskKo
LqysmwvJf5L+b4nE8MjlVH5EVrbZXY61X2pbFM9vWYecFrfXV+e7S7pWpprL
0qx+VG1jsilyfPmk66l81zlVVsY+O+vaZA9f3+PD3jfalVu5zIxuMu3ltQ4b
6x6eH5/2L/9YWLdRjjhuK9VozkY01tUAea0Jg6vF9YKoX94u7iImQblSg6hV
CK2fz2abzWZqQMQUGcwUOC0bYsTP6GJi2vVp4ludGVUlTpfGB7f9zq3pl1Wo
q3hQVO0RpRDlt+wfvu1ca72Wizx32nt51798JATJZ5T+3YdzYrX/+ebk7BX9
vL67WULD/k63kMPLZRWhnTrTMiaztktnnt6Y0aUmy2aNs0m8EmXNF3Jd6RL/
m8dbB1XgTMmHynjqEe6+u7m8uf42qkGrOskg026a2XqGksOsa5xa66oCZQna
Mqm3HkrfJrZIUluiMRKVeN0Y6yiHB72yVa5dgm5JTEhaZwvNbQcUy87k+iDH
exwoz+lA+Y6CyUt6BKgmSSJVCohVBoHcww7y3glkrn3mTAqxkUuADu3W0R5s
gSaVKs9N4AMjh6rnrEXzmS8CbMkOVJpmF5Lfnsr7lfEy9qYMlujjBpWabclL
nEAn6i+gnkwKTvFqnqdv5/PZaxhGf0xaWXTLxoTV/81vIisiwfWpTbnO4TY/
LWcnx1JVld34XbY6RwqqbitCwMraOi2zCuqstjitqDQQUzJ1VoEH6VRTaooF
P6socVhS1jkXkWwru2VQfaYb5YyNNncQE6+VsD+qSGSwT11DTcptOa8sVlZb
KNFLwpZLkk30AT+NVNYmzystxJ/IJ53Nu4xeE+Lxse+XpycQEu+gvgNkJwPj
w2Ag9lDQbkb0yIuI4uHLUqGingQE7h/5nga0iIavKs3PBVLFmMWNYtydplw5
i8o86MqsrM0pL2BUVCYLhCQBVnSeX1vpBi+heamOb5AZGcFFT11WE3yLqPOy
sikUPaIMR3H5gzyJOL221Vpj1hjM0bXJu74JRM/Hy5Sv0OBg01u8lkEnHgmg
aG9+1RwVobTzJmwnXBPSgTxMBPaXzjgeiAzWAZoRJRZkRHEffRdRUHyfWdge
YY+hYkpDrXvI4hh/DgRt/9L1jToYgqhVs93r/LsyB7A/QdC261MbmcbQyHt5
T57Vdego2tOyQMvIppGFs7U8sAIKhJzyXb+gfCAV5xZ+o4DBUQQGmmrMr/3C
QeKzcgPvlQ+NRfCr5S2oJZj3Z5E2+kLRq12zO2RnSK211VQuu2zFmh/kGTt6
72YIW3Shc3pUOOUgRhN2p7khtqeFLDL33OgQzZFS2MJYg4ew7dO/jNL+jO1E
+bCbsZS3ZIOgKQqDgMDEIRFtHMuAeG0NWsBTkbsCp+Q3570IFrsqWNKLvXdd
qKDQZllmXdw9LWc1cjd6YY+CxIBQODqFzFYgMN3y87QSkH7EsAkOS4JBP8Lo
DleAp6cJNge56EpscBD7yWssirWWJ3+dnv2Z8QPrpyeTH344BrKUGk5i6Lse
pjFL1JVjmkiP/WgJKxo5kpoI51FLR7pqzHZAVddU377UA76jA3Cjz07OJiSf
nKKcvJm+5SSRiCaYKWBhu978KblRMjV6lVUOFBHB9X6Tavjh7NUZFJ1yF0I/
YlzUhlyGX051QQOJUb668395oUWhFnAOqFHYmsS/Udu9wvqJAU2iXXM5e/MW
pQX9rJEPpb0vQQyx2f4IgMD1kuK1SmlOxMYxqLZreBqQJlQY2fDgwH7wzDhk
B3pOjqfyKhDWKUaJplnFAdTXfYVnxcZ2VQ761sywfuZPjdY0D3hwbOPMiejx
UrBbCcTeKr8eD7F7PpgKYqau4B5osc61zlA4QCrE4dfZYIcsvzg6e+gdJ7Gl
ONSdpuzcvrMOc99Nw9h03NLi0+flvby+uQc4UYQUHZshjTesiEVBW834oX5c
0vaSA6Ng8FJkb/nx5vM/Lw6CGW5YfpriOgwFXhWGNWU4guqwbGkoosFUA7Vh
O/0WCn7FJKVsuR5rrSOz4C2XEikY2thQdCSDPCTbt7EfQw5CyM9ss8bN3Rfp
BU5reHR5Ia5to5m3pcZMQHL0OB+t+id4x+0/gZibXvr7ZGvlHjRDT+FHqT8+
8tfD09MUZsquMJIDz5JY3ADARGA4PGgaNCv6dvIum+XwBgjcNqWPPmv81xnk
iNpSCrx6eF5/aWgOYmfrzXZf3Fwwf7I9L5Yvmn5bIw99aSO/f3eBHQMzqu/r
P/7x9ze4+vhrlZAhJ1zCCTM9ATU0WfsN4kP88CW7mIjLQZ13WmUrthAq9q5f
U5N0m9w6G2yGCVgYXeVjNe3GgfLiA7a2aOhxI2usvNeu7k+l0TZaYiEbfO6y
WdN3/bBDP9utfv/vbweCPupX+BRkEtKLjJaRSucli1Q8zpuuTkkhfz8qKJ2j
p/gdw/+qAfI5bzJF4kHt3o6OtFZVx/WbpsUUYMf+2dxqNMPPRtmJPF85JHXe
1SiqhAPfdWDgpxXceyL/odcg7dMWM2Ui3+fyo3WVxpJ6jyDntigwYfqmz2wI
uF2WU/E/9ram3J8SAAA=
</rfc> </rfc>
 End of changes. 31 change blocks. 
233 lines changed or deleted 151 lines changed or added

This html diff was produced by rfcdiff 1.48.