Internet DRAFT - draft-ghnb-v6ops-rfc3849-update
draft-ghnb-v6ops-rfc3849-update
V6OPS G. Huston
Internet-Draft APNIC
Updates: 3849 (if approved) N. Buraglio
Intended status: Informational Energy Sciences Network
Expires: 8 February 2024 7 August 2023
Expanding the IPv6 Documentation Space
draft-ghnb-v6ops-rfc3849-update-00
Abstract
The document describes the reservation of an additional IPv6 address
prefix for use in documentation. The reservation of a /20 prefix
allows documented examples to reflect a broader range of realistic
current deployment scenarios.
Discussion Venues
This note is to be removed before publishing as an RFC.
Discussion of this document takes place on the IPv6 Operations
Working Group mailing list (v6ops@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/v6ops/.
Source for this draft and an issue tracker can be found at
https://github.com/buraglio/draft-ghnb-v6ops-rfc3849-update.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 8 February 2024.
Huston & Buraglio Expires 8 February 2024 [Page 1]
Internet-Draft Expanding the IPv6 Documentation Space August 2023
Copyright Notice
Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Current Assignment and Allocation Data . . . . . . . . . . . 3
3. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 4
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
[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.
As the global deployment of IPv6 expands and evolves, individual IPv6
network deployment scenarios have also increased is 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 many realistic current
deployment scenarios.
Huston & Buraglio Expires 8 February 2024 [Page 2]
Internet-Draft Expanding the IPv6 Documentation Space August 2023
Without this additional address allocation, then documentation
address prefixes are 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 reservation of a further /20 address prefix for documentation
purposes avoids such conflicts.
2. Current Assignment and Allocation Data
According to the allocation and assignment data published by the
Regional Internet Registries,
(https://ftp.ripe.net/pub/stats/ripencc/nro-stats/latest/nro-
delegated-stats), in August 2023 some 25.9% of all 62,770 recorded
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.
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.
3. Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
4. Security Considerations
IPv6 addressing documents do not have any direct impact on Internet
infrastructure security.
5. IANA Considerations
IANA is to record the reservation of TBD::/20 in the IANA IPv6
Special-Purpose Address Registry. The Source, Destination,
Forwardable, Globally Reachable and Reserved-by-Protocol fields
should be recorded as False. There is no Termination Date for this
entry.
Huston & Buraglio Expires 8 February 2024 [Page 3]
Internet-Draft Expanding the IPv6 Documentation Space August 2023
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
6.2. Informative References
[RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
Reserved for Documentation", RFC 3849,
DOI 10.17487/RFC3849, July 2004,
<https://www.rfc-editor.org/rfc/rfc3849>.
Acknowledgments
The authors would like to acknowledge the valuable input from Xipeng
Xiao, Chris Cummings, Russ White, Kevin Myers, Ed Horley, Tom
Coffeen, and Scott Hogg
Authors' Addresses
Geoff Huston
APNIC
Email: gih@apnic.net
Nick Buraglio
Energy Sciences Network
Email: buraglio@forwardingplane.net
Huston & Buraglio Expires 8 February 2024 [Page 4]
