[ARIN-consult] Fwd: [arin-announce] Consultation - Retirement of IPv4 Countdown Plan

[Scott Leibrand]

Do we have any easy-to-pull stats on what % of requests that originally come in as regular IPv4 requests and placed on the waiting list eventually get fulfilled via transfer? (If it's not easy to calculate, don't bother: I think the arguments in favor of ending team review are strong enough without knowing). 

-Scott




On Mon, Mar 21, 2016 at 12:05 PM -0700, "John Curran" <jcurran at arin.net> wrote:















On Mar 21, 2016, at 2:45 PM, Owen DeLong <owen at delong.com> wrote:






My concern with this would be its potential impact on requestors who choose to be placed on the waiting list.





Owen - 



   Nominal to zero impact.    At this point, anyone placed on the waiting list is unlikely
   to see any resources issued (ever), given that there are several hundred in front of
   them (and growing - see attached graph)











I would think that requests for IPv4 addresses (other than transfers) should be relatively low volume at this
point and therefore the serialization of them shouldn’t pose that much of a burden.






  One would think that, but we still receiving more than 100 requests per month
  for IPv4 assignments or allocations, and these (per the countdown procedures)
  must be processed by team review to insure maintenance of sequencing.  
  Request stats are here: <https://www.arin.net/knowledge/statistics/index.html>



  The requirement for the Registration Services team to gather and do serial processing
  of these requests significantly increases overall staff time per request, and does not 
  appear to be particularly constructive use of resources given that (when approved), 
  they are all then going to end of a very long waiting list…  We can achieve the same 
  result (and faster for everyone) if we eliminate the phase 4 team review processing.







If this is impacting transfer requests, they should long since have been exempted from the phase 4 processing.





  Perhaps I was not clear - it is not the processing of transfers that is causing the
  impact; it is the processing of IPv4 assignment and allocation requests that results
  in a staff impact and consequently impacts processing of transfers.



Thanks,
/John



John Curran
President and CEO
ARIN






















-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20160321/b9788f4f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-03-21 at 3.03.23 PM.png
Type: image/png
Size: 140306 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20160321/b9788f4f/attachment.png>