[arin-ppml] Wait List Space - Feedback Requested

[Scott Leibrand]

If the requestor's use case works with sub-/24, they can request it. If
they want a /24, they can request that. I agree there are lots of use cases
for which /24 is a de facto minimum (even for MDN when you have a larger
covering aggregate you can announce). But there are some use cases for
which smaller blocks would be sufficient, and they'll likely become more
common over time as people figure out how to get filters opened for
specific use cases.

Regardless, ARIN shouldn't be in the business of telling requestors what
they need. They should be in the business of fairly assigning the space
they have to those who need it.

-Scott

On Fri, Jan 27, 2023 at 6:15 PM Justin Wilson <j2sw at mtin.net> wrote:

> The problem is everyone has their filters set to not accept smaller than
> /24s.  It sounds like a simple fix but it’s like herding cats.
>
> Justin
> Sent from my iPhone
>
> On Jan 27, 2023, at 9:03 PM, Scott Leibrand <scottleibrand at gmail.com>
> wrote:
>
> 
> IMO orgs who can get by with a smaller block should be able to request one
> (with no lower limit: if they really want a /25, they should be able to ask
> for that). But orgs who receive a block should be removed from the waiting
> list and must reapply to rejoin it, putting them at the back of the list.
>
> Organizations on the waiting list should have their requests filled only
> with a block of the size they request. ARIN should not fulfil a /22 request
> with four /24s, for example. Splitting a block should be fine, though.
>
> So if the next few requests on the list are:
> 1. /24
> 2. /22
> 3. /23
> 4. /25
> 5. /22
> 6. /24
> 7. /25
> and a /22 becomes available, requests 1, 3, 4, and 7 should be fulfilled,
> and requests 2, 5, and 6 should move to the top of the waitlist for the
> next available block.
>
> This will provide a (slight) incentive for organizations to only request
> what they "really" need, as they're likely to get it slightly sooner than
> if they have to wait for a bigger block to become available.
>
> -Scott
>
> On Fri, Jan 27, 2023 at 1:35 PM WOOD Alison * DAS <
> Alison.WOOD at das.oregon.gov> wrote:
>
>>
>>
>>
>>
>> Hello!
>>
>>
>>
>> The Policy Experience Report Working Group has been working on the Policy
>> Experience Report from ARIN 50.  I would appreciate your feedback on the
>> following issue regarding transferring waitlist space.
>>
>>
>>
>> The current wait list criteria is:
>>
>>
>>
>>    - Must have a /20 or less in total IPv4 holdings.
>>    - May request up to a /22.
>>    - Removed from list if IPv4 received via 8.3/8.4 transfer.
>>    - Received ip space is eligible for needs-based transfer after five
>>    years.
>>
>>
>>
>>
>>
>> The Policy Experience Working Group would like your feedback on a
>> potential policy idea: With waiting list times being in years, should an
>> org be eligible to get a small block (e.g. /24) via 8.3/8.4 and stay on the
>> waiting list?
>>
>>
>>
>>
>>
>> The working group appreciates your feedback.
>>
>>
>>
>> Thank you!
>>
>>
>>
>>
>> _______________________________________________
>> 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.
>>
> _______________________________________________
> 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/20230127/2756a207/attachment.htm>