Summary

  • ARIN Draft Policy ARIN-2026-1 proposes allocation or registration guidance for extra-terrestrial networks beyond GEO, but its current text makes implementation depend on broader IETF, IANA, RIR and ARIN Board coordination.
  • A September individual IETF draft offers an IANA/NRO path, yet no source in the public record establishes an allocated block, an agreed global allocator or deployed service.

A routing framework starts one decision too late

ARIN’s “Taking IP to Other Planets” draft is easy to read as a question of address design: how should networks on the Moon or farther away receive prefixes that can be aggregated? The text does discuss that problem. But the first operational dependency is more basic. Before a registry can record assignments from a dedicated pool, somebody must decide that such a pool is needed, set aside address space and define who may assign from it.

The current version, dated 27 May 2026 and marked “Under Discussion,” proposes IPv4 and IPv6 allocation or registration guidance for an Extra-Terrestrial Network operating beyond the geostationary Earth orbit arc. It explicitly excludes low Earth orbit and GEO. It contemplates a dedicated pool or specific registration guidelines, with routing scalability as the rationale. The same text says implementation depends on broader coordination, including IETF and IANA determinations, agreement among the RIRs on operational responsibilities, and an ARIN Board finding that the service fits ARIN’s mission. Those are conditions, not completed actions. ARIN’s current draft

That distinction matters because “address plan” can mean two different things. One is a technical hierarchy that might make routes easier to aggregate. The other is an authority chain that determines who reserves, allocates and records numbers. The first cannot settle the second by itself.

The review and the draft describe different moments

The draft page also carries a staff/legal review published on 1 April. It assessed the 24 March version and answered “No” to whether that text was implementable as written. Its conditions included an IETF decision on whether dedicated address space was required; IANA allocation and coordination with the RIRs; a determination that ARIN service was within the Board’s mission; and concurrence by other RIRs if ARIN took that role.

That review should not be presented as a verdict on the later 27 May wording. The current text now expressly points to broader coordination. But naming the dependencies does not complete them. The policy document can describe the framework ARIN might administer; it cannot itself record an IANA allocation or bind other RIRs and ARIN’s Board.

The distinction is visible in the IETF record. Minutes from the 22 July TIPTOP session capture questions about whether one RIR would become a single point of failure, who should decide allocation and what role IANA would take. The recorded next step was to develop technical requirements and success criteria with RIR/NRO and IANA participation. In September, an individual Internet-Draft proposed that IANA allocate dedicated space and that the NRO decide allocation and assignment within celestial bodies. It is an active individual draft, not an adopted IETF policy or an allocation. July meeting minutes · September Internet-Draft

The broader Internet Numbers Registry System already has a layered arrangement: IANA, regional registries and local registries perform distinct functions. RFC 7020 describes that structure; it does not assign a new role for space networks. The IANA IPv6 tables currently show global-unicast and special-purpose entries, but the public snapshot does not name a dedicated extra-terrestrial block. That is a narrow observation about the public register, not proof that no experimental or private arrangement exists. RFC 7020 · IANA IPv6 address space · IANA IPv6 special-purpose registry

What ARIN’s October discussion can and cannot decide

ARIN says the draft is scheduled for discussion on Thursday, 22 October, at ARIN 58. The meeting can shape community views and the policy-development path; discussion alone does not allocate space or approve an operating arrangement. ARIN 58 preview

For engineers, the practical question is whether aggregation gains survive contact with allocation boundaries: are the blocks contiguous, who can assign more-specific prefixes, and how will registry records remain consistent if several bodies participate? For institutions, the question comes first: which decisions belong to the IETF, which to IANA, and which require agreement among the NRO, individual RIRs and their boards?

Until those answers appear in dated decisions and registry records, TIPTOP is a policy proposal for a possible framework. It is not yet a globally assigned address plan. The key evidence will be the sequence of decisions, each made by the body with authority to make it.

Sources