Summary

  • ARIN’s current 27 May text for Draft Policy ARIN-2026-1 remains “Under Discussion” and says ARIN may allocate IPv4 and IPv6 address space for outer-space networks.
  • Draft Advisory Council minutes and a separate individual Internet-Draft describe an IPv6-only direction and an IANA/NRO model. ARIN 58 is scheduled to discuss the policy on 22 October; no policy change or allocation is established.

Two records, two scopes

The question is no longer only whether space networks need registry policy. The public record now contains two different descriptions of what that policy might authorize.

ARIN’s current page for Draft Policy ARIN-2026-1 labels it “Under Discussion” and dates the text 27 May 2026. The opening statement says ARIN may allocate IPv4 and IPv6 address space to organizations operating IP networking infrastructure in outer space. The draft has a section for each address family.

The next dated account is a set of draft Advisory Council minutes from 17 September. They record Alison Wood saying TIPTOP was moving forward with IPv6 only and that removing IPv4 was the largest item requiring a text change. The minutes also say the revised slides had not yet been submitted. They describe a direction, not an approved decision or a replacement policy text.

A document published the day before those minutes adds a different allocation design. The Internet-Draft “IPv6 Address Space for Space” asks IANA to allocate space for space environments and assigns the Number Resource Organization a role in structuring, assigning and distributing resources for celestial bodies. IETF Datatracker classifies it as an active individual Internet-Draft. An individual draft has no IETF endorsement or formal standing in the standards process; a reference to TIPTOP in its header does not make it a working-group document.

The allocator matters as much as the address family

The contrast is substantive. ARIN’s posted proposal describes ARIN allocating both IPv4 and IPv6 to eligible organizations. The newer individual draft describes an IANA allocation followed by an NRO-designed distribution structure, and its title and text focus on IPv6. These are proposals at different stages, not two live services and not a completed transfer of authority.

That distinction matters to anyone trying to evaluate the policy’s eventual reach. Address-family scope says what kind of resource the rule covers; the allocator and distribution path say which institution would make the first assignment and how later assignments might be organized. A policy sentence that still includes IPv4 cannot by itself tell readers whether the current TIPTOP direction has narrowed to IPv6, or whether ARIN’s role would change under the separate model.

ARIN’s agenda schedules ARIN-2026-1 for Policy Block 2 at 1:30 p.m. on 22 October, presented by Alison Wood. That is a discussion slot, not an outcome. Until a dated revision appears, the May text remains the published ARIN baseline. The September minutes remain draft, and the individual Internet-Draft remains unendorsed. None of the reviewed records shows IANA assigning space, the NRO approving a distribution plan, an RIR agreement, or deployment by a space network.

For the meeting, the useful comparison is a dated redline: whether IPv4 is removed, whether IPv6 remains the sole family, who would allocate the initial block, and which body would distribute it. Without that comparison, readers must infer the intended policy from records that describe different scopes.

Analysis

Watch for a revised ARIN-2026-1 text and its date, the slides and minutes from the 22 October discussion, and an explicit statement about the allocator and address-family scope. On the IETF side, the meaningful status change would be a formal working-group adoption step or a later standards document; the individual draft’s publication alone does not cross that line. Any IANA, NRO or RIR action would need its own dated record.

If the ARIN draft is revised to IPv6 only, the public question becomes whether that change also alters the proposed route for initial allocation. If it retains IPv4 and ARIN allocation language, the gap with the September direction remains. Neither outcome can be inferred from the meeting listing.

Sources