[arin-ppml] Fwd: Advisory Council Recommendation Regarding NRPM 4.1.8. Unmet Requests

Scott Leibrand scottleibrand at gmail.com
Mon May 13 13:06:12 EDT 2019


If we did this, I suspect what would happen for the foreseeable future is
that all reclaimed space would be assigned out as /24s to everyone willing
to accept a /24 to fulfil their request. Anyone who insisted on a larger
block would get nothing, so there'd be no incentive to do so. That would
have the effect of giving a small number of space to the largest number of
organizations possible, which could be considered a feature or a bug
(increasing the number of routes that have to go into the global BGP table).

-Scott

On Mon, May 13, 2019 at 9:00 AM Jimmy Hess <mysidia at gmail.com> wrote:

> On Mon, May 13, 2019 at 9:39 AM Tom Pruitt <tpruitt at stratusnet.com> wrote:
>
>
>> If those organizations were watching the list, and moving up, it is
>> likely that they have made
>>
> business decisions based on that data with the assumption that they would
>> get an allocation
>>
> at some point.   I believe the proposed allocation limit is being
>> discussed as a method to
>>
>
> Such speculations would not have been a very prudent to rely upon.
> Anyway: there is likely
> to not ever be a full /7,  so a /7 cannot be allocated, for example.  Some
> "natural" limit exists,
> whether exactly known or not,  and there's no guarantee of anyone on the
> list ever
> eventually getting filled.
>
> Perhaps it should simply be that when ordering the wait list ---  All
> requests whether new or
> still pending each XX day period,  say over 90 days will be considered
> simultaneously
> on one date,  and in addition to being ordered by request date,  the
> requests are sorted
> into buckets based on the number of total IP addresses requested, e.g.:
>
> All requests that can be satisfied at their minimum size by a /24, /23,
> /22, /21, or less (for example)
> in the entire waiting  list, and those larger being processed today shall
> each be sorted into a
> corresponding "bucket"   with other requests that can be satisfied at that
> size.
>
> All requests from every bucket of smaller sized requests shall be
> satisfied in at least their
> minimum size  before considering requests in any buckets of larger size.
>
>
> In this manner a "larger request" like a /20 could in theory be made,  but
> even if that request was pending for  2 years:   all the  new  requests
> that can be
> satisfied by /24 or less,  then /23 or less,  then /22 or less, then /21
> or less  should
> be considered and filled first.
>
> So to have any chance of filling a massive allocation,  then that should
> mean the
> waiting list has become essentially empty.....
>
> --
> -JH
> _______________________________________________
> 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/20190513/e473c2c2/attachment-0002.html>


More information about the ARIN-PPML mailing list