Hi John

 Your M&A transfer may indeed be rejected if you do not have adequate
documentation; see my prior email regarding list of acceptable documents.


As refer to your list of acceptable documents,  please help to resend the
list to me cos i cannot find your previous email.

thanks,
Niki



On Sat, Apr 5, 2014 at 10:58 AM, John Curran <jcur...@arin.net> wrote:

>  On Apr 4, 2014, at 10:51 PM, xiaofan yang <nikiyan...@gmail.com> wrote:
>
>  Please explain  what do you mean by  " pursue another transfer request
> to bring your
> utilization in line with policy." ?
>
>  what does this "another transfer "refer to ?  which policy should we
> based on?
>
>
>  You indicated that "in case of the other /16 to return to ARIN free pool
> or  rejecting for our second /16 transfer in future." -
> if that were to occur, ARIN would indicate that you should return address
> space or pursue another 8.3/8.4 transfer.
>
>
>   furthermore, i am afraid of ARIN rejecting the 8.2 transfer , not even
> to mention the second 8.3/8.4 transfer.
> However, based on your reply,  no matter what happens, ARIN
> will definitely approve the 8.2 transfer and ARIN will only impose
> "restriction" on 8.3/8.4 transfer ?   and the utilisation rate in 8.2
> transfer is just  a paper tiger ?
>
>
>  No.  Your M&A transfer may indeed be rejected if you do not have adequate
> documentation; see my prior email regarding list of acceptable documents.
>
>  It would be best if you contact hostmas...@arin.net with any questions
> specific
> to your situation.  The PPML mailing list is for policy development
> discussions,
> not registry policy administration.
>
>  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@arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.

Reply via email to