Owen -
Correct - ARIN will not allow you to bring non-legacy resources under
an LRSA agreement.
Thanks,
/John
John Curran
President and CEO
American Registry for Internet Numbers
> On 4 Dec 2021, at 9:59 PM, Owen DeLong <o...@delong.com> wrote:
>
> I would be more than happy to consilolidate my ipv6 addresses under my lrsa,
> but ARIN will not allow it.
>
> Owen
>
>
>> On Dec 4, 2021, at 17:43, John Curran <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> wrote:
>>>
>>>
>>>
>>>> On Dec 4, 2021, at 8:59 AM, John Curran <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
>>>>
>>>
