[arin-ppml] Draft Policy ARIN-2015-2: Modify 8.4 (Inter-RIR Transfers to Specified Recipients)

Owen DeLong owen at delong.com
Wed May 27 08:09:07 EDT 2015


You are correct, David… We should restore the anti-flip language that prohibits an organization which received a transfer from subsequently being a provider for any transfer within 24 months.

Owen

> On May 27, 2015, at 12:38 AM, David Huberman <David.Huberman at microsoft.com> wrote:
> 
>> So basically, you'd like to do an end run around the law in China and it would
>> be oh so helpful if ARIN would cooperate?
> 
> ???
> 
> For clarity:
> 
> Statement 1: If you acquire a block on the open market and transfer it into your ARIN account, NRPM 8.4 locks it into ARIN for 2 years.
> 
> Statement 2: If you need to operate in China and get Chinese transit or peering, Chinese law requires the prefix being announced be registered in CNNIC.
> 
> Statement 1 was intended to prevent flipping/speculating. 
> Statement 2 is Chinese internet policy.
> 
> A bad actor gets around Statement 1 by transferring the block to a different OrgID in ARIN via NRPM 8.2.  Once that transfer occurs, the block in the different OrgID is not subject to Statement 1 . Flipping/speculation can now occur. 
> 
> A good actor has no choice but to get around Statement 1 by transferring the block to a different OrgID in ARIN via NRPM 8.2, then doing an inter-RIR transfer to APNIC (and then to CNNIC).  BGP can now occur.
> 
> In either case, Statement 1 is no-op.
> 
> 
> _______________________________________________
> 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.




More information about the ARIN-PPML mailing list