<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Rent and profit seeking?</div><div>That horse has long left the barn. But it's telling that arguments against this policy reveal themselves to be ideological in nature.</div><div><br></div><div>Speculation? Only existing in fevered imaginations. Absent in RIPE despite its "encouragement/enablement". Still waiting for evidence of speculation, care to share any?</div><div><br></div><div>I support this overdue relaxing of outdated inhibitors to normal business practices and to accurate registration.</div><div><br></div><div><br></div><div>Mike </div><div><br></div><div><br></div><div><br></div><div><div style="font-size:10px;color:#575757">Sent from my Sprint phone</div></div><br><br><div>-------- Original message --------</div><div>From: Dani Roisman <droisman@softlayer.com> </div><div>Date:02/18/2016 3:03 PM (GMT-05:00) </div><div>To: arin-ppml@arin.net </div><div>Subject: Re: [arin-ppml] ARIN-PPML Digest, Vol 128, Issue 7 </div><div><br></div>I support this re-write of the previous draft, and agree with the removal of the 8.4 language at this stage (8.4 transfers should get separate attention due to the tie-in with other RIRs). When I defended this proposal in Montreal, I had may people come up to me after the session had ended who expressed their support.<br><br>I would ask that those of you who *do* think the time has come to shift ARIN focus away from an inhibiting role, and instead prioritize accurate documentation of IPv4 market-induced transfers, please speak up now. The ARIN AC and membership needs to hear views of not only those opposed to this proposal.<br><br>----<br>Dani Roisman<br><br><br>| -----Original Message-----<br>| Date: Wed, 17 Feb 2016 00:12:54 +0000<br>| From: Leif Sawyer <lsawyer@gci.com><br>| To: ARIN PPML <arin-ppml@arin.net><br>| Subject: [arin-ppml] Draft Policy ARIN-2015-9: Eliminating needs-based<br>| evaluation for Section 8.2 and 8.3 transfers of IPv4 netblocks<br>| Message-ID:<br>| <EDF941B230F4C446826CF893A9C8CE59E0DBF413@ex-mbx-<br>| prd02.gci.com><br>| Content-Type: text/plain; charset=WINDOWS-1252<br>| <br>| Good afternoon -<br>| <br>| Based on feedback from Montreal as well as internal discussions, I've<br>| reworked this policy.<br>| AC members and ARIN staff are looking for additional feedback, as well as<br>| your position in terms<br>| of supporting or opposing this draft policy.<br>| <br>| We'll be discussing this policy, as well as any feedback provided on this<br>| week's AC teleconference,<br>| so I'm very appreciative of your input.<br>| <br>| Thanks,<br>| <br>| Leif Sawyer<br>| Shepherd - ARIN-2015-9<br>| <br>| NRPM section 8: https://www.arin.net/policy/nrpm.html#eight<br>| <br>| Most current draft policy text follows:<br>| --<br>| <br>| Draft Policy ARIN-2015-9<br>| Eliminating needs-based evaluation for Section 8.2 and 8.3 transfers of IPv4<br>| netblocks<br>| Original Date: 23 September 2015<br>| Updated: 16 February, 2016<br>| <br>| Problem statement:<br>| The current needs-based evaluation language in NRPM sections 8.2 and 8.3,<br>| regarding transfer of IPv4<br>| netblocks from one organization to another, may cause a recipient<br>| organization to bypass the ARIN<br>| registry entirely in order to secure the needed IPv4 netblocks in a more<br>| timely fashion directly from the<br>| current holder. The result is that the data visible in ARIN registry may become<br>| more inaccurate over<br>| time.<br>| <br>| Policy statement:<br>| This proposal eliminates all needs-based evaluation language for sections 8.2<br>| and 8.3, allowing<br>| transfers to be reflected in the database as they occur following an<br>| agreement of transfer from the<br>| resource provider to the recipient.<br>| <br>| Section 8.1 Principles:<br>| - Strike the fragment from the 3rd paragraph which reads<br>| ", based on justified need, "<br>| so the resulting text reads<br>| "Number resources are issued to organizations, not to individuals<br>| representing those organizations."<br>| Section 8.2 Mergers and Acquisitions:<br>| - Change the 4th bullet from:<br>| "The resources to be transferred will be subject to ARIN policies."<br>| to:<br>| "The resources to be transferred will be subject to ARIN policies, excluding<br>| any policies related to needs-based justification."<br>| <br>| - Strike the final paragraph which begins "In the event that number resources<br>| of the combined organizations are no longer justified under ARIN policy ..."<br>| <br>| Section 8.3 Transfers between Specified Recipients within the ARIN Region:<br>| - Change the first bullet under "Conditions on recipient of the transfer" from:<br>| "The recipient must demonstrate the need for up to a 24-month supply of IP<br>| address resources under current ARIN policies and sign an RSA."<br>| to:<br>| "The recipient must sign an RSA."<br>| <br>| - Change the 2nd bullet under "Conditions on recipient of the transfer" from:<br>| "The resources to be transferred will be subject to ARIN policies."<br>| to:<br>| "The resources to be transferred will be subject to ARIN policies, excluding<br>| any policies related to needs-based justification."<br>| <br>| Comments:<br>| a. Timetable for implementation: Immediate<br>| b. Anything else<br>| As the "free pool" for 4 of the 5 world's RIR's (APNIC, RIPE, LACNIC, and<br>| ARIN) have now been<br>| exhausted, networks in need of additional IPv4 addresses have shifted away<br>| from the practice of<br>| receiving them from the RIR's resource pool. Instead, networks in need are<br>| seeking out current holders<br>| of IPv4 resources who are willing to transfer them in order to fulfill that need.<br>| Accordingly, the RIR's<br>| primary responsibility vis-?-vis IPv4 netblock governance has shifted from<br>| "allocation" to ensuring an<br>| accurate registry database.<br>| <br>| The RIPE registry can be used as a reference of one which has evolved over<br>| the past couple years to<br>| shift their focus away from conservation/allocation and towards database<br>| accuracy. IPv4 netblock<br>| transfers within that RIR consist merely of validating authenticity of the<br>| parties requesting a transfer.<br>| Provided the organizations meet the basic requirement of RIR membership,<br>| and that the transferring<br>| organization has the valid authority to request the transfer, the transaction<br>| completes without any<br>| "needs-based" review.<br>| <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>http://lists.arin.net/mailman/listinfo/arin-ppml<br>Please contact info@arin.net if you experience any issues.<br><br></body>