Summary

  • RFC 1881 put IPv6 address-space management with IANA, advised by IAB and IESG, and specific allocations with delegated regional and other registries.
  • It separated the address space from the cost of running registries, allowed revocation of a badly mishandled delegation with protection for active addresses, and called for anti-monopoly and appeals arrangements.

The first surprise in the IAB and IESG's December 1995 RFC 1881 is its size. Two printed pages settle questions that could keep a committee fed for a winter: who stewards the new IPv6 address space, who hands it out, what a registry may charge, and who can take back a delegation. The second surprise is its arithmetic. The addresses themselves carried no charge in the memo. The people maintaining the registry could recover their costs. The cupboard was public; the clerk still needed lunch.

The authors placed overall management with IANA for the Internet community, drawing on advice from the IAB and IESG. IANA would delegate the work of specific allocations to regional and other registries. Those registries could allocate to network service providers and subregional registries. An individual or organization might obtain addresses from the appropriate registry or from a provider. The arrangement separated the authority to manage the common space from the day-to-day work of assigning pieces of it. More than one counter could serve applicants, while the stewardship chain remained visible.

Delegation came with a return address. If a registry seriously mishandled its delegated space, IANA could revoke the delegation after due notice and consideration of operational effects. The memo then applied an important brake: IANA would make every effort not to revoke addresses already in active use, unless overwhelming technical reasons required it. A registry could lose its job without every network behind it immediately losing its address. Revocation power mattered because it could correct failure; restraint mattered because the users of the space had built working connections on top of the allocation.

The fee rule was equally pointed. Revenue related to IPv6 address space, including transaction fees, was supposed to pay only for registry activities. It was not a pot for subsidizing unrelated work. There would be no charge for the address space itself, only fees to recover registry costs. That distinction did not make the operation costless. It identified what a bill was buying: administration, rather than ownership of a slice of the numbering universe. The memo also called for avoiding monopoly control and predatory practices. Scarcity of gatekeepers was a governance problem even when the address space was immense.

One sentence looked toward the first distribution. IANA was to develop an initial allocation plan that included a provision for automatic IPv6 allocation to IPv4 address holders. Another called for mediation and appeals procedures concerning delegation and revocation. Those were jobs assigned for later, not procedures printed on these two pages. The document's value lies in seeing the design choices before the machinery was filled in: a common resource, delegated registries, recoverable costs, revocable authority, continuity for active users and a path to contest a decision.

RFC 1881 was an Informational statement of 1995 intentions. It did not list later allocation outcomes or a schedule of actual fees. Read at its own date, it shows how much institutional architecture arrived with the technical excitement of IPv6. A vast new address space still needed someone to keep the books, someone able to dismiss a failing keeper, and a rule against turning the address itself into merchandise. The new numbers were plentiful. The governance clauses were not spare change.