> On Dec 4, 2021, at 8:24 PM, Sylvain Baya <absc...@gmail.com> wrote: > > Dear NANOGers, > > Le dim. 5 déc. 2021 04:00, Owen DeLong via NANOG <nanog@nanog.org > <mailto:nanog@nanog.org>> a écrit : > I would be more than happy to consilolidate my ipv6 addresses under my lrsa, > but ARIN will not allow it. > > > Hi Owen, > ...so you want to convert community-based > INRs into legacy INRs?
Nope… I see no difference between community and legacy INRs… They’re all community INRs, the only difference is when they were registered and with which registry they were originally registered. > Please, brother, explain your peculiar need. The difference between the lRSA and the RSA is strictly some base protections on how fast the fees can increase, protections which ARIN has already, in fact, found clever ways to violate. It’s not all that peculiar… I’m just more vocal about it than others with both types of resources, in part, because those with vast holdings are more likely to participate in ARIN processes and those with little are less likely to even be fully aware of that ability. Those with vast holdings are receiving a subsidy in this latest fee structure change by the ARIN board, but that subsidy is being provided on the backs of those with less. Owen > > Thanks. > > Shalom, > --sb. > > > > Owen > > >> On Dec 4, 2021, at 17:43, John Curran <jcur...@arin.net >> <mailto:jcur...@arin.net>> wrote: >> >> Yes Owen, that is correct… >> >> If an organization insists on maintaining multiple contractual relationships >> with ARIN (for whatever reason) then they will be billed for each relation >> separately - and that is indeed likely to be more than having a single >> consolidated agreement for all number resources. >> >> Thanks, >> /John >> >> John Curran >> President and CEO >> American Registry for Internet Numbers >> >>> On Dec 4, 2021, at 7:09 PM, Owen DeLong <o...@delong.com >>> <mailto:o...@delong.com>> wrote: >>> >>> >>> >>>> On Dec 4, 2021, at 8:59 AM, John Curran <jcur...@arin.net >>>> <mailto:jcur...@arin.net>> wrote: >>>> >>>> Just for clarity - ARIN’s fee schedule is such that ISP customers (i.e. >>>> those with registration service plans) pay an annual services fee based on >>>> their higher category of IPv4 or IPv6 resources – i.e. those with IPv4 >>>> resources can obtain a corresponding size of IPv6 resources without any >>>> change in size category or increase in their annual fee. >>>> >>>> [Also worth noting - as of January 2022, all end-user customers are moving >>>> to the same registration services plan, and similarly those with just IPv4 >>>> number resources be able to obtain corresponding IPv6 resources without >>>> change to their annual fee.] >>> >>> This, whether they want to or not… In many cases resulting in significant >>> unwanted fee increases, especially if you have a mix of resources covered >>> under RSA and LRSA due to ARIN’s accounting limitations that they are >>> perversely disincentivized against fixing because it allows them to >>> essentially double-bill. >>> >>> Owen >>>> >>>
