<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [arin-ppml] Questions about updated ARIN policy proposal 2011-1</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Paul,<BR>
<BR>
2011-1 as is, was written a while back to incorporate all the issues that were raised in order to given them a full hearing in the upcoming meeting.<BR>
Seemed that the proposal as written before was at an impasse and this seemed to be the best way forward.<BR>
Given changes in policy in the APNIC regions, I believe that a compromise that reduces this language to its most simple and compatible form can be achieved...which will gain consensus in the ARIN region. I will be pushing mightily for such.<BR>
<BR>
Thank you for bringing your comments back before the meeting so that these can be incorporated. I encourage you to be as explicit as possible about what language you believe would meet that test of simple and compatible.<BR>
<BR>
Best,<BR>
<BR>
bd<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: arin-ppml-bounces@arin.net on behalf of Paul Wilson<BR>
Sent: Thu 9/29/2011 7:53 AM<BR>
To: ARIN PPML (ppml@arin.net)<BR>
Subject: [arin-ppml] Questions about updated ARIN policy proposal 2011-1<BR>
<BR>
I notice an updated version of APNIC proposal 2011-1 here:<BR>
<BR>
<A HREF="https://www.arin.net/policy/proposals/2011_1.html">https://www.arin.net/policy/proposals/2011_1.html</A><BR>
<BR>
My reading of this proposal is that it now incorporates the main aspects of the proposal ARIN-prop-156 which was recently abandoned by the ARIN AC. Specifically, the 2011-1 now requires both source and recipient to comply with the policies of both of the RIRs involved, apparently requiring ARIN to apply its policies to organisations outside of the ARIN region. I note also the enshrining of a 3-month demonstrated need policy, which happens to be part of today's ARIN policy anyway, on recipients outside of the ARIN region.<BR>
<BR>
If this interpretation is correct, I'd like to repeat the practical questions which I previously asked about ARIN-prop-156, as these are now relevant to this one as well: <BR>
<BR>
> Is it proposed that ARIN staff would conduct a full need-based assessment of the each recipient, even in another region, including examination of all prior allocations? <BR>
><BR>
> Has there been any consideration of the cost and practicality of this approach? <BR>
><BR>
> Is it possible that a recipient [in another region] would be asked to pay ARIN to cover the cost of this service? <BR>
><BR>
> Would a registration services agreement be required with ARIN?<BR>
<BR>
Thanks,<BR>
<BR>
Paul Wilson<BR>
APNIC.<BR>
<BR>
===<BR>
<BR>
Draft Policy ARIN-2011-1<BR>
ARIN Inter-RIR Transfers<BR>
<BR>
Date: 22 September 2011<BR>
<BR>
Policy statement:<BR>
Address resources may be transferred in or out of the ARIN region to those who demonstrate need and plan to deploy them for a networking purpose within 3 months. Such transfers will take place between RIRs who share compatible, needs-based policies supporting entities agreeing to the transfer and which otherwise meet both RIR's policies. Transferred resources will become part of the resource holdings of the recipient RIR unless otherwise agreed by both RIRs.<BR>
Rationale: Since individual RIRs now allow transfers, it makes sense to be able to transfer between regions as well. Reasoning....It is explicit about...<BR>
<BR>
in or out of region,<BR>
that transfers are between RIRs that support needs-based policies,<BR>
that RIRs have to agree,<BR>
that parties meet all of both RIR policies<BR>
that it is needs based, and the need is for a networking purpose,<BR>
that the receiving RIR is entitled to the addresses<BR>
I think all these details were raised as objections at one time or another...so it seems best to waste a few more words to be explicit.<BR>
It is not explicit about...<BR>
block sizes<BR>
utilization of prior allocations,<BR>
assignments or transfers<BR>
RFC 2050<BR>
subsequent transfers<BR>
Timetable for implementation: Upon ratification by the ARIN Board of Trustees<BR>
<BR>
<BR>
<BR>
<BR>
________________________________________________________________________<BR>
Paul Wilson, Director-General, APNIC <dg@apnic.net><BR>
<A HREF="http://www.apnic.net">http://www.apnic.net</A> +61 7 3858 3100<BR>
<BR>
_______________________________________________<BR>
PPML<BR>
You are receiving this message because you are subscribed to<BR>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<BR>
Unsubscribe or manage your mailing list subscription at:<BR>
<A HREF="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</A><BR>
Please contact info@arin.net if you experience any issues.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>