<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="">Moved to ARIN-PPML per your previous advice and your request below...<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 7, 2022, at 09:25 , John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
On 7 Apr 2022, at 12:05 PM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:<br class="">
<div class="">
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Alternatively,
if ARIN starts billing LRSA+RSA organizations on the basis of MAX(IPv4, IPv6), I will also stop calling this double billing.</span></div>
</blockquote>
<br class="">
</div>
<div class="">Mr. Delong – </div>
<div class=""><br class="">
</div>
<div class="">Organizations with legacy IPv4 resources and IPv6 number resources under a registration services plan are already being invoiced one amount based on the highest category of IPv4 / IPv6 - i.e. “on the basis of MAX(IPv4, IPv6)” as you put it. </div></div></div></blockquote><div><br class=""></div>Incorrect. Those organizations no longer have legacy IPv4 resources… Once they bring the resources under RSA, they lose any meaningful “legacy” status.</div><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="">However, the “Fee Cap on IPv4 maintenance fees” provided to IPv4 legacy resource holders does not apply to such an amount invoiced because the customer is being invoiced for a registration services plan that contains multiple items [services for IPv4,
IPv6, and ASN resources] that are more than just "IPv4 maintenance fees”. Customers can keep their IPv4 resources in a separate billing relationship and then the “Fee Cap on IPv4 maintenance fees” will continue to be applied to their “IPv4 registry maintenance
fees”, exactly as expected. </div></div></div></blockquote><div><br class=""></div>It is not a “fee cap” as you express it. It is a rate of increase cap. Further, what I have repeatedly proposed would not impose that cap on fee increases for non-LRSA resources.</div><div><br class=""></div><div>I have repeatedly proposed:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Calculate LRSA fees (with cap on annual increases).</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Calculate RSA fees (no cap on annual increases).</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>MAX(LRSA,RSA) = fee paid.</div><div><br class=""></div><div>Current RSA holders are calculated in a similar manner:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Calculate RSA(IPv4)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Calculate RSA(IPv6)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>MAX(IPv4, IPv6) = fee paid.</div><div><br class=""></div><div>This would not provide for LRSA holders to pay less for their RSA resources than they are currently paying.</div><div>If the cap on their LRSA fees currently prevents their LRSA fees from exceeding their RSA fees, then that will gradually catch up over time.</div><div>This would be fair to LRSA holders.</div><div><br class=""></div><div>The current process which results in SUM(LRSA, RSA) = fee paid is (IMHO) not fair. That is why I terminated my LRSA as soon as I found a way to do so without losing my resources.</div><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="">At this point I’d suggest that we take this off the nanog mailing list - if you have further questions feel free to contact ARIN's Registration Services Helpdesk (Hours: 7 AM to 7 PM ET, Phone: +1.703.227.0660. <a href="https://www.arin.net/resources/guide/helpdesk/" class="">https://www.arin.net/resources/guide/helpdesk/</a>) </div></div></div></blockquote><div><br class=""></div>I don’t have questions in this process at all. I’ve had opinions and we disagree. I’ve expressed my opinions and you’ve expressed yours.</div><div><br class=""></div><div>Owen</div><div><br class=""></div></body></html>