Are you really sure the organizations that will use these resource blocks want a single contact and a single contracting entity within a single legal jurisdiction?

NASA and US-based commercial space entities would likely be fine with contracting through ARIN and under US Law. However, ESA and European commercial space entities might prefer contracting through RIPE with Dutch and EU Laws. Furthermore, China and India might prefer to continue working with APNIC as they do now. Unfortunately, today, the Earth's political and legal environment will shape operations and the governance of missions to the Moon, Mars, and other celestial bodies, and the Internet Technical community isn't going to be able to change that.

Now, I would support allocating an IPv6 prefix outside 2000::/3 and a block of ASNs for Outer Space and for entities supporting spacecraft and missions to the Moon, Mars, and other celestial bodies. The distinction should be that satellites that provide service to Earth come from 2000::/3. However, satellites, ground stations, and other systems, such as ground simulators that support missions to the Moon, Mars, and other celestial bodies, should use this new prefix and block of ASNs.

But allocations from this block should be administered and registered through the current RIRs, in my opinion. Unless you want to invite an international treaty organization to administer the blocks, however, the Internet technical community has to date resisted the involvement of such an organization in Internet resource management.

So, my vision would be for the TIPTOP WG to produce a document proposing the allocation of an IPv6 block outside of 2000::/3 and a block of ASNs, define the qualifications for use of the block, and request that IANA and the RIRs develop policies to ensure allocations to organizations are consistent with those qualifications.

Thanks.