[address-policy-wg] APNIC temporarily freezing v4 transfers to RIPE NCC?

On Mar 11, 2015, at 9:40 AM, Nick Hilliard <nick at inex.ie> wrote:
> 
> Hi Marco,
> 
> There are two fundamental problems here, one operational- and one
> policy-related.
> 
> On 11/03/2015 13:24, Marco Schmidt wrote:
> [...]
>> ARIN has confirmed that the proposed policy text is compatible with its own
>> inter-RIR transfer policy. No potential issues have been indicated.
> 
> 1. If there is a future incompatibility between RIPE policy and ARIN policy
> which concerns resources transferred under this category:
> 
>>   - Recipients within the ARIN region will be subject to current ARIN
>> policies and sign an RSA for the resources being received.
> 
> ... whose policy applies?  RIPE's or ARIN's?

Nick - 

   ARIN's policies only apply to number resources that are contained 
   within in the ARIN registry.  To the best of my knowledge, number 
   resources which have been transferred to another regional registry 
   would be subject to that regional Internet registry's policies.  
 
   ARIN's policies most certainly apply to all resources in the ARIN 
   registry database, and could easily have implications for ability 
   to transfer to another party in the ARIN region or party in another 
   region, but once transferred to another region, I am unaware of any 
   ARIN policy that would be applicable to transferred number resources.

   I hope this helps clarify matters.

Thanks!
/John

John Curran
President and CEO
ARIN

p.s.  Note also that the ARIN Policy Development Process (PDP) allows for 
      development of policies for administration of number resources 
      "in the ARIN region" (and IANA-applicable global number resource 
      policies per the ASO MOU); it is questionable if a policy proposal
      for administration of number resources in another regional registry
      would even be within the scope for the ARIN PDP...