[arin-ppml] ARIN discontinuing DNSSEC capability to legacy holders

John Curran jcurran at arin.net
Fri Oct 5 09:38:29 EDT 2018

On 5 Oct 2018, at 4:35 AM, hostmaster at uneedus.com<mailto:hostmaster at uneedus.com> wrote:

Just so I can get a prospective of how much money was lost for ARIN during this discussion, can someone please tell me what the current minimum cost under the current RSA for someone to hold 2 /24's?

Albert -

ARIN registry users pay annual maintenance fees.   These fees are set at $150/year/object in the database – an IPv4 address block is an object in the database, as is an IPv6 address block, as an AS number.

As of 1 July 2018, those who are legacy resource holders (i.e. a party or their legal successor that was issued resources prior to ARIN’s formation), have their total maintenance fees applicable to legacy resources capped at $125 USD annually, regardless of the number of legacy resources held under their LRSA.  This amount is actually a decrease from previous years for many legacy holders, but it was important to get consistent fees for all (and note that the total cap for legacy holders can go up by $25 year if the Board so directs.)

So, presently an organizations with 2 distinct IPv4 /24 blocks would be invoiced at $300/year as an end user organizations, but legacy resource holders with the same resources would be invoiced $125 USD due to the cap.

Note also that end-user and legacy resource holder organizations may instead opt to be ARIN Registration Service Plan customers and just pay a single fee based on total resource holdings (the same annual fee as ISPs do), and this also includes the benefit of ARIN membership.  This approach generally makes sense for organizations that have many objects in the database which total only a modest amount of address space.

The ARIN fee schedule is available here - https://www.arin.net/fees/fee_schedule.html – I hope this information helps to inform the discussion.


John Curran
President and CEO

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20181005/66b54567/attachment-0001.html>

More information about the ARIN-PPML mailing list