[ARIN-consult] [arin-announce] Consultation on ARIN Fees

[John Curran]

On 10 Apr 2021, at 9:16 PM, Owen DeLong <owen at delong.com<mailto:owen at delong.com>> wrote:

On Apr 10, 2021, at 3:40 PM, John Curran <jcurran at arin.net<mailto:jcurran at arin.net>> wrote:
(Owen wrote)
I have no problem with ARIN increasing its fees to cover costs. I just want to see it done on an equitable basis and not on the backs of the smallest end users.

You should be pleased then, as the proposed fee change is not on the backs of the smallest end-users – the average change for those with /20 in IPv4 number resources or less (7130 customers of the 8000)) is an increase of $126 (i.e. approximately $900K of the $3.8M total.)

Sure… I’ve always felt that there was an equity issue with the larger end-users paying so little, but how is that remaining $2.9M distributed?

Owen -

As sought, here is the distribution of the fee change, as summarized by registration service plan fee category –

[cid:image001.png at 01D72ECA.37D77EA0]

(I’d also like to thank the folks inside ARIN who made this chart appear in record time… :-)

I will note that customers with up to a /16 in IPv4 space (Medium Category) and /14 in IPv4 space (Large Category) [up to /24 & /20 in IPv6 resources respectively] are the ones who bear the brunt of the fee change – these customers have been paying approx $500 and $1000 annually compared to others with similar holdings who have been paying $4000 and $8000 respectively on an annual basis for the same registry services from ARIN.

Thanks,
/John

John Curran
President and CEO
American Registry for Internet Numbers




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20210411/1c26ce00/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 152772 bytes
Desc: image001.png
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20210411/1c26ce00/attachment-0001.png>