<?xmlversion="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) -->version='1.0' encoding='UTF-8'?> <!DOCTYPE rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-v6ops-rfc3849-update-05" number="9637" consensus="true" category="info" submissionType="IETF" updates="3849" obsoletes="" tocInclude="true" sortRefs="true"symRefs="true">symRefs="true" version="3" xml:lang="en"> <front> <title abbrev="Expanding the IPv6 Documentation Space">Expanding the IPv6 Documentation Space</title> <seriesInfo name="RFC" value="9637"/> <author initials="G." surname="Huston" fullname="Geoff Huston"> <organization>APNIC</organization> <address> <email>gih@apnic.net</email> </address> </author> <author initials="N." surname="Buraglio" fullname="Nick Buraglio"> <organization>Energy Sciences Network</organization> <address> <email>buraglio@forwardingplane.net</email> </address> </author> <date year="2024"month="June" day="29"/> <area>Operations and Management</area> <workgroup>V6OPS</workgroup> <keyword>Internet-Draft</keyword>month="August"/> <area>OPS</area> <workgroup>v6ops</workgroup> <abstract><?line 42?><t>The document describes the reservation of an additional IPv6 address prefix for use in documentation. This update to RFC 3849 expands on the existing 2001:db8::/32 address block with the reservation of an additional, larger prefix. The addition of a /20 prefix allows documented examples to more closely reflect a broader range of realistic, current deployment scenarios and more closely aligns with contemporary allocation models for largenetworks.</t>networks. </t> </abstract> </front> <middle><?line 51?><sectionanchor="introduction"><name>Introduction</name>anchor="introduction"> <name>Introduction</name> <t><xref target="RFC3849"/> introduced2001:db8::/32, describing the use ofthe 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 network deployment scenarios have also increasedisin size and diversity, and there is a requirement for documentation to reflect this increased diversity and scope. The original 2001:db8::/32 reservation is inadequate to describe manyrealisticrealistic, current deployment scenarios.</t> <t>Without this additional address allocation, documentationaddressprefixes are drawn from address blocks already allocated or assigned to existing organizations orto well knownwell-known ISPs, or they are drawn from the currently unallocated address pool. Such use conflicts with existing or future allocations or assignments of IPv6 address space. The reservation of afurther/20 IPv6 address prefix from the Global Unicast Address pool <xref target="RFC4291"/> for documentation purposesavoidsallows suchconflicts.</t>conflicts to be avoided.</t> </section> <sectionanchor="current-assignment-and-allocation-data"><name>Currentanchor="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 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here. </t> </section> <section anchor="current-assignment-and-allocation-data"> <name>Current Assignment and Allocation Data</name> <t>According to the allocation and assignment data published by the Regional InternetRegistries,Registries (RIRs) (see <xreftarget="NROStatsReport"/>,target="NROStatsReport"/>), in August2023 some2023, 25.9% ofallthe 62,770 recorded IPv6 unicast allocations and assignmentsarewere larger than a /32 in size. The most common allocation or assignment sizeiswas 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 theRIRs' address allocation policiesRIRs moved away from the use of a fixed /48 site address prefix in IPv6 address assignment policies, and in the foreseeablefuture itsfuture, it is unlikely that individual networks will require more than a /20. It is believed thatareservation of a /20wouldwill cover the documentation needs as they relate to the broad range of realistic network deployments.</t> </section> <sectionanchor="filtering-and-appropriate-use"><name>Filteringanchor="filtering-and-appropriate-use"> <name>Filtering andappropriate use</name>Appropriate Use</name> <t>Documentation prefixes are for the useorof relaying configuration and documentationexamplesexamples, and assuch MUST NOTsuch, they <bcp14>MUST NOT</bcp14> be used for actual traffic,MUST NOT<bcp14>MUST NOT</bcp14> be globally advertised, andSHOULD NOT<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> <sectionanchor="conventions-and-definitions"><name>Conventions and Definitions</name> <t>None.</t> </section> <section anchor="security-considerations"><name>Securityanchor="security-considerations"> <name>Security Considerations</name> <t>Thisspecial usespecial-use prefix should be marked as and considered bogon <xref target="BOGON"/>. As is appropriate with bogon prefixes, packets whosesrc/dstsource or destination belongs to this prefix should be dropped and disallowed over the publicInternet.</t>Internet. </t> </section> <sectionanchor="iana-considerations"><name>IANAanchor="iana-considerations"> <name>IANA Considerations</name> <t>IANAis to recordhas registered thereservation of TBD::/20following in theIANA"IANA IPv6 Special-Purpose AddressRegistry;Registry" <xreftarget="IANAIPv6SPAR"/>. The Source, Destination, Forwardable, Globallytarget="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 Reachableand 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>:</dt><dd>False</dd> <dt>Reserved-by-Protocol:</dt><dd>False</dd> </dl> </section> </middle> <back><references title='Normative References'><references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <referenceanchor="IANAIPv6SPAR" target="https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml">anchor="IANA-IPv6-SPAR" target="https://www.iana.org/assignments/iana-ipv6-special-registry"> <front> <title>IANA IPv6 Special-Purpose Address Registry</title><author > <organization></organization><author> <organization>IANA</organization> </author><date year="n.d."/></front> </reference> </references><references title='Informative References'> <reference anchor='RFC3849'> <front> <title>IPv6 Address Prefix Reserved for Documentation</title> <author fullname='G. Huston' initials='G.' surname='Huston'/> <author fullname='A. Lord' initials='A.' surname='Lord'/> <author fullname='P. Smith' initials='P.' surname='Smith'/> <date month='July' year='2004'/> <abstract> <t>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.</t> </abstract> </front> <seriesInfo name='RFC' value='3849'/> <seriesInfo name='DOI' value='10.17487/RFC3849'/> </reference> <reference anchor='RFC4291'> <front> <title>IP Version 6 Addressing Architecture</title> <author fullname='R. Hinden' initials='R.' surname='Hinden'/> <author fullname='S. Deering' initials='S.' surname='Deering'/> <date month='February' year='2006'/> <abstract> <t>This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, 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><references> <name>Informative References</name> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3849.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4291.xml"/> <reference anchor="NROStatsReport"target="https://ftp.ripe.net/pub/stats/ripencc/nro-stats/latest/nro-delegated-stats">target="https://ftp.ripe.net/pub/stats/ripencc/nro-stats"> <front> <title>NRO StatsReport</title> <author > <organization></organization>Reports</title> <author> <organization/> </author><date year="n.d."/></front> </reference> <reference anchor="BOGON" target="https://www.team-cymru.com/post/unravelling-the-mystery-of-bogons-a-senior-stakeholder-and-it-professional-guide"> <front><title>Team Cymru Bogon Guide</title> <author > <organization></organization><title>Unravelling the Mystery of Bogons: A senior stakeholder and IT professional guide</title> <author> <organization>Team Cymru</organization> </author> <dateyear="n.d."/>month="July" year="2023"/> </front> </reference> </references><?line 115?></references> <section numbered="false"anchor="acknowledgments"><name>Acknowledgments</name>anchor="acknowledgments"> <name>Acknowledgments</name> <t>The authors would like to acknowledge the valuable input fromXiPeng Xiao, Chris Cummings, Russ White, Kevin Myers, Ed Horley, Tom Coffeen, and Scott Hogg.</t><contact fullname="XiPeng Xiao"/>, <contact fullname="Chris Cummings"/>, <contact fullname="Russ White"/>, <contact fullname="Kevin Myers"/>, <contact fullname="Ed Horley"/>, <contact fullname="Tom Coffeen"/>, and <contact fullname="Scott Hogg"/>.</t> </section> </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>