LRSA Requirement Modified for 8.3 Transfers
Posted: Wed, 20 April 2011
Based on ARIN’s Public Policy Mailing List (email@example.com) discussion in February 2011 and concurrent interest from ARIN’s Board of Trustees, the procedure requiring a Legacy or standard Registration Services Agreement (Legacy RSA or RSA) for resources being transferred has been revised. Effective immediately, the transferor of legacy address space is not required to have the resources under a current registration services agreement with ARIN.
In the absence of a Legacy RSA or RSA, transfer requests may take longer than expected and/or not be completed at all, because the address holder must be verified and confirmed to be a valid transferor via the vetting process. Organizations with legacy resources are strongly encouraged to enter into a registration services agreement with ARIN prior to initiating a transfer to avoid these issues. Also note that in lieu of a Legacy RSA or RSA, ARIN requires an officer attestation from the claiming address holder in order to initiate the vetting process.
This procedural change was implemented in order to remove what some organizations may have viewed as a burdensome requirement in the specified transfer process.
Transfer process documentation on the ARIN website has been updated to reflect this procedural change. Additional reformatting and minor text edits were made to improve process clarity and to make it easier to complete the various types of transfers available in the ARIN region.
Communications and Member Services
American Registry for Internet Numbers (ARIN)
These are archives of announcements, and have generally not been updated since they were published. As a result, some content, specifically links to other pages and other references may be out-of-date or no longer available.