[arin-ppml] ARIN-prop-143 Clarify Specified Transfer RSA Requirement

[Owen DeLong]

I oppose this proposal. Transfer recipients should be required to sign
the current standard RSA and not a less restrictive RSA.

Owen

On May 2, 2011, at 10:59 AM, ARIN wrote:

> ARIN-prop-143 Clarify Specified Transfer RSA Requirement
> 
> ARIN received the following policy proposal and is posting it to the
> Public Policy Mailing List (PPML) in accordance with the Policy
> Development Process.
> 
> The ARIN Advisory Council (AC) will review the proposal at their next
> regularly scheduled meeting (if the period before the next regularly
> scheduled meeting is less than 10 days, then the period may be extended
> to the subsequent regularly scheduled meeting). The AC will decide how
> to utilize the proposal and announce the decision to the PPML.
> 
> The AC invites everyone to comment on the proposal on the PPML,
> particularly their support or non-support and the reasoning
> behind their opinion. Such participation contributes to a thorough
> vetting and provides important guidance to the AC in their deliberations.
> 
> Draft Policies and Proposals under discussion can be found at:
> https://www.arin.net/policy/proposals/index.html
> 
> The ARIN Policy Development Process can be found at:
> https://www.arin.net/policy/pdp.html
> 
> Mailing list subscription information can be found
> at: https://www.arin.net/mailing_lists/
> 
> Regards,
> 
> Communications and Member Services
> American Registry for Internet Numbers (ARIN)
> 
> 
> ## * ##
> 
> 
> ARIN-prop-143 Clarify Specified Transfer RSA Requirement
> 
> Proposal Originator: Matthew Kaufman
> 
> Proposal Version: 1
> 
> Date: 2 May 2011
> 
> Proposal type: new
> 
> Policy term: permanent
> 
> Policy statement:
> 
> Replace section 8.3 "Such transferred number resources may only be
> received under RSA" with "Such transferred number resources may only be
> received under a registration services agreement"
> 
> Add to section 8.3 "It is the intent of this policy that the
> registration services agreement under which the transferred resources
> are received SHOULD be at least as restrictive as the registration
> services agreement that covers these resources prior to the transfer.
> Legacy resources that are not currently covered by a registration
> services agreement should be received under a Legacy Registration
> Services Agreement (or at the recipient's option, the standard
> Registration Services Agreement). Legacy resources that are currently
> covered by a Legacy Registration Services Agreement should be received
> under a Legacy Registration Services Agreement which is at least as
> restrictive as the previous LRSA (or at the recipient's option, the
> standard Registration Services Agreement). Resources that are currently
> covered under the standard Registration Services Agreement should be
> received under the standard Registration Services Agreement. ARIN staff
> shall report periodically on any required deviation from this paragraph,
> including modifications that have been required to either the standard
> forms of the LRSA or RSA."
> 
> Rationale:
> 
> Clarifies the NRPM to reflect policy as currently implemented and to
> properly reflect that legacy resources may be received, at the option of
> the recipient, under either the standard RSA or the legacy RSA.
> 
> Also clarifies the NRPM to reflect that registration services agreements
> may be modified from standard if necessary for the purposes of effecting
> Section 8.3 transfers.
> 
> Requires transparency for deviations from the recommended policy and/or
> customized registration services agreements.
> 
> Timetable for implementation: immediate
> 
> _______________________________________________
> PPML
> 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.