Summary

  • ARIN-2026-1 is a Draft Policy under discussion, not an adopted or operational allocation service.
  • Four locks concern technical need, resource supply, ARIN authority and other-RIR concurrence.
  • BTW recommends a public prerequisite register; this is analysis, not an existing or promised ARIN system.

ARIN’s TIPTOP draft has four locked gates between a proposed NRPM clause and any operational registry service. First, the IETF would need to determine that a dedicated block is required. Second, IANA would need to allocate appropriate IPv6 and/or IPv4 space and coordinate registry services with the RIRs. Third, the ARIN Board would need to determine that providing those services fits ARIN’s mission. Fourth, the other RIRs would need to concur with ARIN serving in that capacity. These are separate external decisions, not one approval.

The draft defines an Extra-Terrestrial Network as IP infrastructure physically beyond the GEO arc. It includes lunar, Martian and deep-space deployments, while excluding LEO and GEO. It proposes eligibility for government, research and commercial operators. IPv4 provisions retain ordinary Section 4.2.4 utilization rules, with possible exceptions for high-latency cold-storage nodes or orbital relays where active-host ping verification is impractical. IPv6 is preferred, with a proposed /48 minimum or enough space for hierarchical subnetting, planetary aggregation and sparse allocation.

Aggregation would be voluntary, and more-specific advertisements would remain possible. Celestial topology is a routing hypothesis, not a proven operational outcome.

Chronology matters: the proposal appeared 3 March 2026; the Advisory Council accepted it as a Draft Policy on 19 March; the history records that status on 24 March; staff/legal review followed on 1 April; ARIN 57 discussed it on 21 April; current text is dated 27 May. That review said the draft was not implementable as written at that stage, citing resource source, jurisdiction, definitions, service-region alignment and coordination. It does not predict what later text might do.

BTW publication note: Published is the scheduled editorial date, 2026-09-06. The actual server publication time remains unset until publish-now succeeds.

Proposed prerequisite register

Lock Owner Evidence Decision state Dependency Review/expiry
Technical need IETF Formal IETF determination Not evidenced Resource and service design Set by IETF process
Resource and coordination IANA with RIRs Allocation and coordination record Not evidenced IETF need determination Set by IANA/RIR process
Mission authority ARIN Board Board determination Not evidenced Resource and service scope Board-defined review
Inter-RIR consent Other RIRs Recorded concurrence Not evidenced Proposed ARIN role and coordination RIR-defined review