Legacy Resource Services

Services Available to Legacy Resource Holders

As shown in the table above, legacy resource holders are able to both maintain their unique registration information in ARIN’s Whois, as well as update and manage this information, without having a signed Registration Services Agreement (RSA) or Legacy RSA (LRSA). However, there are certain circumstances in which a legacy resource holder may be required to sign an ARIN RSA/LRSA.

An RSA/LRSA is not required to do the following:

• Maintain your registration information in Whois
• Create an ARIN Online Profile to manage your records, as long as you are the registered Point of Contact (POC) associated with the record, and are authorized to make changes to the record as either an Admin or Tech POC

Transactions That Require Signing an RSA/LRSA

The following transactions require the signing of an 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.
• Requests to be added as a source to ARIN’s Specified Transfer Listing Service (STLS) – Resources must be covered under an RSA/LRSA in order to be added.
• RPKI is an opt-in service that allows users to certify their ARIN Internet number resources that are covered by an RSA/LRSA to help secure Internet routing.
• DNSSEC customers can use DNS Security (DNSSEC) functionality by adding DS Records as part of DNS zone management for Internet number resources that are covered by an RSA/LRSA.
• 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 that are covered by an RSA/LRSA are eligible for participation in ARIN’s IRR.
• ARIN Membership via application – Entities with a signed RSA/LRSA and Internet number resources from ARIN (end users, for example) may become members by filling out the application and paying an annual membership fee or requesting to enroll in ARIN’s Registration Services Plan.

In addition to the above transactions, certain types of transfers require 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 will 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.

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.

Using ARIN Online

You 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

Legacy resource holders 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.