<div dir="ltr"><div><span class="gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">Hello everyone,</span><div class="gmail-gWqWw gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual"><br></div><span class="gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">I am very interested in the discussion about the IP Address Space for Outer Space. It’s a fascinating and critical topic that needs to consider both where we are now and what we’ll need in the future.</span><div class="gmail-gWqWw gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual"><br></div><span class="gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">I'm focused on the debate between the two main ideas: grouping IP space by celestial body (like giving Mars one prefix) versus the more traditional approach of allocating space based on the space agency/provider.</span><div class="gmail-gWqWw gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual"><br></div><span class="gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">While the 'celestial body' aggregation seems clean, I'm concerned about the administrative work and policy issues it might create, especially in the early stages of deep space networking.</span><div class="gmail-gWqWw gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual"><br></div><span class="gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">Could the supporters of the celestial body model explain how it's genuinely simpler for routing and less burdensome than a model where each space agency gets its own aggregate block for all its missions, no matter where they are in space? Also, I'd like to hear more about how this model would handle the necessary coordination between all the different agencies and countries that will be operating off-world.</span><div class="gmail-gWqWw gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual"><br></div><span class="gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">In my view, starting with the path that involves the least amount of administrative friction might be a more practical way to begin, and we can adjust the policy as the space community grows.</span><div class="gmail-gWqWw gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual"><br></div><span class="gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">Best</span><div class="gmail-gWqWw gmail-rnc2Gd" style="color:rgb(31,31,31);font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:16px;font-variant-ligatures:no-contextual">Mohibul</div></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Feb 27, 2026 at 12:00 PM <<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send ARIN-PPML mailing list submissions to<br>
<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arin-ppml-request@arin.net" target="_blank">arin-ppml-request@arin.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arin-ppml-owner@arin.net" target="_blank">arin-ppml-owner@arin.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ARIN-PPML digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Addressing for other planets (Warren Kumari)<br>
2. Re: Addressing for other planets (Tony Li)<br>
3. Re: Addressing for other planets (Tony Li)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 26 Feb 2026 16:35:30 -0600<br>
From: Warren Kumari <<a href="mailto:warren@kumari.net" target="_blank">warren@kumari.net</a>><br>
To: Lee Howard <<a href="mailto:spiffnolee@yahoo.com" target="_blank">spiffnolee@yahoo.com</a>><br>
Cc: Tony Li <<a href="mailto:tony.li@tony.li" target="_blank">tony.li@tony.li</a>>, William Herrin <<a href="mailto:bill@herrin.us" target="_blank">bill@herrin.us</a>>,<br>
<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Addressing for other planets<br>
Message-ID:<br>
<CAHw9_iLJB3H=<a href="mailto:Jm2ZjpCkJvoHrC6AUQC8vi50kSA24%2BhRv-DK9A@mail.gmail.com" target="_blank">Jm2ZjpCkJvoHrC6AUQC8vi50kSA24+hRv-DK9A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Wed, Feb 25, 2026 at 9:30 AM, Lee Howard <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:<br>
<br>
> On Tuesday, February 24, 2026 at 02:28:03 PM GMT-3, William Herrin <bill@<br>
> <a href="http://herrin.us" rel="noreferrer" target="_blank">herrin.us</a>> wrote:<br>
><br>
><br>
> > Taking my Bill Herrin hat off and putting my Advisory Council hat on:<br>
><br>
> > If you want to achieve something like this at ARIN, at some point you<br>
> > would write and submit a number policy proposal which does three<br>
> > things:<br>
><br>
> It is not clear to me that ARIN can or should consider an<br>
> extra-terrestrial policy without support from the other RIRs.<br>
><br>
> In other words, I think this should be discussed as a global policy<br>
> proposal, shepherded by the NRO NC.<br>
><br>
<br>
<br>
+lots.<br>
<br>
IMO one of the RIR's could administer the ranges (or provide a backed to a<br>
new RIR), but the policy decisions and proposals are global in nature?<br>
W<br>
<br>
<br>
> > 1. Establishes criteria in the ARIN NRPM where IP addresses deployed<br>
> > in outer space are considered in use for the purpose of ARIN<br>
> > determining an organization's use and qualification.<br>
><br>
> > 2. Establishes pools of IPv4 addresses reserved for each of the<br>
> > specific celestial bodies, and the quantity reserved for each.<br>
><br>
> IPv4? How much could possibly be reserved?<br>
><br>
> > 3. Establishes pools of IPv6 addresses reserved for each of the<br>
> > specific celestial bodies, and the quantity reserved for each.<br>
><br>
> I am concerned that this scope is limited to the solar system.<br>
> Further, it is not clear to me that every "celestial body" (some of the<br>
> examples, like the lagrange points or asteroid belt, aren't even bodies)<br>
> needs the same allocation. Further, are moons numbered from their parent<br>
> planet, or from separate allocations? As proposed, Earth's moon gets as<br>
> much address space as L3 and as Pluto, but I don't know what Europa and<br>
> Deimos get.<br>
><br>
><br>
> > Finally, you'd specify that implementation would pend a request from<br>
> > IANA pursuant to publication of the relevant TIPTOP RFC.<br>
><br>
> I'm pretty sure that RFC7020, and the ASO MoU, mean that requests for<br>
> address allocations from from the ASO. The IETF can establish new protocol<br>
> registries and request protocol numbers, but addresses are in the RIR<br>
> system.<br>
><br>
> IMHO, YMMV,<br>
><br>
> Lee<br>
><br>
> _______________________________________________<br>
> ARIN-PPML<br>
> You are receiving this message because you are subscribed to the ARIN<br>
> Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>). Unsubscribe or manage<br>
> your mailing list subscription at: <a href="https://lists.arin.net/mailman/" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/</a><br>
> listinfo/arin-ppml<br>
> Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.arin.net/pipermail/arin-ppml/attachments/20260226/1a5056e2/attachment-0001.htm" rel="noreferrer" target="_blank">https://lists.arin.net/pipermail/arin-ppml/attachments/20260226/1a5056e2/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 26 Feb 2026 14:55:24 -0800<br>
From: Tony Li <<a href="mailto:tony.li@tony.li" target="_blank">tony.li@tony.li</a>><br>
To: Warren Kumari <<a href="mailto:warren@kumari.net" target="_blank">warren@kumari.net</a>><br>
Cc: Lee Howard <<a href="mailto:spiffnolee@yahoo.com" target="_blank">spiffnolee@yahoo.com</a>>, William Herrin<br>
<<a href="mailto:bill@herrin.us" target="_blank">bill@herrin.us</a>>, <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Addressing for other planets<br>
Message-ID: <<a href="mailto:2034C0F6-300C-4A98-A54B-6DFD1E9C1A55@tony.li" target="_blank">2034C0F6-300C-4A98-A54B-6DFD1E9C1A55@tony.li</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
>> In other words, I think this should be discussed as a global policy proposal, shepherded by the NRO NC.<br>
> <br>
> <br>
> +lots.<br>
> <br>
> IMO one of the RIR's could administer the ranges (or provide a backed to a new RIR), but the policy decisions and proposals are global in nature?<br>
<br>
<br>
I?ve dropped NRO NC a line.<br>
<br>
Cheers,<br>
Tony<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.arin.net/pipermail/arin-ppml/attachments/20260226/b55e3ce8/attachment-0002.htm" rel="noreferrer" target="_blank">https://lists.arin.net/pipermail/arin-ppml/attachments/20260226/b55e3ce8/attachment-0002.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 26 Feb 2026 14:55:24 -0800<br>
From: Tony Li <<a href="mailto:tony.li@tony.li" target="_blank">tony.li@tony.li</a>><br>
To: Warren Kumari <<a href="mailto:warren@kumari.net" target="_blank">warren@kumari.net</a>><br>
Cc: Lee Howard <<a href="mailto:spiffnolee@yahoo.com" target="_blank">spiffnolee@yahoo.com</a>>, William Herrin<br>
<<a href="mailto:bill@herrin.us" target="_blank">bill@herrin.us</a>>, <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Addressing for other planets<br>
Message-ID: <<a href="mailto:2034C0F6-300C-4A98-A54B-6DFD1E9C1A55@tony.li" target="_blank">2034C0F6-300C-4A98-A54B-6DFD1E9C1A55@tony.li</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
>> In other words, I think this should be discussed as a global policy proposal, shepherded by the NRO NC.<br>
> <br>
> <br>
> +lots.<br>
> <br>
> IMO one of the RIR's could administer the ranges (or provide a backed to a new RIR), but the policy decisions and proposals are global in nature?<br>
<br>
<br>
I?ve dropped NRO NC a line.<br>
<br>
Cheers,<br>
Tony<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.arin.net/pipermail/arin-ppml/attachments/20260226/b55e3ce8/attachment-0003.htm" rel="noreferrer" target="_blank">https://lists.arin.net/pipermail/arin-ppml/attachments/20260226/b55e3ce8/attachment-0003.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a><br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
<br>
------------------------------<br>
<br>
End of ARIN-PPML Digest, Vol 248, Issue 33<br>
******************************************<br>
</blockquote></div></div>