[arin-ppml] DRAFT POLICY ARIN-2011-1: GLOBALLY COORDINATED TRANSFER POLICY (Legecy space)

Owen DeLong owen at delong.com
Mon Apr 11 14:06:21 EDT 2011


Space needs to be non-legacy before it is transferred. In order to take advantage of any ARIN transfer policy at least as it currently stands, you must first bring the resources under RSA or LRSA. In the case of LRSA, upon transfer, it is under RSA with the recipient and is no longer legacy. In the case of RSA, it stops being legacy space when the RSA is signed.

Owen

On Apr 11, 2011, at 9:31 AM, Knowles, John wrote:

> DRAFT POLICY ARIN-2011-1: GLOBALLY COORDINATED TRANSFER POLICY.   
>  
> How would ARIN treat Legacy space. (space issued directly from IANA pre-ARIN not covered by a RSA or LRSA.)
>  
> Example:  Let’s say Halliburton wants to transfer 34.0.0.0/10 from 34.0.0.0/8 to another RIR for their or any other companies operation  (I don’t know if this space is covered by RSA or LRSA for fun let’s say it’s NOT)   
>  
> Does ‘needs-based’ apply to legacy space not under RSA?
>  
> Thanks,
>  
> John Knowles
> JKN12-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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20110411/e196b759/attachment-0001.html>


More information about the ARIN-PPML mailing list