Summary

  • The September draft asks IANA for a space-related IPv6 allocation and names the NRO in its proposed distribution model; it remains an individual, unendorsed Internet-Draft, not an adopted policy.
  • The NRO says it does not make number-resource policy. The draft does not explain how its proposed role would connect to the five RIR communities’ separate policy processes, including RIPE.

A proposal can distribute without deciding

A request for address space looks like an engineering task: reserve a block, divide it into usable prefixes and keep routing manageable. The September 2026 Internet-Draft on IPv6 space for space environments goes further. It asks IANA to allocate a block and says the Number Resource Organization (NRO) would determine how resources are structured, assigned and distributed for and within celestial bodies. Another sentence says the registry system would establish allocation policies.

That wording creates a governance interface. It does not show that anyone has exercised authority, that an allocation has occurred or that a policy has changed. The document’s first-page boilerplate says “Intended status: Standards Track”; Datatracker metadata currently lists both RFC stream and intended RFC status as “None”. Datatracker identifies it as an active individual Internet-Draft marked “I-D Exists” and says I-Ds have no formal standing in the IETF standards process. That is work in progress, not an institutional decision.

The question is not whether global coordination could be useful. A block spanning regions would need technical coordination. The question is how that coordination meets the policy authority that decides who may receive resources, under which conditions, and with what review or remedy.

Coordination is not policy authority

The NRO’s own description draws a line: it coordinates the five Regional Internet Registries and serves as ICANN’s Address Supporting Organization, but it does not develop, approve or implement regional or global number-resource policy. Regional communities define policy through their own open processes. The FAQ adds a distinct global route: with RIR input, the NRO reviews and develops recommendations on global IP address policy for ICANN Board ratification. That recommendation role does not specify whether this draft seeks a global rule or five regional decisions coordinated by the NRO.

The NRO’s registry-system overview likewise distinguishes RIR registry services from coordination among the RIRs.

The September draft places the NRO in a proposed distribution chain while assigning policy establishment to “the registry system”. Those words do not identify a decision procedure. Would distribution execute policies already agreed by RIR communities, recommend a model to them, or create a new common policy instrument? The text does not say. “The registry system” cannot be assumed to mean one policy-making body.

A separate individual TIPTOP draft from May 2026 described another route: IANA would delegate space to existing RIRs, which would set policy through their normal processes. It is a useful architectural comparison, not evidence that the newer text supersedes it or that either model has been adopted. The changed wording calls for clarification; it does not prove a dispute.

RIPE’s process is relevant, not yet implicated

RIPE NCC provides regional registry services and supports the RIPE community’s open policy development process. Published IPv6 policy, including RIPE-738, is the current regional baseline. A space-specific regime would need to explain which questions belong to RIPE, which can be coordinated across RIRs, and what happens when a global distribution rule meets a regional policy decision.

The September document is not a RIPE proposal. Yet it invokes a cross-RIR role and a registry system, while RIPE’s institutional model locates policy development in its community. The sources reviewed do not show RIPE NCC endorsing the draft, opening a policy proposal on the community’s behalf or accepting a new allocation duty. IETF 126 TIPTOP minutes record a plan for an interim to define technical requirements with IANA and RIR representatives. Planned technical discussion is not authorization to allocate or govern a block.

Make the handoff testable

A usable specification can identify the forum responsible for eligibility and allocation criteria; say whether the NRO coordinates, recommends or executes; name the RIR responsible for registry records; and describe assignment decisions, objections, correction and appeal. It should also explain how the model works when a resource spans regions or regional policies differ.

These details decide whether a technical allocation can be administered consistently without silently moving policy authority. If separate regional decisions are expected, the document should explain how they compose. If it proposes a common rule, it should state who adopts it and how each community participates. Until then, “the registry system” should not stand in for a named decision-maker.

The record supports a narrow conclusion: the new draft proposes NRO-coordinated distribution but does not document the policy handoff behind it. RIPE’s process has not been displaced. The next useful evidence is a revised draft that shows where coordination ends, where policy begins, and how an operator or applicant can tell which rule applies.

Sources