| Internet-Draft | Expanding the IPv6 Address Prefix Reserv | May 2021 |
| Horley, et al. | Expires 4 November 2021 | [Page] |
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. This document adds an additional prefix to the existing reserved IPv6 prefixes, 2001:db8::/32. This document describes the use of the IPv6 address prefix 3ffe::/16 (formerly 6bone) as a reserved prefix for use in documentation.¶
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 4 November 2021.¶
Copyright (c) 2021 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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
The address architecture for IPv6 [RFC4291] does not specifically allocate an IPv6 address prefix for use for documentation purposes. The current IPv6 documentation prefix of 2001:db8::/32 defined in [RFC6890] is not large enough for many design, lab, and documentation requirements. An example of this limitation is apparent when doumenting a multi-provder ISP network address plan. An additional, larger allocation would help address these needs.¶
The additional prefix allocated for documentation purposes is 3ffe::/16.¶
This assignment implies that IPv6 network operators should add this address prefix to the list of non-routeable, bogon IPv6 address space, and if packet filters are deployed, this address prefix should be added to packet filters intended to prevent public routing of such address space.¶
Because this address prefix has previously been used for the 6bone, and subsequently the 6bone was shutdown, this address prefix is already listed in many non-routeable tables, filters and lists. It was also depreferred in [RFC6724] which limits its usability. In addition, the address prefix was returned to IANA and is available to be marked for documentation purposes.¶
This is not a local-use address prefix, and the filters may be used in both local and public contexts.¶
IANA is to record the allocation of the IPv6 global unicast address prefix 3ffe::/16 as a documentation-only prefix in the IPv6 address registry. No end party is to be assigned this address.¶
IPv6 addressing documents generally do not have any direct impact on Internet infrastructure security.¶
However, the assignment of a new address space for documentation purposes does mean, as indicated above, that these addresses SHOULD be added to any filters required by individual operators to prevent their use for globally routed destinations.¶
The authors acknowledge the work of Geoff Huston, assisted by Anne Lord, and Philip Smith, in authoring the previous proposal for the IPv6 documentation prefix.¶