<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 22, 2021, at 02:30 , 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 22 Apr 2021, at 1:38 AM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:
<div class="">
<blockquote type="cite" class="">
<div class=""><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; 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;" class="">
<blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
For RSA plans that consist entirely of legacy number resources (i.e. blocks issued by ARIN’s predecessor registry entities and now held by the original registrant or their legal successor), then there is a cap on the total annual maintenance fees. There is
a benefit to consolidation, but indeed the legacy registration fee cap is not applicable to registration service plans include non-legacy resources. The choice to consolidate under a single RSA or not remains with the customer, and may not be optimum in all
cases.<span class="Apple-converted-space"> </span><br class="">
</blockquote>
<br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; 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;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; 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="">Right,
so this is a fancy way of saying if you don’t want to consolidate, we’re going to bill you twice for what used to be billed as a single organization.</span></div>
</blockquote>
<br class="">
</div>
<div class="">Owen - </div>
<div class=""><br class="">
</div>
<div class="">It is not particularly fancy or complicated: it is simply confirming that the choice is yours – you can consolidate under a single agreement, pay what everyone else is paying (and less than you are paying today), or can maintain separate agreements and
pay more for the sake of maintaining the provision that caps fee changes for your legacy resource holdings.</div></div></div></blockquote><div><br class=""></div>It wouldn’t actually be less than I am paying today. Today, it would be more because I’d lose the fee increase cap on two of my resources.</div><div><br class=""></div><div>(Though at the next billing cycle, I think that ends up being a wash if we keep the current billing system).</div><div><br class=""></div><div>It would be less than you’re probably about to start charging me under the proposed restructure where I’m forced into not one, but two RSPs if I’m not willing to either abandon my fee increase cap or abandon IPv6.</div><div><br class=""></div><div>Even if I went to a single RSP, unless I’m willing to abandon part or all of my IPv4 it would still be an increase vs. what I’m paying now, though not quite as steep of one as what is currently proposed.</div><div><br class=""></div><div>What I don’t understand is why ARIN can’t treat both classes of RSA under a single ORG and bill accordingly as MAX(fee_cap,std_rsa).</div><div><br class=""></div><div>Which would initially result in slightly higher fees than I currently pay and eventually (in about 2-3 years) result in my paying the same as I would pay if I consolidated RSAs and the board didn’t come up with a new creative way to restructure the fee plan to extract even more revenue while pretending it’s not a price-hike.</div><div><br class=""></div><div>Owen</div><div><br class=""></div></body></html>