RFC 1881
IPv6 Address Allocation Management
RFC 1881: IPv6 Address Allocation Management πΈ
- Group: Network Working Group π
- Author: IAB and IESG β¨
- Category: Informational π
- Date: December 1995 π¦
- Obsoletes: none listed π§
- Updates: none listed π
Status of this Memo β¨
okay so this memo is here to provide information for the Internet community π«Ά. It does not specify an Internet standard of any kind, so please don't treat it like one π. Distribution of this memo is unlimited, so share it with everyone bestie π .
Abstract π¦
tl;dr: the IPv6 address space will be managed by the IANA for the good of the Internet community π. The IANA gets advice from the IAB and the IESG, and it hands the actual work off to the regional registries π.
Statement π
okay so the IPv6 address space must be managed for the good of the Internet community π. Good management needs at least a small amount of central authority over how the space gets delegated and allocated π.
The Internet community recognizes the Internet Assigned Numbers Authority (IANA) as the right entity to be responsible for managing the IPv6 address space π. It's giving official, it's giving trust β¨.
The IANA will rely on advice from the Internet Architecture Board (IAB) and the Internet Engineering Steering Group (IESG) when it manages the IPv6 address space π§ .
The IANA will delegate to regional (and other) registries the job of making specific address allocations to network service providers and other subregional registries πΈ. Individuals and organizations may get address allocations straight from the appropriate regional (or other) registry, or from their service provider. Main character energy, choose your path π¦.
Delegation of address space by the IANA is not irrevocable π. If, in the judgement of the IANA, a registry has seriously mishandled the address space delegated to it, the IANA may revoke the delegation, with due notice and with due consideration of the operational implications β. IANA will make every effort in such a case not to revoke addresses that are in active use, unless there are overwhelming technical reasons for doing so π«Ά. Respect the addresses that people are actually using, periodt π .
Any revenues (such as transaction fees) received with respect to the IPv6 address space should be used only for expenses related to registry activities, and not to subsidize any other activities π°. There will be no charges for the address space itself, only fees to recover the registry costs π. No cap, the address space is not for sale, it's just cost recovery β¨.
Any situation in the management of the IPv6 address space that leads to monopoly control or predatory practices must be avoided π«. Absolutely no villain arcs here π.
The IANA will develop a plan for the initial IPv6 address allocation, including a provision for the automatic allocation of IPv6 addresses to holders of IPv4 addresses π§. IANA will also develop mediation and appeals procedures concerning delegation and revocation π. So yeah, there's a whole plan for disputes too, iconic π.
Security Considerations π
Security issues are not discussed in this memo.
Plot twist, bestie: this memo doesn't talk about security at all π. Security issues are not discussed in this memo, so keep that in mind as you read it π.
Contact Information π«Ά
Internet Architecture Board
EMail: <iab@isi.edu>
Internet Engineering Steering Group
EMail: <iesg@cnri.reston.va.us>
π¦ where this page comes from
- ietf: rfc1881 1995-12
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms