<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Mar 21, 2016, at 2:45 PM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
My concern with this would be its potential impact on requestors who choose to be placed on the waiting list.</div>
</div>
</blockquote>
<div><br class="">
</div>
Owen - </div>
<div><br class="">
</div>
<div> Nominal to zero impact. At this point, anyone placed on the waiting list is unlikely</div>
<div> to see any resources issued (ever), given that there are several hundred in front of</div>
<div> them (and growing - see attached graph)</div>
<div>
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">I would think that requests for IPv4 addresses (other than transfers) should be relatively low volume at this</div>
<div class="">point and therefore the serialization of them shouldn’t pose that much of a burden.</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
One would think that, but we still receiving more than 100 requests per month</div>
<div> for IPv4 assignments or allocations, and these (per the countdown procedures)</div>
<div> must be processed by team review to insure maintenance of sequencing. </div>
<div> Request stats are here: <<a href="https://www.arin.net/knowledge/statistics/index.html" class="">https://www.arin.net/knowledge/statistics/index.html</a>></div>
<div><br class="">
</div>
<div> The requirement for the Registration Services team to gather and do serial processing</div>
<div> of these requests significantly increases overall staff time per request, and does not </div>
<div> appear to be particularly constructive use of resources given that (when approved), </div>
<div> they are all then going to end of a very long waiting list… We can achieve the same </div>
<div> result (and faster for everyone) if we eliminate the phase 4 team review processing.</div>
<div><br class="">
</div>
<div>
<div>
<blockquote type="cite" class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class="">If this is impacting transfer requests, they should long since have been exempted from the phase 4 processing.</div>
</div>
</blockquote>
<div><br class="">
</div>
Perhaps I was not clear - it is not the processing of transfers that is causing the</div>
<div> impact; it is the processing of IPv4 assignment and allocation requests that results</div>
<div> in a staff impact and consequently impacts processing of transfers.</div>
<div><br class="">
</div>
<div>Thanks,</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
<div class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class=""><img apple-inline="yes" id="5AA66D2F-D074-4B99-A94D-D75A95BD9464" height="480" width="610" apple-width="yes" apple-height="yes" src="cid:7BD583A4-519B-4DD4-A495-4FF9BC43B197@fios-router.home" class=""></div>
</div>
</div>
</div>
</div>
</body>
</html>