rfc9812v1.txt   rfc9812.txt 
Internet Engineering Task Force (IETF) B. Carpenter Internet Engineering Task Force (IETF) B. Carpenter
BCP: 242 Univ. of Auckland BCP: 242 Univ. of Auckland
Request for Comments: 9812 S. Krishnan Request for Comments: 9812 S. Krishnan
Updates: 7249 Cisco Updates: 7249 Cisco
Category: Best Current Practice D. Farmer Category: Best Current Practice D. Farmer
ISSN: 2070-1721 Univ. of Minnesota ISSN: 2070-1721 Univ. of Minnesota
June 2025 October 2025
Clarification of IPv6 Address Allocation Policy Clarification of IPv6 Address Allocation Policy
Abstract Abstract
This document specifies the approval process for changes to the This document specifies the approval process for changes to the "IPv6
"Internet Protocol Version 6 Address Space" registry. It also Address Space" registry. It also updates RFC 7249.
updates RFC 7249.
Status of This Memo Status of This Memo
This memo documents an Internet Best Current Practice. This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on Internet Engineering Steering Group (IESG). Further information on
BCPs is available in Section 2 of RFC 7841. BCPs is available in Section 2 of RFC 7841.
skipping to change at line 51 skipping to change at line 50
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Revised BSD License text as described in Section 4.e of the include Revised BSD License text as described in Section 4.e of the
Trust Legal Provisions and are provided without warranty as described Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License. in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction 1. Introduction
2. Approval Level of IPv6 Address Allocations 2. Approval Level of IPv6 Address Allocations
3. RFC Editor Considerations 3. IANA Considerations
4. IANA Considerations 4. Security Considerations
5. Security Considerations 5. References
6. References 5.1. Normative References
6.1. Normative References 5.2. Informative References
6.2. Informative References Acknowledgements
Appendix A. Acknowledgements
Authors' Addresses Authors' Addresses
1. Introduction 1. Introduction
Internet Protocol Version 6 (IPv6) and its address space are defined Internet Protocol Version 6 (IPv6) and its address space are defined
by [STD86] and [RFC4291]. The management of the IPv6 address space by [STD86] and [RFC4291]. The management of the IPv6 address space
was delegated to IANA by [RFC1881], some years before the was delegated to IANA by [RFC1881], some years before the
relationship between the IETF and IANA was formalized [RFC2860] and relationship between the IETF and IANA was formalized [RFC2860] and
registry details were clarified [RFC7020] [RFC7249]. registry details were clarified [RFC7020] [RFC7249].
Occasionally, IPv6 address space allocations are performed outside Occasionally, IPv6 address space allocations are performed outside
the scope of routine allocations to Regional Internet Registries the scope of routine allocations to Regional Internet Registries
(RIRs). For example, a substantial allocation was requested by an (RIRs). For example, a substantial allocation was requested by an
IETF document approved by the IESG [RFC9602], which moved the range IETF document approved by the IESG [RFC9602], which moved the range
5f00::/16 from the "Internet Protocol Version 6 Address Space" 5f00::/16 from the "IPv6 Address Space" registry [IANA1] to the "IPv6
registry [IANA1] to the "IANA IPv6 Special-Purpose Address Registry" Special-Purpose Address Space" registry [IANA3].
[IANA3].
At the time of writing, the allocation policy in the "Internet At the time of writing, the allocation policy in the "IPv6 Address
Protocol Version 6 Address Space" registry [IANA1] was shown as "IESG Space" registry [IANA1] was shown as "IESG approval", whereas a more
approval", whereas a more stringent policy is appropriate for major stringent policy is appropriate for major allocations. The present
allocations. The present document therefore strengthens the approval document therefore strengthens the approval level needed for non-
level needed for non-routine address allocations, which requires an routine address allocations, which requires an update to [RFC7249].
update to [RFC7249].
This document also clarifies the status of [RFC1881]. This This document also clarifies the status of [RFC1881]. This
clarification is necessary because [RFC1881], a joint publication of clarification is necessary because [RFC1881], a joint publication of
the IAB and IESG following an IETF Last Call, was incorrectly listed the IAB and IESG following an IETF Last Call, was incorrectly listed
in the RFC index at the time of writing as "Legacy", whereas it is in the RFC index at the time of writing as "Legacy", whereas it is
part of the IETF Stream [RFC8729]. part of the IETF Stream [RFC8729].
2. Approval Level of IPv6 Address Allocations 2. Approval Level of IPv6 Address Allocations
Portions of the IPv6 address space are shown in the registry as Portions of the IPv6 address space are shown in the registry as
skipping to change at line 137 skipping to change at line 133
| with future needs. | with future needs.
NEW: NEW:
| The vast bulk of the IPv6 address space (approximately 7/8ths of | The vast bulk of the IPv6 address space (approximately 7/8ths of
| the whole address space) is reserved by the IETF [RFC4291], with | the whole address space) is reserved by the IETF [RFC4291], with
| the expectation that further assignment of globally unique unicast | the expectation that further assignment of globally unique unicast
| address space will be made from this reserved space in accordance | address space will be made from this reserved space in accordance
| with future needs, through "IETF Review" as defined in [BCP26]. | with future needs, through "IETF Review" as defined in [BCP26].
3. RFC Editor Considerations 3. IANA Considerations
Per this document, the RFC Editor has updated the Stream information
for [RFC1881] to IETF in place of Legacy.
4. IANA Considerations
IANA has updated the registration procedure of the "Internet Protocol IANA has updated the registration procedure of the "IPv6 Address
Version 6 Address Space" registry [IANA1] to "IETF Review". Space" registry [IANA1] to "IETF Review".
5. Security Considerations 4. Security Considerations
The security considerations of [RFC7249] apply. While having no The security considerations of [RFC7249] apply. While having no
direct security impact, carefully reviewed address allocation direct security impact, carefully reviewed address allocation
mechanisms are necessary to ensure operational address mechanisms are necessary to ensure operational address
accountability. accountability.
6. References 5. References
6.1. Normative References 5.1. Normative References
[BCP26] Best Current Practice 26, [BCP26] Best Current Practice 26,
<https://www.rfc-editor.org/info/bcp26>. <https://www.rfc-editor.org/info/bcp26>.
At the time of writing, this BCP comprises the following: At the time of writing, this BCP comprises the following:
Cotton, M., Leiba, B., and T. Narten, "Guidelines for Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
skipping to change at line 180 skipping to change at line 171
[STD86] Internet Standard 86, [STD86] Internet Standard 86,
<https://www.rfc-editor.org/info/std86>. <https://www.rfc-editor.org/info/std86>.
At the time of writing, this STD comprises the following: At the time of writing, this STD comprises the following:
Deering, S. and R. Hinden, "Internet Protocol, Version 6 Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200, (IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017, DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>. <https://www.rfc-editor.org/info/rfc8200>.
6.2. Informative References 5.2. Informative References
[IANA1] IANA, "Internet Protocol Version 6 Address Space", [IANA1] IANA, "IPv6 Address Space",
<https://www.iana.org/assignments/ipv6-address-space>. <https://www.iana.org/assignments/ipv6-address-space>.
[IANA2] IANA, "IPv6 Global Unicast Address Assignments", [IANA2] IANA, "IPv6 Global Unicast Address Space",
<https://www.iana.org/assignments/ipv6-unicast-address- <https://www.iana.org/assignments/ipv6-unicast-address-
assignments>. assignments>.
[IANA3] IANA, "IANA IPv6 Special-Purpose Address Registry", [IANA3] IANA, "IPv6 Special-Purpose Address Space",
<https://www.iana.org/assignments/iana-ipv6-special- <https://www.iana.org/assignments/iana-ipv6-special-
registry>. registry>.
[RFC1881] IAB and IESG, "IPv6 Address Allocation Management", [RFC1881] IAB and IESG, "IPv6 Address Allocation Management",
RFC 1881, DOI 10.17487/RFC1881, December 1995, RFC 1881, DOI 10.17487/RFC1881, December 1995,
<https://www.rfc-editor.org/info/rfc1881>. <https://www.rfc-editor.org/info/rfc1881>.
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
Understanding Concerning the Technical Work of the Understanding Concerning the Technical Work of the
Internet Assigned Numbers Authority", RFC 2860, Internet Assigned Numbers Authority", RFC 2860,
skipping to change at line 221 skipping to change at line 212
[RFC8729] Housley, R., Ed. and L. Daigle, Ed., "The RFC Series and [RFC8729] Housley, R., Ed. and L. Daigle, Ed., "The RFC Series and
RFC Editor", RFC 8729, DOI 10.17487/RFC8729, February RFC Editor", RFC 8729, DOI 10.17487/RFC8729, February
2020, <https://www.rfc-editor.org/info/rfc8729>. 2020, <https://www.rfc-editor.org/info/rfc8729>.
[RFC9602] Krishnan, S., "Segment Routing over IPv6 (SRv6) Segment [RFC9602] Krishnan, S., "Segment Routing over IPv6 (SRv6) Segment
Identifiers in the IPv6 Addressing Architecture", Identifiers in the IPv6 Addressing Architecture",
RFC 9602, DOI 10.17487/RFC9602, October 2024, RFC 9602, DOI 10.17487/RFC9602, October 2024,
<https://www.rfc-editor.org/info/rfc9602>. <https://www.rfc-editor.org/info/rfc9602>.
Appendix A. Acknowledgements Acknowledgements
Useful comments were received from Dale Carder, Bob Hinden, Scott Useful comments were received from Dale Carder, Bob Hinden, Scott
Kelly, Philipp Tiesel, and others. Kelly, Philipp Tiesel, and others.
Authors' Addresses Authors' Addresses
Brian E. Carpenter Brian E. Carpenter
The University of Auckland The University of Auckland
School of Computer Science School of Computer Science
PB 92019 PB 92019
 End of changes. 15 change blocks. 
36 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.48.