<div dir="ltr"><div dir="ltr">First, compliance, regulation, and enforcement are stronger terms than I intended. I'm thinking more along the lines of mutual understanding, shared intent, and consensus.<div><br></div><div>Early in this discussion, others and I asked for more details about what is meant by "celestial body aggregation". I believe this means that relatively large address pools will be reserved for use on and around other celestial bodies. Allocations will then be made from these reserved pools to ETNs and their operators. I think this much is generally agreed upon. However, which celestial bodies receive which size reserved pools is a detail that needs to be resolved before ARIN or anyone else can begin allocating to ETN operators on such a basis.</div><div><br></div><div>Furthermore, to be effective and to avoid future renumbering or address block fragmentation around celestial bodies, it seems likely that very large reserve pools will be necessary and will be of interest to the Internet Registry System as a whole, the IETF, space agencies, other space and Internet operators. What processes will be used to reach consensus regarding these parameters? Ideas like "slow start" seem out of place; conservation and other goals will likely have new balance points within a celestial-body aggregation-allocation regime, compared to the provider-based aggregation-allocation regime we have today. </div><div><br></div><div>I'm doubtful these issues can be effectively resolved within IPv4, given that IPv4 allocations have been exhausted. The only possible solutions I see for IPv4 are either to allocate Class-E (<a href="http://240.0.0.0/4" target="_blank">240.0.0.0/4</a>) for ETN use or to have NASA or another government agency provide an IPv4 block for ETN use. </div><div><br></div><div>For IPv6, I envision asking the IETF to allocate a block outside 2000::/3 for ETN use, and then using sparse allocation within that block, probably starting with allocations for the Moon and Mars, then other celestial bodies as necessary.</div><div><br></div><div>Finally, I think an ETN advisory group should be created that includes representatives from space agencies, other space operators, and the Internet number resource community as a whole.</div><div><br></div><div>However, nothing in the current proposal addresses how these many issues will be resolved.</div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, May 19, 2026 at 11:48 PM Alison Wood <<a href="mailto:Alison.WOOD@das.oregon.gov">Alison.WOOD@das.oregon.gov</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 class="msg-2524596009922387509">
<div dir="ltr">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
Thank you for the suggestion!</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
One intended goal of the policy was aggregation, but compliance was not defined. I would appreciate any suggestions that you have on compliance and enforcing the aggregation per celestial body.</div>
<div id="m_-2524596009922387509appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="m_-2524596009922387509divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a>> on behalf of David Farmer via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>><br>
<b>Sent:</b> Tuesday, May 19, 2026 11:48 AM<br>
<b>To:</b> Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>><br>
<b>Cc:</b> <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a> <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>><br>
<b>Subject:</b> Re: [arin-ppml] TIPTOP</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div dir="ltr"><br>
</div>
<div>
<div dir="ltr">On Thu, May 14, 2026 at 5:12 PM Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
</div>
<div>
<div>
<div dir="ltr">On Thu, May 14, 2026 at 13:07 Tony Li <<a href="mailto:tony1athome@gmail.com" target="_blank">tony1athome@gmail.com</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Hi Fernando,<br>
<br>
> Honestly, what is the demand of it in terms of devices, networks right now and for the next few years ?<br>
<br>
In 2025, there were about a dozen space missions of note. I would expect the same with a slow linear increase for the foreseeable future.</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">
<div dir="auto" style="font-size:inherit"><span style="color:rgb(0,0,0);font-family:-apple-system,sans-serif;font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">+1
to find a policy solution to support this need.</span></div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Demand doesn't matter. A need presented by a community does. They(network and other engineers building these networks) already have demand using the resources. </div>
<div dir="auto"><br>
</div>
<div dir="auto">There's no good reason to argue if aggregation benefits are important both policy or <span style="font-family:-apple-system,sans-serif">technical. ICP2 and the NRPM say so. The high level resource engineering discussed is a “duh” moment. Physics.</span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I also support a policy to allocate resources for use in deep space and to aggregate them around celestial bodies. However, the current policy doesn't seem to include any kind of commitment from the entities receiving the resources to use them in accordance
with the proposed aggregation. Without even a theoretical commitment by the resource holders to implement the intended aggregation, how will it ever be achieved? Obviously, there will be limits to what ARIN can contractually enforce; nevertheless, it seems
prudent that resources received under this policy have some minimal exceptions to implement the intended aggregation. Without at least a minimal commitment to fulfill the intended aggregation, creating a new policy regime seems unwise.</div>
<div> </div>
</div>
<span>-- </span><br>
<div dir="ltr">
<div dir="ltr">
<div>Thank you / Ho Pidamayado / Miigwech</div>
===============================================<br>
David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">
Email:farmer@umn.edu</a><br>
Networking & Telecommunication Services<br>
Office of Information Technology<br>
University of Minnesota <br>
2829 University Ave SE Phone: 612-626-0815<br>
Minneapolis, MN 55414 Cell: 612-812-9952<br>
=============================================== </div>
</div>
</div>
</div>
</div>
</div></blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Thank you / Ho Pidamayado / Miigwech</div>===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2829 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414 Cell: 612-812-9952<br>=============================================== </div></div></div>