Network Working Group E. Horley
Internet-Draft T. Coffeen
Intended status: Informational S. Hogg
Expires: November 4, 2021 HexaBuild
N. Buraglio
Energy Sciences Network
K. Myers
IP ArchiTechs
C. Cummings
Energy Sciences Network
R. White
Juniper Networks
May 3, 2021
Expanding the IPv6 Address Prefix Reserved for Documentation
draft-horley-v6ops-expand-doc-00
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. 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.
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 November 4, 2021.
Horley, et al. Expires November 4, 2021 [Page 1]
Internet-DrExpanding the IPv6 Address Prefix Reserved for Doc May 2021
Copyright Notice
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Expanded Documentation IPv6 Address Prefix . . . . . . . . . 2
3. Operational Implications . . . . . . . . . . . . . . . . . . 2
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
7.1. Normative References . . . . . . . . . . . . . . . . . . 3
7.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
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.
2. Expanded Documentation IPv6 Address Prefix
The additional prefix allocated for documentation purposes is
3ffe::/16.
3. Operational Implications
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
Horley, et al. Expires November 4, 2021 [Page 2]
Internet-DrExpanding the IPv6 Address Prefix Reserved for Doc May 2021
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.
4. IANA Considerations
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.
5. Security Considerations
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.
6. Acknowledgements
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.
7. References
7.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/info/rfc2119>.
[RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6
(IPv6) Addressing Architecture", RFC 3513,
DOI 10.17487/RFC3513, April 2003,
<https://www.rfc-editor.org/info/rfc3513>.
Horley, et al. Expires November 4, 2021 [Page 3]
Internet-DrExpanding the IPv6 Address Prefix Reserved for Doc May 2021
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>.
7.2. Informative References
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6
Multicast Addresses", RFC 3306, DOI 10.17487/RFC3306,
August 2002, <https://www.rfc-editor.org/info/rfc3306>.
[RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown,
"Default Address Selection for Internet Protocol Version 6
(IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012,
<https://www.rfc-editor.org/info/rfc6724>.
[RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,
"Special-Purpose IP Address Registries", BCP 153,
RFC 6890, DOI 10.17487/RFC6890, April 2013,
<https://www.rfc-editor.org/info/rfc6890>.
Authors' Addresses
Ed Horley
HexaBuild
Email: ed@hexabuild.io
Tom Coffeen
HexaBuild
Email: tom@hexabuild.io
Scott Hogg
HexaBuild
Email: scott@hexabuild.io
Nick Buraglio
Energy Sciences Network
Email: buraglio@es.net
Horley, et al. Expires November 4, 2021 [Page 4]
Internet-DrExpanding the IPv6 Address Prefix Reserved for Doc May 2021
Kevin Myers
IP ArchiTechs
Email: kevin.myers@iparchitechs.com
Chris Cummings
Energy Sciences Network
Email: chriscummings@es.net
Russ White
Juniper Networks
Email: russ@riw.us
Horley, et al. Expires November 4, 2021 [Page 5]