Services Available to Organizations Holding Legacy Resources
Services Available to Legacy Resource Holders
|Service||Provided by ARIN?|
|Maintain unique registration in Whois/RDAP||Yes|
|Update and manage publicly available data in Whois/RDAP||Yes|
|Manage reverse DNS delegations||Yes|
|Maintenance of registry records (ARIN Online)||Yes|
|DNS Security (DNSSEC) access||Yes|
|Resource Public Key Infrastructure (RPKI) access||No|
|Internet Routing Registry (IRR) access||No|
To maintain your registry records, you will need to create an ARIN Online account. You will be able to make changes as long as you are the registered Point of Contact (POC) associated with the record, and you are authorized to make changes to the record as either an Admin or Tech POC.
Note: ARIN will not reclaim your legacy resources when you come to ARIN to update your records, request resources, or request to transfer your resources.
As shown in the table above, organizations without an ARIN Service Agreement and who hold legacy resources are able to both maintain their unique registration information in ARIN’s Whois/RDAP, as well as update and manage this information. However, there are certain circumstances in which an organization may be required to sign an ARIN RSA/LRSA to access particular services.
Transactions That Require Signing an RSA/LRSA
The following transactions require an organization to submit a signed RSA or LRSA:
- Approved resource transfers will require a signed RSA/LRSA depending on the type of transfer.
- Approved resource requests will require a signed RSA/LRSA.
- RPKI is an opt-in service that allows users to certify their ARIN Internet number resources are covered by an RSA/LRSA to help secure Internet routing.
- IRR – Customers can use ARIN’s IRR to share routing policies and announcements with other network operators to help avoid Internet-wide routing issues. Only Internet number resources covered by an organization’s RSA/LRSA are eligible for participation in ARIN’s IRR.
- ARIN General Membership is available to those legacy holders who sign a RSA/LRSA and then become Service Members – Service Members with a signed RSA/LRSA and IPv4 and/or IPv6 from ARIN may become General Members by submitting a request and meeting General Member criteria.
In addition to these specified transactions, certain types of transfers require an organization to have resources under an RSA/LRSA. When legacy number resources are transferred to another organization through a specified transfer (NRPM 8.3 and 8.4), the recipient organization is required to sign an RSA/LRSA, and the resources being transferred do not retain their legacy status.
In cases where number resources are transferred due to a company merger or acquisition (NRPM 8.2), the organization receiving the resources will have the option to enter into an LRSA for any IPv4 resources that were originally registered prior to 22 December 1997 and are not already covered under an RSA.
Organizations with Legacy Resources Receiving New Resources
If a legacy number resource holder requests and receives new number resources directly from ARIN, they will be required to sign an RSA/LRSA which will cover only the resources being assigned by ARIN. Any legacy number resources that an organization currently holds will retain legacy status and will not be covered under the RSA/LRSA, unless that organization specifically requests it.
Resource Management Services Available
Individuals acting on behalf of registered POCs and Org IDs can use ARIN Online at any time to perform the following resource management tasks:
- Add, delete, or modify nameservers for Reverse DNS
- Add, delete, or modify POCs associated with the resource
- Change the NetName of an IP address block or the ASName of an ASN
- Add reassignment information via a simple reassignment (only available if the legacy block is a direct allocation)
- Modify organization information to include mailing address; adding, deleting, or modifying POCs; and adding public comments
- Request new number resources as a result of a merger, acquisition, or reorganization event – documentation is required. Requirement is to sign an RSA/LRSA only upon approval and pay fees according to the current fee schedule.
- Request the transfer of number resources – requirement is to sign an RSA/LRSA only upon approval and pay fees according to the current fee schedule.
- Request an organization name change – this must be a simple name change and not the result of any merger or acquisition activity. Name change documentation will be required.
- Request an organization recovery – needed when the registered Admin or Tech POC are no longer associated with the organization and a new POC needs to be added to the organization record, or no Admin or Tech exist on the record. An RSA/LRSA is only required if the organization recovery leads to a transfer.
- Validate your POC record during ARIN’s annual POC validation by logging in to ARIN Online and accessing the list of unvalidated POCs on the Dashboard. You can also validate your POC by:
- Clicking the secure link in the validation email that ARIN sends once per year
- Replying to the validation email and putting “Correct” in the subject line
- Updating your POC record in ARIN Online if the POC information is no longer accurate
- Submit questions via Ask ARIN
Organizations with legacy resources, regardless of service agreement status, are also welcome to participate in ARIN’s Policy Development Process (PDP), including posting to mailing lists and attending ARIN Public Policy and Members Meetings.
- Services Available to Organizations Holding Legacy Resources
- Legacy Resource History
- Governmental Entity/Institution LRSA Requests
Registration Services Help Desk
7:00 AM to 7:00 PM ET