<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Unfortunately that doesn’t solve any problems Michael. It would encourage “off-ARIN” transfers more heavily and still lead to sales if a bit more informal. Not only does this cause logistical problems for those with legitimate M&A transactions but would still lead to fraudsters abusing the system with shell corps. <div><br></div><div>Adding more friction to transfers is not the answer here.</div><div><br><div id="AppleMailSignature" dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">Robert Clarke<br class="">CubeMotion LLC<br class=""><a href="mailto:robert@cubemotion.com" class="">robert@cubemotion.com</a><br class="">M: <a href="tel:+1%20(844)%20244-8140" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="0/2" style="-webkit-text-decoration-color: rgba(0, 0, 0, 0.258824);">+1 (844) 244-8140</a> ex. 512<br class=""><a href="x-apple-data-detectors://0/3" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="address" x-apple-data-detectors-result="0/3" style="-webkit-text-decoration-color: rgba(0, 0, 0, 0.258824);">300 Lenora Street #454, Seattle, WA, 98121</a></span></div><div dir="ltr"><br>On Feb 26, 2019, at 9:28 PM, Michael Williams <<a href="mailto:michael.williams@glexia.com">michael.williams@glexia.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span>Easy. Eliminate transfers. If you obtain a block you use it yourself</span><br><span>or it goes back to ARIN for redistribution. Seems easy enough to me.</span><br><span>We’ve been waiting years to get any available IP address as we have an</span><br><span>immediate need. I’m actually not sure why we even allow for private</span><br><span>transfers of blocks acquired through the waiting list.</span><br><span></span><br><span>My vote is if you acquire a block from waiting list you must pay and</span><br><span>use or return to ARIN.</span><br><span></span><br><span>Sent from my iPhone</span><br><span></span><br><blockquote type="cite"><span>On 26 Feb 2019, at 20:41, John Curran <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>On 26 Feb 2019, at 5:51 PM, Ronald F. Guilmette <<a href="mailto:rfg@tristatelogic.com">rfg@tristatelogic.com</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>...</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I see rampant abuse of the Internet, day in and day out, every bit of which</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>involves number resources, said resources having been obtained, by hook or</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>by crook, and virtually all of this online evil that I see is the proverbial</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>"riddle, wrapped in a mystery, inside an enigma", apparently because the</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Good Stewards of the address space wanted it that way.  Therefore, my friends,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>please do not begrudge me for asking for a little transparency from time</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>to time, even if I know ahead of time that I'm totally unlikely to get it.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Call me old-fashioned if you like, but I'd just like to know, every once</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>and awhile, who exactly is screwing me and/or all of us.  That alone would</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>be a most refreshing change.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Ron -</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>ARIN cannot publish more specific information about fraudulent resource requests, as the detailed justifications for number resources is based on significant technical information that is subject to non-disclosure agreements with ARIN (i.e. the very same agreements that you each enter into before supplying detailed business and network information to ARIN.)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>If you wish complete transparency regarding fraudulent requests, that can be accommodated, but first requires the community to come to consensus that requests for number resource activities (issuance/transfers/updates) should be made publicly.   To my knowledge, there has been no proposal or discussion of this stance within the ARIN community.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I can provide the following information which summarizes some of the nature of the fraudulent activity that we’ve been seeing:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>- Multiple blocks received via the waiting list policy that transferred 13 months after receipt, particularly large blocks</span><br></blockquote><blockquote type="cite"><span>- Large blocks obtained by multiple organizations via similar waiting list policy requests and then all transferred via 8.2 to a single organization for monetization</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>To characterize the fraudulent activities better, consider the following:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Since the waiting list policy came into operation, 682 blocks have been issued (668 blocks of /18 and above, 14 of /16 or /17 in size)    Of those blocks issued, 25 have been subsequently transferred (19 of which were /18 and above, 6 of which /16 or /17 in size); i.e. only 3% of the smaller blocks issued have been transferred, whereas 42% of the largest block sizes issued (/16 and /17) were subsequently transferred.   The significant difference in the proportion of requests subsequently transferred should raise concern within the community, and resource review by ARIN has indeed borne evidence of significant calculated efforts to fraudulently obtain larger blocks for subsequent monetization.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The question before the community is _not_ whether you believe that significant fraud is occurring and whether the issuance per the waiting list policy should be suspended – that actually has already occurred after review & due consideration by the ARIN Board of Trustees.   The question now before the community is whether there is a some waiting list issuance policy that will fulfill the desired purpose without encouraging similar gamesmanship.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I hope this information aids in your policy development efforts,</span><br></blockquote><blockquote type="cite"><span>/John</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>John Curran</span><br></blockquote><blockquote type="cite"><span>President and CEO</span><br></blockquote><blockquote type="cite"><span>American Registry for Internet Numbers</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>ARIN-PPML</span><br></blockquote><blockquote type="cite"><span>You are receiving this message because you are subscribed to</span><br></blockquote><blockquote type="cite"><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br></blockquote><blockquote type="cite"><span>Unsubscribe or manage your mailing list subscription at:</span><br></blockquote><blockquote type="cite"><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br></blockquote><blockquote type="cite"><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></blockquote><span>_______________________________________________</span><br><span>ARIN-PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></div></blockquote></div></body></html>