idnits 2.17.1 draft-horley-v6ops-expand-doc-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (May 3, 2021) is 1087 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2119' is defined on line 133, but no explicit reference was found in the text == Unused Reference: 'RFC3513' is defined on line 138, but no explicit reference was found in the text == Unused Reference: 'RFC3306' is defined on line 149, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3513 (Obsoleted by RFC 4291) Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Horley 3 Internet-Draft T. Coffeen 4 Intended status: Informational S. Hogg 5 Expires: November 4, 2021 HexaBuild 6 N. Buraglio 7 Energy Sciences Network 8 K. Myers 9 IP ArchiTechs 10 C. Cummings 11 Energy Sciences Network 12 R. White 13 Juniper Networks 14 May 3, 2021 16 Expanding the IPv6 Address Prefix Reserved for Documentation 17 draft-horley-v6ops-expand-doc-00 19 Abstract 21 To reduce the likelihood of conflict and confusion when relating 22 documented examples to deployed systems, an IPv6 unicast address 23 prefix is reserved for use in examples in RFCs, books, documentation, 24 and the like. This document adds an additional prefix to the 25 existing reserved IPv6 prefixes, 2001:db8::/32. This document 26 describes the use of the IPv6 address prefix 3ffe::/16 (formerly 27 6bone) as a reserved prefix for use in documentation. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on November 4, 2021. 46 Copyright Notice 48 Copyright (c) 2021 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (https://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. Expanded Documentation IPv6 Address Prefix . . . . . . . . . 2 65 3. Operational Implications . . . . . . . . . . . . . . . . . . 2 66 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 67 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 68 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 70 7.1. Normative References . . . . . . . . . . . . . . . . . . 3 71 7.2. Informative References . . . . . . . . . . . . . . . . . 4 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 74 1. Introduction 76 The address architecture for IPv6 [RFC4291] does not specifically 77 allocate an IPv6 address prefix for use for documentation purposes. 78 The current IPv6 documentation prefix of 2001:db8::/32 defined in 79 [RFC6890] is not large enough for many design, lab, and documentation 80 requirements. An example of this limitation is apparent when 81 doumenting a multi-provder ISP network address plan. An additional, 82 larger allocation would help address these needs. 84 2. Expanded Documentation IPv6 Address Prefix 86 The additional prefix allocated for documentation purposes is 87 3ffe::/16. 89 3. Operational Implications 91 This assignment implies that IPv6 network operators should add this 92 address prefix to the list of non-routeable, bogon IPv6 address 93 space, and if packet filters are deployed, this address prefix should 94 be added to packet filters intended to prevent public routing of such 95 address space. 97 Because this address prefix has previously been used for the 6bone, 98 and subsequently the 6bone was shutdown, this address prefix is 99 already listed in many non-routeable tables, filters and lists. It 100 was also depreferred in [RFC6724] which limits its usability. In 101 addition, the address prefix was returned to IANA and is available to 102 be marked for documentation purposes. 104 This is not a local-use address prefix, and the filters may be used 105 in both local and public contexts. 107 4. IANA Considerations 109 IANA is to record the allocation of the IPv6 global unicast address 110 prefix 3ffe::/16 as a documentation-only prefix in the IPv6 address 111 registry. No end party is to be assigned this address. 113 5. Security Considerations 115 IPv6 addressing documents generally do not have any direct impact on 116 Internet infrastructure security. 118 However, the assignment of a new address space for documentation 119 purposes does mean, as indicated above, that these addresses SHOULD 120 be added to any filters required by individual operators to prevent 121 their use for globally routed destinations. 123 6. Acknowledgements 125 The authors acknowledge the work of Geoff Huston, assisted by Anne 126 Lord, and Philip Smith, in authoring the previous proposal for the 127 IPv6 documentation prefix. 129 7. References 131 7.1. Normative References 133 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 134 Requirement Levels", BCP 14, RFC 2119, 135 DOI 10.17487/RFC2119, March 1997, 136 . 138 [RFC3513] Hinden, R. and S. Deering, "Internet Protocol Version 6 139 (IPv6) Addressing Architecture", RFC 3513, 140 DOI 10.17487/RFC3513, April 2003, 141 . 143 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 144 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 145 2006, . 147 7.2. Informative References 149 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 150 Multicast Addresses", RFC 3306, DOI 10.17487/RFC3306, 151 August 2002, . 153 [RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown, 154 "Default Address Selection for Internet Protocol Version 6 155 (IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012, 156 . 158 [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, 159 "Special-Purpose IP Address Registries", BCP 153, 160 RFC 6890, DOI 10.17487/RFC6890, April 2013, 161 . 163 Authors' Addresses 165 Ed Horley 166 HexaBuild 168 Email: ed@hexabuild.io 170 Tom Coffeen 171 HexaBuild 173 Email: tom@hexabuild.io 175 Scott Hogg 176 HexaBuild 178 Email: scott@hexabuild.io 180 Nick Buraglio 181 Energy Sciences Network 183 Email: buraglio@es.net 184 Kevin Myers 185 IP ArchiTechs 187 Email: kevin.myers@iparchitechs.com 189 Chris Cummings 190 Energy Sciences Network 192 Email: chriscummings@es.net 194 Russ White 195 Juniper Networks 197 Email: russ@riw.us