[arin-ppml] Looking for final show of support on revised Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

Fernando Frediani fhfrediani at gmail.com
Thu Jun 6 21:54:49 EDT 2019


What an absurd idea !

That's not ideal propose and although ARIN can and should not ignor
transfer market and it is the RIR function to handle the waiting list and
have it in its full control.
It is one of its main proposes to handle this waiting list and I personaly
support this fully.

Regards
Fernando


On Thu, 6 Jun 2019, 22:22 William Herrin, <bill at herrin.us> wrote:

> Support, though frankly I'd prefer it if ARIN simply abolished the wait
> list and put the addresses on the transfer market.
>
> Philosophically speaking, how could you possibly *need* addresses the way
> we think of need if you can afford to wait months and months for them to
> become available on the wait list? Seems to me like there's some fudging
> going on at this point.
>
> Regards,
> Bill Herrin
>
> > Replace section 4.1.8 et. seq. as follows, then reinstate the full
> operation of sections 4.1.8, 4.1.8.1 and 4.1.8.2 immediately.
> >
> > 4.1.8 ARIN Waitlist
> >
> > ARIN will only issue future IPv4 assignments/allocations (excluding 4.4
> and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an
> organization may qualify for at any one time is a /22. Organizations will
> be able to elect a smaller block size than they qualify for down to a /24.
> Only organizations holding a /20 or less of IPv4 address space may apply
> and be approved. Address space distributed from the waitlist will not be
> eligible for transfer for a period of 60 months. This policy will be
> applied to all future distributions from the waitlist to include those
> currently listed.
> >
> > Repeated requests, in a manner that would circumvent 4.1.6, are not
> allowed: an organization currently on the waitlist must wait 90 days after
> receiving a distribution from the waitlist before applying for additional
> space. ARIN, at its sole discretion, may waive this requirement if the
> requester can document a change in circumstances since their last request
> that could not have been reasonably foreseen at the time of the original
> request, and which now justifies additional space. Qualified requesters
> whose request will also be advised of the availability of the transfer
> mechanism in section 8.3 as an alternative mechanism to obtain IPv4
> addresses.
> >
> > 4.1.8.1 Sequencing
> >
> > The position of each qualified request on the waiting list will be
> determined by the date it was approved. Each organization may have one
> approved request on the waiting list at a time.
> >
> > 4.1.8.2 Fulfillment
> >
> > ARIN will fulfill requests on a first-approved basis, subject to the
> size of each available address block as address blocks become available for
> distribution. A timely review of the original request may be conducted by
> ARIN staff. Requests will not be partially filled. Any requests met through
> a transfer will be considered fulfilled and removed from the waiting list
>
> --
> William Herrin
> bill at herrin.us
> https://bill.herrin.us/
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190606/438ba826/attachment.htm>


More information about the ARIN-PPML mailing list