Not a dumb question Matthew. See this in the comments sections off the Draft Policy:
This is being proposed jointly with the IETF TIPTOP working group. Please see https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-li-tiptop-address-space%2F&data=05%7C02%7Cbjones%40vt.edu%7C02731f65fa2c45dbd3c408de89cc12a8%7C6095688410ad40fa863d4f32c1e3a37a%7C0%7C0%7C639099706754518164%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FzT7LTuRq9d2VX8xJvfBnJUL%2Fq88NC6sYuf%2FnzY4u9U%3D&reserved=0<https://datatracker.ietf.org/doc/draft-li-tiptop-address-space/> and https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-many-tiptop-ip-architecture%2F&data=05%7C02%7Cbjones%40vt.edu%7C02731f65fa2c45dbd3c408de89cc12a8%7C6095688410ad40fa863d4f32c1e3a37a%7C0%7C0%7C639099706754536946%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=8oaSC2HkH6pzPUH8Ks3uf9gSNAK57I0qjFw0MmyglmM%3D&reserved=0<https://datatracker.ietf.org/doc/draft-many-tiptop-ip-architecture/> for more details. _ Brian Jones On Mar 25, 2026, at 15:19, Matthew Cowen via ARIN-PPML <[email protected]> wrote: Perhaps these are dumb questions... Is this a policy proposal uniquely for ARIN, or is it being proposed simultaneously in other RIRs? If so, what feedback have you had? Is this really only an operational problem and not specifically a policy problem? For example, couldn’t different project groups agree on which resources are obtained from whom in concertation to avoid the issues highlighted, given they are often inherently international in nature already? (i.e. Project management decides on which RIR resources are attributed to which programs: NASA, for example, could use ARIN resources, and the ESA RIPE, etc. Private programs similarly nominate which RIR resources as appropriate, perhaps with fewer constraints. All adhereing to an MoU on use and allocations) I guess I’m asking why a policy is *absolutely* required? That’s very interesting about v4 vs v6 constraints and pretty much justfies v4 use IMO. I agree that a simple carve-out for v4 in each RIR would respond to the demand. Why only space programs? However, shouldn't high-importance terestrial programs also have similar privileges? I.e., are we opening the door to have a carve out for “special” resources? My best. Begin forwarded message: From: ARIN <[email protected]> Subject: [arin-ppml] Draft Policy ARIN-2026-1: Taking IP To Other Planets (TIPTOP) Date: 24 March 2026 at 13:37:24 GMT-4 To: <[email protected]> On 19 March 2026, the ARIN Advisory Council (AC) accepted “ARIN-prop-349: Taking IP To Other Planets (TIPTOP)” as Draft Policy. Draft Policy ARIN-2026-1 is below and can be found at: https://www.arin.net/participate/policy/drafts/2026_1 You are encouraged to discuss all Draft Policies on PPML. The AC will evaluate the discussion to assess the conformance of this draft policy with ARIN's Principles of Internet number resource policy as stated in the Policy Development Process (PDP). Specifically, these principles are: * Enabling Fair and Impartial Number Resource Administration * Technically Sound * Supported by the Community The PDP can be found at: https://www.arin.net/participate/policy/pdp/ Draft Policies and Proposals under discussion can be found at: https://www.arin.net/participate/policy/drafts/ Regards, Eddie Diego Policy Analyst American Registry for Internet Numbers (ARIN) Draft Policy ARIN-2026-1: Taking IP To Other Planets (TIPTOP) Problem Statement Organizations conducting space exploration missions are deploying IP-based networking infrastructure beyond Earth orbit, including on the Moon and in other deep-space environments. These networks currently utilize address space allocated independently from multiple RIRs, including ARIN. As international missions expand and networks operated by multiple agencies interconnect to share communications infrastructure and provide operational redundancy, the use of unrelated terrestrial address allocations introduces routing scalability concerns. Existing allocations are not aligned with the topology of outer space communications networks, which may require the advertisement of numerous disaggregated prefixes when networks interconnect. Outer space communications infrastructure is expected to develop around natural clusters near celestial bodies, with limited communication links between those regions. Addressing structures that reflect these topological boundaries could improve route aggregation and long-term routing scalability. For the purposes of this policy, outer space includes the Moon and regions beyond Earth orbit, but excludes low Earth orbit (LEO) and geostationary Earth orbit (GEO). Policy Statement: ARIN may allocate IPv4 and IPv6 address space to organizations operating IP networking infrastructure in outer space, including beyond Earth orbit and on the Moon. Allocations are intended to support interagency connectivity, operational redundancy, and scalable routing in emerging space networks. Addressing structures should be organized hierarchically to reflect major celestial regions—such as the Moon, Earth–Moon Lagrange points, asteroid belt, and other planetary systems—enabling route aggregation where feasible. Participation in aggregation is voluntary, and organizations may advertise more specific prefixes when necessary. This policy applies to government, research, and commercial space operators, and encourages coordination among agencies to facilitate efficient address usage and scalable routing for outer space networks. Definitions (Add to NRPM Section 2) 2.xx Extra-Terrestrial Network (ETN) An ETN is defined as any IP-based networking infrastructure operating physically beyond the Geostationary Earth Orbit (GEO) arc, including but not limited to Lunar, Martian, or deep-space deployments. IPv4 Policy (Add to NRPM Section 4) 4.11 IPv4 Allocations for Extra-Terrestrial Networks ARIN shall maintain a dedicated pool or specific registration guidelines for organizations operating ETNs to ensure routing scalability. 4.11.1 Eligibility: Applicants must demonstrate a direct operational requirement for networking infrastructure located beyond Earth’s orbit. Eligible entities include government agencies, research institutions, and commercial operators. 4.11.2 Topological Hierarchy: To prevent global routing table exhaustion, allocations for ETNs should be issued from contiguous blocks where possible, designated by "Celestial Regions" (e.g., Luna, Mars, Lagrange Points). 4.11.3 Utilization Requirements: Standard utilization requirements (Section 4.2.4) apply, but ARIN may grant exceptions for high-latency "cold storage" nodes or orbital relay constellations where traditional "active host" pings are impractical for verification. IPv6 Policy (Add to NRPM Section 6) 6.12 IPv6 Allocations for Extra-Terrestrial Networks Due to the vast distances and high-latency nature of deep-space communications, IPv6 is the preferred protocol for ETN deployments. 6.12.1 Minimum Allocation: The minimum allocation size for an ETN operator shall be a /48, or a size sufficient to allow for hierarchical subnetting per celestial body. 6.12.2 Planetary Aggregation: Organizations are encouraged to aggregate all prefixes within a specific gravity well or orbital system to a single aggregate route for advertisement back to Terrestrial Ground Stations (TGS). 6.12.3 Sparse Allocation: ARIN will employ sparse allocation techniques within the ETN block to allow for the future growth of lunar and planetary colonies without fragmenting the space. Comments: This is being proposed jointly with the IETF TIPTOP working group. Please see https://datatracker.ietf.org/doc/draft-li-tiptop-address-space/ and https://datatracker.ietf.org/doc/draft-many-tiptop-ip-architecture/ for more details. _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues. — My best/Cordialement, Matthew Cowen _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
_______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
