<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
On 9 Apr 2022, at 2:40 AM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Apr 7, 2022, at 14:54 , John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:</div>
</blockquote>
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">
<div class="">
<div class="">...</div>
</div>
</div>
</blockquote>
<div class="">The "annual limit on total maintenance fees applicable to legacy resource holder organizations” is the “fee cap” to which I have been referring, and it is only applicable to registry maintenance fees for legacy number resources – regardless of
the number of legacy resources held. </div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
While ARIN may have implemented it that way (because they kind of made a hash of it initially), the contractual language in the LRSA referred to a maximum increase in the amount paid under the LRSA of $25/year.
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Mr. DeLong - </div>
<div><br class="">
</div>
<div>Yes, ARIN did implement the change to the fee schedule as I stated above - and hence my remark that is it “fee cap” on total maintenance fees is and remains correct. </div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">...</div>
<div class="">
<div class="">As you can see from the slides — Single maintenance fee $100. I believe that persisted until some time around 2013, so I was wrong about the time between signing the LRSA and the change to the fee structure to make it fee-per resource instead
of fee-per-organization.</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
Yes, you did not have that correct (but it doesn’t matter since we have since moved to the same fee schedule for everyone based on total resources held rather than number of records in the registry.) <br class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">
<div class=""><br class="">
</div>
</div>
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">
<div class="">...</div>
<div class="">The creation of bifurcated organizations due to RSA differences was foisted upon LRSA signatories as part of the 2031 Fee structure change.</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
I believe you mean 2013 in the above. Note that ARIN doesn’t require or encourage “bifurcation"; we allow customers who wish to have multiple billing arrangements to do so - again, it is their choice. <br class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">
<div class=""><br class="">
</div>
</div>
</div>
</div>
<blockquote type="cite" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="">
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class=""></div>
<div class="">I have not been expressing an opinion, but rather explaining how the ARIN fee schedule is actually defined and the fact that there is no “double billing” involved. Customers can’t claim the legacy maintenance “fee cap” for registration service
plans with IPv6 resources in them because the "fee cap" as defined is only applicable the registry fees for legacy resources held. </div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
And I’ve been expressing both the facts of how the ARIN fee schedule has evolved to the detriment of end users and opinions as to whether that is fair to end users or not.</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Our fees are now the same for all organizations with similar amounts of number resources, regardless of whether they are end-user, ISP, hosting, cloud, data center, enterprise, etc. This can be mean that some end-user customers are paying more than they
were paying before, but other end-user customers are definitely paying less than before – particularly those with smaller amounts of total address space in multiple blocks in the registry. </div>
<div><br class="">
</div>
<div>In either case, it is the same amount paid by all other customers who receiving registry services for comparably-sized total address space. This was discussed at length during the most recent fee change consultation, and the benefit of having equitable
treatment for all customers was deemed the fairest approach for our fees. I understand you see it differently, but I do not anticipate that ARIN will be changing its fee structure again in the near future. (You are of course welcome to submit a suggestion
to the ARIN Consultation and Suggestion Process <<a href="https://www.arin.net/participate/community/acsp/" class="">https://www.arin.net/participate/community/acsp/</a>> and it will be considered the next time the fee structure is reviewed.) </div>
<div><br class="">
</div>
<div>Thanks! </div>
<div>/John</div>
<div><br class="">
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
<div><br class="">
</div>
</div>
<div><br class="">
</div>
</div>
</body>
</html>