<!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] ARIN-2011-1: ARIN Inter-RIR Transfers - RevisedAssessment</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Thanks for the feedback John.<BR>
<BR>
Everyone else, for or against the DP...please provide your feedback and if for or against, any concrete input on ways to improve it are welcome.<BR>
<BR>
bd<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: arin-ppml-bounces@arin.net on behalf of Westerman John<BR>
Sent: Fri 11/11/2011 10:09 AM<BR>
To: ARIN<BR>
Cc: arin-ppml@arin.net<BR>
Subject: Re: [arin-ppml] ARIN-2011-1: ARIN Inter-RIR Transfers - RevisedAssessment<BR>
<BR>
All-<BR>
<BR>
I am OK with your proposal as it is written.<BR>
<BR>
Regards,<BR>
<BR>
John<BR>
<BR>
John Westerman<BR>
jdub@loudounwireless.com<BR>
<BR>
<BR>
On Nov 9, 2011, at 13:51 , ARIN wrote:<BR>
<BR>
> Below is a revised staff and legal assessment for 2011-1: ARIN Inter-RIR Transfers.<BR>
><BR>
> The draft policy text is below and available at:<BR>
> <A HREF="https://www.arin.net/policy/proposals/2011_1.html">https://www.arin.net/policy/proposals/2011_1.html</A><BR>
><BR>
> Regards,<BR>
><BR>
> Communications and Member Services<BR>
> American Registry for Internet Numbers (ARIN)<BR>
><BR>
><BR>
> ##*##<BR>
><BR>
><BR>
> ARIN STAFF ASSESSMENT 2011-1 (Revised)<BR>
><BR>
> Draft Policy: 2011-1 ARIN Inter-RIR Transfers<BR>
><BR>
> Date of Assessment: 9 Nov 2011<BR>
><BR>
> 1. Proposal Summary (Staff Understanding)<BR>
><BR>
> This revised proposal directly modifies section 8.3 "Transfers to Specified Recipients" to allow specified transfers to or from organizations in other regions, and it eliminates the single aggregate language.<BR>
><BR>
> <BR>
><BR>
> 2. Comments<BR>
><BR>
> A. ARIN Staff Comments<BR>
><BR>
> · The phrase, "compatible, needs-based policies" is not specifically defined. If adopted, staff would consider a "compatible, needs-based policy" for outward transfers as a transfer policy at another RIR that requires the recipient to have operational need for the address space, and to demonstrate that need to their RIR for transfer approval.<BR>
> <BR>
> · Allowing the transfer of number resources between RIRs will require careful coordination between RIRs in order to avoid reverse DNS zone fragmentation and synchronization problems. The ability to maintain the necessary coordination between RIRs is unproven if Inter-RIR transfers become extremely common.<BR>
> <BR>
> · This proposal doesn't have any provisions to preclude organizations that have recently obtained IPv4 resources from ARIN from immediately releasing them for profit to a specified recipient. This policy may provide incentive for organizations to game the system by obtaining resources based on justified need, when the real intent is to sell them for profit. This behavior would directly violate certain terms and conditions of the RSA, but may be difficult for staff to distinguish from bona fide changes in circumstances. <BR>
> <BR>
> · General Staff Implementation Plan:<BR>
><BR>
> For transfers from the ARIN region into another RIR region:<BR>
><BR>
> 1. ARIN receives the transfer request template from the requestor and verifies that they are the authorized registrant of the resources.<BR>
> 2. ARIN verifies that the recipient RIR has been confirmed to have a compatible needs-based transfer policy and then forwards the request to the recipient RIR.<BR>
> 3. The Recipient RIR determines if the recipient meets its relevant policies.<BR>
> 4. The Recipient RIR confirms to ARIN that the customer has met its transfer policy as a recipient, and asks ARIN to authorize the release of the resource to the recipient RIR.<BR>
> 5. ARIN coordinates with the Recipient RIR to complete the transfer.<BR>
><BR>
> For transfers into the ARIN region from another RIR region:<BR>
><BR>
> 1. ARIN receives the transfer request template from the source RIR verifying that their customer is authorized to submit the transfer.<BR>
> 2. ARIN contacts the proposed resource recipient to gather initial data needed to justify the 8.3 transfer and obtains a signed RSA from the resource recipient.<BR>
> 3. ARIN applies its relevant policy criteria to the resource recipient<BR>
> 4. When ready to approve, ARIN will contact the source RIR and have them authorize the release of the resource to ARIN.<BR>
> 5. ARIN approves the transfer, receives transfer fee payment from the recipient, and will then complete the request by coordinating with the source RIR on the final transfer of the resource into the ARIN database (and de-registration from the source database), including the DNS zone coordination.<BR>
> <BR>
> <BR>
><BR>
> B. ARIN General Counsel Comments<BR>
><BR>
> Adoption of this policy will materially assist ARIN's legal position. <BR>
><BR>
> <BR>
><BR>
> 3. Resource Impact<BR>
><BR>
> This policy would have major resource impact from an implementation aspect. It is estimated that implementation would occur within 9-12 months after ratification by the ARIN Board of Trustees. The following would be needed in order to implement:<BR>
><BR>
> - Careful coordination between the RIRs on DNS issues and updates<BR>
> - Updated guidelines<BR>
> - Staff training<BR>
><BR>
> <BR>
><BR>
> 4. Draft Policy 2011-1 Text<BR>
><BR>
> 8.3 Transfers to Specified Recipients<BR>
><BR>
> In addition to transfers under section 8.2, IPv4 number resources may be?> released to ARIN by the authorized resource holder or another RIR, in?> whole or in part, for transfer to another specified organizational?> recipient. Organizations in the ARIN region may receive transferred?> number resources under RSA if they can demonstrate the need for such?> resources in the amount which they can justify under current ARIN policies.<BR>
><BR>
> IPv4 address resources may be transferred to organizations in another?> RIR's service region if they demonstrate need to their region's RIR,?> according to that RIR's policies. Inter-regional transfers may take?> place only via RIRs who agree to the transfer and share compatible,?> needs-based policies. Such resources must be transferred in blocks of?> /24 or larger and will become part of the resource holdings of the?> recipient RIR.<BR>
><BR>
> Timetable for implementation: Upon ratification by the ARIN Board of Trustees<BR>
><BR>
> Note from the AC:<BR>
><BR>
> The Advisory Council reviewed the results of feedback from the ARIN?> XXVIII Public Policy Meeting concerning Draft Policy 2011-1 Inter-RIR?> Transfers. While there were concerns regarding the presented wording,?> there was significant continued support for a policy enabling?> Inter-Regional transfers of IPv4 number resources from organizations able?> to make them available to any organization with valid requirements.<BR>
><BR>
> In addition to cumbersome wording, the presented text could not be?> cleanly inserted into the NRPM. The following is new language that?> directly modifies section 8.3 "Transfers to Specified Recipients" to?> allow such transfers to or from organizations in other regions.<BR>
><BR>
> The first paragraph is a modified version of the current 8.3 policy?> language, envisioning resources being released to ARIN by the authorized?> resources holder or additionally by another RIR to be transferred to a?> specified recipient. The second sentence was reorganized to emphasize?> that it applies to an organization within the ARIN region that will?> receive such a specified transfer, and to eliminate the single aggregate?> language per 2011-10 which is also being sent to last call.<BR>
><BR>
> The new second paragraph adds language enabling transfers to a specified?> recipient in another RIR's service region. This language specifies that?> such recipients justify their need to their RIR, following that RIR's?> policies. ARIN will verify that there is a compatible needs based?> policy that the other RIR will use to evaluate the need of the recipient?> and that both RIR's agree to the transfer. Implicit in the intent of?> the language presented and in conformance with statements made, the size?> of the block to be transferred is identified as /24 or larger, for?> obvious practical reasons.<BR>
><BR>
> In accordance with concern for immediate adoption, the AC chose to?> forward this version to last call. Concerns expressed by some?> stakeholders for further controls were noted by the AC, and are being?> considered for future policy modification, assuaged in part by ARIN?> staff assurances that if any significant abuse of this policy were to?> occur, then the policy could easily be suspended.<BR>
><BR>
><BR>
><BR>
><BR>
> On 10/19/11 3:11 PM, ARIN wrote:<BR>
>><BR>
>> The ARIN Advisory Council (AC) met on 14 October 2011 and decided to<BR>
>> send an amended version of the following draft policy to an extended last call:<BR>
>><BR>
>> ARIN-2011-1: ARIN Inter-RIR Transfers<BR>
>><BR>
>> The AC provided the following statement:<BR>
>><BR>
>> ********<BR>
>> The Advisory Council reviewed the results of feedback from the ARIN<BR>
>> XXVIII Public Policy Meeting concerning Draft Policy 2011-1 Inter-RIR<BR>
>> Transfers. While there were concerns regarding the presented wording,<BR>
>> there was significant continued support for a policy enabling<BR>
>> Inter-Regional transfers of IPv4 number resources from organizations able to make them available to any organization with valid requirements.<BR>
>><BR>
>> In addition to cumbersome wording, the presented text could not be<BR>
>> cleanly inserted into the NRPM. The following is new language that<BR>
>> directly modifies section 8.3 "Transfers to Specified Recipients" to<BR>
>> allow such transfers to or from organizations in other regions.<BR>
>><BR>
>> The first paragraph is a modified version of the current 8.3 policy<BR>
>> language, envisioning resources being released to ARIN by the authorized<BR>
>> resources holder or additionally by another RIR to be transferred to a<BR>
>> specified recipient. The second sentence was reorganized to emphasize<BR>
>> that it applies to an organization within the ARIN region that will<BR>
>> receive such a specified transfer, and to eliminate the single aggregate<BR>
>> language per 2011-10 which is also being sent to last call.<BR>
>><BR>
>> The new second paragraph adds language enabling transfers to a specified<BR>
>> recipient in another RIR's service region. This language specifies that<BR>
>> such recipients justify their need to their RIR, following that RIR's<BR>
>> policies. ARIN will verify that there is a compatible needs based<BR>
>> policy that the other RIR will use to evaluate the need of the recipient<BR>
>> and that both RIR's agree to the transfer. Implicit in the intent of<BR>
>> the language presented and in conformance with statements made, the size<BR>
>> of the block to be transferred is identified as /24 or larger, for<BR>
>> obvious practical reasons.<BR>
>><BR>
>> In accordance with concern for immediate adoption, the AC chose to<BR>
>> forward this version to last call. Concerns expressed by some<BR>
>> stakeholders for further controls were noted by the AC, and are being<BR>
>> considered for future policy modification, assuaged in part by ARIN<BR>
>> staff assurances that if any significant abuse of this policy were to<BR>
>> occur, then the policy could easily be suspended.<BR>
>><BR>
>> The AC thanks everyone in the community for their help in crafting this<BR>
>> important policy and for your statements of support or other comments<BR>
>> during Last Call.<BR>
>> ********<BR>
>><BR>
>> Feedback is encouraged during the last call period. All comments should<BR>
>> be provided to the Public Policy Mailing List. Last call for 2011-1 will<BR>
>> expire on 16 November 2011. After last call the AC will conduct their last call review.<BR>
>><BR>
>> The draft policy text is below and available at:<BR>
>> <A HREF="https://www.arin.net/policy/proposals/">https://www.arin.net/policy/proposals/</A><BR>
>><BR>
>> The ARIN Policy Development Process is available at:<BR>
>> <A HREF="https://www.arin.net/policy/pdp.html">https://www.arin.net/policy/pdp.html</A><BR>
>><BR>
>> Regards,<BR>
>><BR>
>> Communications and Member Services<BR>
>> American Registry for Internet Numbers (ARIN)<BR>
>><BR>
>><BR>
>> ## * ##<BR>
>><BR>
>><BR>
>> Draft Policy ARIN-2011-1<BR>
>> ARIN Inter-RIR Transfers<BR>
>><BR>
>> Date/version: 14 October 2011<BR>
>><BR>
>> Policy statement:<BR>
>><BR>
>> 8.3 Transfers to Specified Recipients<BR>
>><BR>
>> In addition to transfers under section 8.2, IPv4 number resources may be<BR>
>> released to ARIN by the authorized resource holder or another RIR, in<BR>
>> whole or in part, for transfer to another specified organizational<BR>
>> recipient. Organizations in the ARIN region may receive transferred<BR>
>> number resources under RSA if they can demonstrate the need for such<BR>
>> resources in the amount which they can justify under current ARIN policies.<BR>
>><BR>
>> IPv4 address resources may be transferred to organizations in another<BR>
>> RIR's service region if they demonstrate need to their region's RIR,<BR>
>> according to that RIR's policies. Inter-regional transfers may take<BR>
>> place only via RIRs who agree to the transfer and share compatible,<BR>
>> needs-based policies. Such resources must be transferred in blocks of<BR>
>> /24 or larger and will become part of the resource holdings of the<BR>
>> recipient RIR.<BR>
>><BR>
>> Timetable for implementation: immediate<BR>
><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>
<BR>
</FONT>
</P>
</BODY>
</HTML>