[arin-ppml] Implementation of NRPM 8.3

[Matthew Kaufman]

Thank you John for the concise answers below. Clearly a few policy tweaks would go a long way towards simplifying future transfers... I'll be submitting a couple in the near future.

Matthew Kaufman

(Sent from my iPhone)

On Apr 18, 2011, at 6:49 PM, John Curran <jcurran at arin.net> wrote:

> On Apr 18, 2011, at 8:57 PM, Benson Schliesser wrote:
> 
>> Thanks for clarifying.  Combining this with your other recent messages, here is what I conclude about ARIN's implementation of NRPM 8.3:
>> 
>> 1) ARIN will accept any legally enforceable document confirming ownership and the desire to transfer.
> 
> ARIN requires the seller to attest to being the valid address holder and 
> that they desire to transfer to the recipient.  
> 
>> 2) ARIN will accept any form of RSA with the buyer, including the standard LRSA or a negotiated LRSA, and the actual agreement language will be kept private without disclosure to the ARIN membership or community.
> 
> Not quite. The resources transferred must come under a registration services 
> agreement; this will usually be a standard RSA, unless otherwise required by
> nature of the transfer.  If legacy resources are involved, the result could 
> be an LRSA, just as can occur during the assignment of an LRSA during an 8.2
> M&A transfer.
> 
>> 3) ARIN will accept justification of need from buyers, in private and without disclosure to the ARIN membership or community.
> 
> Correct. 
> 
>> 4) ARIN will accept the transfer of any arbitrary collection of address blocks, as long as the total is in compliance with justified need.
> 
> ARIN has to implement NRPM 8.3 as written, and while it does not 
> support "any arbitrary collection of address blocks", the existing
> existing NRPM 8.3 language may be less than ideal when compared to 
> some goals in the rational of the policy. At the San Juan PPM, the
> Policy Experience report noted that there was nothing to prevent 
> transfers of resources received back out of the receiving organization, 
> and similarly it does not appear to preclude multiple successive 
> transfers (depending on the particular utilization situation).
> The above issues are compounded by the "single-aggregate" language
> applying to the demonstrated need as the policy is presently written.  
> 
> While I've mentioned some of these issues individually, I appreciate
> your question and the opportunity to put these all in one place as
> it may help folks in determining possible next steps for refinement
> of the policy.
> 
> Thanks!
> /John
> 
> John Curran
> President and CEO
> ARIN
> 
> _______________________________________________
> 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.