rfc9812v2.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 August 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 Addresses" 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 71 skipping to change at line 70
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 Addresses" registry [IANA1] to the "IPv6
registry [IANA1] to the "IANA IPv6 Special-Purpose Address Registry" Special-Purpose Addresses" regisry [IANA3].
[IANA3].
At the time of writing, the allocation policy in the "Internet At the time of writing, the allocation policy in the "IPv6 Addresses"
Protocol Version 6 Address Space" registry [IANA1] was shown as "IESG 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 138 skipping to change at line 135
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. IANA Considerations 3. IANA Considerations
IANA has updated the registration procedure of the "Internet Protocol IANA has updated the registration procedure of the "IPv6 Addresses"
Version 6 Address Space" registry [IANA1] to "IETF Review". registry [IANA1] to "IETF Review".
4. 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.
5. References 5. References
skipping to change at line 176 skipping to change at line 173
<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>.
5.2. Informative References 5.2. Informative References
[IANA1] IANA, "Internet Protocol Version 6 Address Space", [IANA1] IANA, "IPv6 Addresses",
<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 Addresses",
<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 Addresses",
<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,
 End of changes. 8 change blocks. 
18 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.48.