[ARIN-consult] Consultation on ARIN Fees

[Owen DeLong]

The gotcha that is left out of this (seemingly) attractive table is:

Organization #2 with legacy /16 IPv4 under LRSA and /48 IPv6 resources in 2030
LRSA Legacy /16 IPv4 $4000 (Medium RSP) Legacy Fee Cap $375			$375
RSA		IPv6 /48 $250 (3X Small RSP)								$250
																$625 Total
And it continues to go up until eventually reaching a total of $4,250 vs. a single RSA total of MAX(IPv6,IPv4) of $4,000.

Or in the case of a smaller organization:

LRSA Legacy /22 $150->$500 ($150/object->$500 2X Small RSP)			$150     ->  $500 by 2034
RSA IPv6 /48 $150->$250 ($150/object -> $250 3X Small RSP)				$150.    ->  $250 immediately
Total change in billing:
2022: $300 -> $425
2034: $300 -> $750

Without LRSA: 2034: $300 -> $500

So ARIN is inflicting a financial penalty on the RSA side against those holding on to their LRSA fee protections.

This should stop.

An organization should not be required to pay more than MAX(LRSA,RSA) any more than an organization
with only RSA resources is required to pay MAX(IPv4, IPv6).

Owen



> On Apr 23, 2021, at 07:33 , John Curran <jcurran at arin.net> wrote:
> 
> On 23 Apr 2021, at 10:03 AM, John Curran <jcurran at arin.net <mailto:jcurran at arin.net>> wrote:
>> ...
>> For organizations that have obtained IPv6 resources from ARIN under a separate RSA, the two most common size allocations are /32 (generally issued to ISPs) and /28 (generally issued to organizations for their own use).   
> 
> The above sentence should read "For organizations that have obtained IPv6 resources from ARIN under a separate RSA, the two most common size allocations are /32 (generally issued to ISPs) and /48 (generally issued to organizations for their own use)."
> 
> (i.e. /48 not /28)
> 
>> For those legacy resources holders with /16 blocks, I suspect that maintaining the separate LRSA with ARIN for legacy resource services and the applicable legacy fee cap will make the most sense (at least for the foreseeable future.)   I’ve quickly outlined the three most common cases below for your legacy IPv6 resource holders and believe them to be correct (although it has not been proofed by second set of eyes).  I’ll note that all presume that that the organizations would not consolidate to a single agreement with ARIN for reason noted above.
> 
> As the table may not have been readable for some depending on their mail agent, I’ve quickly reformatted and attached as pdf. 
> 
> Best wishes,
> /John
> 
> John Curran
> President and CEO
> American Registry for Internet Numbers
> 
> 
> <merit.pdf>
> 
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services
> Help Desk at info at arin.net if you experience any issues.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20210426/e2e97639/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: merit.pdf
Type: application/pdf
Size: 34644 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20210426/e2e97639/attachment-0001.pdf>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20210426/e2e97639/attachment-0003.htm>