[arin-ppml] Fwd: [arin-announce] LRSA Requirement Modified for 8.3 Transfers

David Conrad drc at virtualized.org
Thu Apr 21 00:13:12 EDT 2011

I would be happy to work with you on revising ARIN-prop-134.

I'm surprised having clearly defined and well documented community consensus definitions would be controversial.  Clearly documenting the consensus view as to what a 'legitimate address holder' is would seem to be a really good idea as we move into a world in which the probability people will contest address holdership approaches 1.  However, I'm sure I'm missing something (having been out of this particular world for so long)...


On Apr 20, 2011, at 10:05 AM, Benson Schliesser wrote:

> If you've already seen this announcement, then I apologize for the redundancy.
> I think this is a good change, and a much-needed improvement to ARIN's specified transfer process.  In light of this update, if anybody wishes to revive and/or rewrite ARIN-prop-134 (Identification of Legitimate Address Holders) then please let me know - I'm happy to collaborate.
> Cheers,
> -Benson
> Begin forwarded message:
>> From: ARIN <info at arin.net>
>> Date: April 20, 2011 9:02:24 AM CDT
>> To: <arin-announce at arin.net>
>> Subject: [arin-announce] LRSA Requirement Modified for 8.3 Transfers
>> Based on ARIN’s Public Policy Mailing List (arin-ppml at arin.net) 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.
>> Regards,
>> Communications and Member Services
>> American Registry for Internet Numbers (ARIN)
> _______________________________________________
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20110420/5d279b5e/attachment-0001.html>

More information about the ARIN-PPML mailing list