<div dir="ltr"><img width="0" height="0" class="mailtrack-img" alt="" style="display:flex" src="https://mailtrack.io/trace/mail/d927c7f84255970711cd039168285e608f94ce4d.png?u=2153471"><div dir="ltr"><div>John Curran<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">did you gain any perspective into number of network operators per planetary body and number of planetary bodies they are envisioning? </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Is there any insight into what common registry services (whois/RDAP, reverse DNS, IRR, RPKI) they expect to operate across these prefixes?</blockquote><div> </div><div>Not yet. From what I understand from the limited 'space' contacts I know, this topic is brand new to them, and they weren't aware the IETF has begun work on the subject.</div><div><br></div><div>Perhaps some space operators are already on the IETF, RIPE, or this ARIN mailing list. I'm not sure. If you folks are here, please join this discussion; we need your real-life, non-theoretical data and insights.</div><div><br></div><div>My understanding is that the current "hot" topic in space networking is IP geolocation (circa NANOG 96). No IPv6, yet. This is completely fresh and new.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Is it possible that any of them could join the discussion here or on the corresponding RIPE mailing list?</blockquote><div>I've, in a personal capacity, requested they join the discussions on either this ARIN mailing list or the IETF (with those two drafts in the email chain).</div><div>We can hope they and more from the space networking industry join in. We need their hands-on operational data because it is valuable to the discussion, if not its foundation.</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/7a8c0b243d40cc362cc164fd13927b92ecf864b4?u=2153471" target="_blank">daryllswer.com</a></font></div></div></div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 20 Feb 2026 at 22:41, John Curran <<a href="mailto:jcurran@arin.net">jcurran@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">
<div>
Daryll -
<div><br>
</div>
<div>
<div><span style="white-space:pre-wrap"></span>Modeling requires engineering to specific assumptions - did you gain any perspective into number of network operators per planetary body and number of planetary bodies they are envisioning?</div>
<div><span style="white-space:pre-wrap"></span>Is there any insight into what common registry services (whois/RDAP, reverse DNS, IRR, RPKI) they expect to operate across these prefixes?</div>
<div><span style="white-space:pre-wrap"></span>Is it possible that any of them could join the discussion here or on the corresponding RIPE mailing list?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>/John</div>
<div><br>
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
</div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div>On Feb 20, 2026, at 12:04 PM, Daryll Swer via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:</div>
<br>
<div>
<div dir="ltr">
<div dir="ltr">
<div>I looked into some people that I know who currently operate real-life space networks:</div>
<div>The sentiment I'm getting is: This is serious; it's not a joke, and we/they want IPv6 for space to be properly subnet modelled, with no IPv4 psychosis or, what I personally dislike even more, /48 psychosis in the DFZ table. Has anyone looked at /48's growth
lately? Yeah, not pleasant. I do not want that in that space.</div>
<div><br>
</div>
<div>It's unclear which real-life space network operator(s) are treating this as a joke or prank; <span>perhaps</span> Fernando Frediani has industry insights that we are unaware of.</div>
<div><br>
</div>
<div>I, for one, am not known for having a sense of humour in a professional setting. Work is work, engineering is engineering, and we must evaluate and assess data, facts, figures and peer reviews.</div>
<div>
<div dir="ltr" class="gmail_signature">
<div dir="ltr"><font face="arial, sans-serif"><br>
<b>--</b><br>
</font>
<div><font face="arial, sans-serif">Best Regards</font></div>
<div><font face="arial, sans-serif">Daryll Swer</font></div>
<div><font face="arial, sans-serif">Website: <a href="https://l.shortlink.es/l/5c534d492ecd030217c5e35e643b3493eb6e10a8?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 22:11, 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">
<br>
Hi Fernando,<br>
<br>
> That's my point. What is the issue of they using the already owned prefixes they got from their respective RIR and if necessary request more ?<br>
<br>
We end up with a swamp in space, with grossly inefficient routing, no aggregation, coupled with low bandwidth, long latencies, anemic processors, and insufficient memory.<br>
<br>
I would like to avoid that.<br>
<br>
Regards,<br>
Tony<br>
<br>
_______________________________________________<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/7bd6a057798fa50960e3c03485cd7d5ba672ec08?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>
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/e0cf2358ddea413bafc8994275e66630851fb7d3?u=2153471" 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>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote></div></div>