ACSP Consultation 2011.3: New Legacy Registration Services Agreement (LRSA 3.0)
Consultation Tracking Information
- Requested By: Staff
- Status: Closed
- Comments Opened: Linked to Discussion Archives: 05 October 2011
- Comments Closed: 04 November 2011
- Suggestion Number: n/a
Based on executing approximately 500+ Legacy Registration Services Agreements (LRSA) and the corresponding feedback, ARIN has constructed a new LRSA, version 3.0, and is seeking community input regarding this new version.
Like prior LRSA versions, the LRSA 3.0 will be offered to those organizations and individuals in the ARIN service region who hold legacy Internet number resources not covered by any other registration services agreement with ARIN. Existing LRSA holders are not impacted by the new 3.0 version, but may want to evaluate this new version for the benefits it could offer their organizations.
There are notable and substantive changes with this new version. These changes are highlighted in the change summary provided below with the new LRSA 3.0 available at the following URLs:
Draft Legacy RSA, Version 3
Understanding Legacy Registration Services Agreement (LRSA)
The community’s constructive thoughts on LRSA version 3.0 are welcome during this 30 day review period.
Please provide comments to email@example.com. You can subscribe to this mailing list at: http://lists.arin.net/mailman/listinfo/arin-consult.
Discussion on firstname.lastname@example.org will close on 4 November 2011. If you have any questions, please contact us at email@example.com.
On 4 November 2011 ARIN concluded its consultation with the community with regards to the Legacy Registration Services Agreement (LRSA) 3.0, the first fundamental rewrite of the LRSA introduced in 2007. The revisions found in version 3.0 were based on the execution of over 500 LRSAs and community feedback throughout that process. The consultation yielded constructive comments both on ARIN’s Public Policy Mailing List (PPML) as well as off-list.
ARIN will take one final review of LRSA 3.0 and report back to the community shortly with regard to implementation.