<div dir="ltr"><div dir="ltr"><div>I agree with Alejandro's suggested model; this keeps it simple at the allocation level from IANA and simple for aggregating at RIR (or whoever is the authority) and simple for celestial-body-type segmentation: /3 for planet-like+moons and /3 for non-planet (asteroids or a small rock large enough for human operations such as 1-month resource mining and then auto-remove assignment as soon as human presence is gone, etc.) – perhaps that old standard "Mobile <span class="gmail-Q6ibn gmail-ng">IPv6",</span> which was never really used in real operations, might also come into play for space networking, enabling the auto-mobility of subnets from one asteroid/rock to another as human operations move that way.</div><div><br></div><div>The contention point then becomes:</div><div>What is the prefix length per planet? /10? /11? /16? It has to be large enough for future scaling on the planet but small enough not to cause exhaustion.</div><div>Likewise, prefix length or aggregation for non-planet-type bodies. Perhaps someone can run calculations based on real numbers of celestial bodies to determine the optimal prefix length allocation and sizing for minimised wastage, without introducing IPv4 psychosis into space. Also perhaps it's wise to assume RFC9663 may become widely used for space networking endpoints in the future. This would greatly impact subnet modelling.</div><div><br></div><div>I'd think it's unlikely other planets will have 8.3 billion humans anytime soon, and by the time it happens, we'll probably have moved beyond 128 bits.</div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><font color="#000000" face="arial, sans-serif"><br><b>--</b><br></font><div><font color="#000000" face="arial, sans-serif">Best Regards</font></div><div><font color="#000000" face="arial, sans-serif">Daryll Swer</font></div><div><font color="#000000" face="arial, sans-serif">Website: <a href="https://l.shortlink.es/l/491acc4f24e6ad057c5284ee3da28e8f464790a0?u=2153471" target="_blank">daryllswer.com</a></font></div></div></div></div><br></div><br><img width="0" height="0" class="mailtrack-img" alt="" style="display:flex" src="https://mailtrack.io/trace/mail/39f97bb4ff993123a9cbd6d23af4e3279e4f6508.png?u=2153471"><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 20 Feb 2026 at 19:52, Alejandro Acosta <<a href="mailto:alejandroacostaalamo@gmail.com">alejandroacostaalamo@gmail.com</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"><u></u>
<div>
<p>For me, it makes a lot of sense. However, I’d add one more layer:
I would suggest a separate `/3` subnet just for planets
(unfortunately other planets than earth) and another `/3` for
other objects (like asteroids or Pluto, which isn’t actually a
planet). Addresses for natural satellites would fall within the
address space of their respective planets.”</p>
<p>Alejandro,</p>
<p><br>
</p>
<div>On 20/2/26 9:54 AM, Daryll Swer via
ARIN-PPML wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>
<div>If we create GUA
aggregates per planet (like we did on Earth with
2000::/3), should we also create /10s per planet,
excluding Earth? I'm curious to hear what people think we
should do for prefix length allocation to large bodies
(planets) and possibly moons as well.</div>
<div><br>
</div>
<div>I don't think we
should use 2000::/3 for anything outside Earth's immediate
orbit, maybe the Moon at most. I think a <b>different</b> /3
from IANA should be used for space networking. This would
allow clean aggregation per large body (planet or
equivalent) and clean <span>segmentations</span>
across RIRs (if we decide RIRs have allocation authority
for space networking).</div>
</div>
<div>
<div dir="ltr" class="gmail_signature">
<div dir="ltr"><font color="#000000" face="arial, sans-serif"><br>
<b>--</b><br>
</font>
<div><font color="#000000" face="arial, sans-serif">Best
Regards</font></div>
<div><font color="#000000" face="arial, sans-serif">Daryll
Swer</font></div>
<div><font color="#000000" face="arial, sans-serif">Website:
<a href="https://l.shortlink.es/l/19174986ed03cd89016996337141dbbdd6d81d1f?u=2153471" target="_blank">daryllswer.com</a></font></div>
</div>
</div>
</div>
<br>
</div>
<br>
<img width="0" height="0" alt="" style="display: flex;" src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 20 Feb 2026 at
02:32, Tony Li <<a href="mailto:tony.li@tony.li" target="_blank">tony.li@tony.li</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">
<div>
<div style="color:rgb(0,0,0)">Hi,</div>
<div style="color:rgb(0,0,0)"><br>
</div>
<div style="color:rgb(0,0,0)">As part of the IETF TIPTOP
working group, we are working towards enabling the
Internet in outer space. We would like to direct your
attention to a couple of recent Internet drafts that may
be of interest:</div>
<div style="color:rgb(0,0,0)"><br>
</div>
<div>
<div style="color:rgb(0,0,0);display:block">
<div style="display:inline-block" role="link"><a style="border-radius:10px;font-family:-apple-system,Helvetica,Arial,sans-serif;display:block;width:300px;overflow:hidden;text-decoration:none" rel="nofollow" href="https://l.shortlink.es/l/bb3f349606709332df0d907e89aff9dc4b7929e6?u=2153471" dir="ltr" role="button" width="300" target="_blank">
<table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:rgb(230,230,230);font-family:-apple-system,Helvetica,Arial,sans-serif" cellpadding="0" cellspacing="0" border="0" width="300">
<tbody>
<tr>
<td>
<table bgcolor="#E6E6E6" cellpadding="0" cellspacing="0" width="300" style="table-layout:fixed;font-family:-apple-system,Helvetica,Arial,sans-serif;background-color:rgb(230,230,230)">
<tbody>
<tr>
<td style="padding:8px 0px">
<div style="max-width:100%;margin:0px 16px;overflow:hidden">
<div style="font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left"><a rel="nofollow" href="https://l.shortlink.es/l/1813710a45f7ad72c654d1b8969aabb76b2dbe22?u=2153471" style="text-decoration:none" target="_blank"><font color="#272727" style="color:rgba(0,0,0,0.847)">An Architecture for IP in Deep Space</font></a></div>
<div style="font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left"><a rel="nofollow" href="https://l.shortlink.es/l/f580ac31fc41293e66404782d04f732f152894b7?u=2153471" style="text-decoration:none" target="_blank"><font color="#808080" style="color:rgba(0,0,0,0.498)">datatracker.ietf.org</font></a></div>
</div>
</td>
<td style="padding:6px 12px 6px 0px" width="30"><a rel="nofollow" href="https://l.shortlink.es/l/6ee9737ad750a5813c6b12f219cecf793f629eba?u=2153471" target="_blank"><img style="display: inline-block; width: 30px; height: 30px; border-radius: 3px;" width="30" height="30" alt="ietf-logo-nor-180.png" src="cid:ii_19c7b77fbf4b54048e51"></a></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</a></div>
</div>
<font color="#000000"><span></span></font></div>
<div>
<div style="color:rgb(0,0,0);display:block">
<div style="display:inline-block" role="link"><a style="border-radius:10px;font-family:-apple-system,Helvetica,Arial,sans-serif;display:block;width:300px;overflow:hidden;text-decoration:none" rel="nofollow" href="https://l.shortlink.es/l/82399640efdcef95edca46fbe1251937a241d506?u=2153471" dir="ltr" role="button" width="300" target="_blank">
<table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:rgb(230,230,230);font-family:-apple-system,Helvetica,Arial,sans-serif" cellpadding="0" cellspacing="0" border="0" width="300">
<tbody>
<tr>
<td>
<table bgcolor="#E6E6E6" cellpadding="0" cellspacing="0" width="300" style="table-layout:fixed;font-family:-apple-system,Helvetica,Arial,sans-serif;background-color:rgb(230,230,230)">
<tbody>
<tr>
<td style="padding:8px 0px">
<div style="max-width:100%;margin:0px 16px;overflow:hidden">
<div style="font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left"><a rel="nofollow" href="https://l.shortlink.es/l/dfcc23dabc86dcb97704246bd5d4021672db38ae?u=2153471" style="text-decoration:none" target="_blank"><font color="#272727" style="color:rgba(0,0,0,0.847)">IP Address Space for Outer Space</font></a></div>
<div style="font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left"><a rel="nofollow" href="https://l.shortlink.es/l/bd548e3926b6d9a2b5aa00c5aff588aa31036816?u=2153471" style="text-decoration:none" target="_blank"><font color="#808080" style="color:rgba(0,0,0,0.498)">datatracker.ietf.org</font></a></div>
</div>
</td>
<td style="padding:6px 12px 6px 0px" width="30"><a rel="nofollow" href="https://l.shortlink.es/l/a6be19550bc26f1ed1a4c70512c05f8660594abd?u=2153471" target="_blank"><img style="display: inline-block; width: 30px; height: 30px; border-radius: 3px;" width="0" height="0" alt="ietf-logo-nor-180.png" src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7"></a></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</a></div>
</div>
<font color="#000000"><span></span></font></div>
<div style="color:rgb(0,0,0)"><br>
</div>
<div style="color:rgb(0,0,0)">The latter has direct
implications for the ARIN community,</div>
<div style="color:rgb(0,0,0)"><br>
</div>
<div style="color:rgb(0,0,0)">I would welcome any and all
comments.</div>
<div style="color:rgb(0,0,0)"><br>
</div>
<div style="color:rgb(0,0,0)">Regards,</div>
<div style="color:rgb(0,0,0)">Tony</div>
</div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://l.shortlink.es/l/b797cf2006b76fefc5570004428285e50c281890?u=2153471" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you
experience any issues.<br>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a href="https://l.shortlink.es/l/71422d60639247323da91e07a7492f203d97e2cc?u=2153471" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://l.shortlink.es/l/80aa7d1fa73cab6f147abb79995efb94875029fd?u=2153471" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div></div>