<div dir="ltr">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.<div><br></div><div>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.</div><div><br></div><div>-Scott</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 27, 2023 at 6:15 PM Justin Wilson <<a href="mailto:j2sw@mtin.net">j2sw@mtin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">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. <br><br><div dir="ltr"><div>Justin </div>Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Jan 27, 2023, at 9:03 PM, Scott Leibrand <<a href="mailto:scottleibrand@gmail.com" target="_blank">scottleibrand@gmail.com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">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.<div><br></div><div>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.</div><div><br></div><div>So if the next few requests on the list are:</div><div>1. /24</div><div>2. /22</div><div>3. /23</div><div>4. /25</div><div>5. /22</div><div>6. /24</div><div>7. /25</div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>-Scott</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 27, 2023 at 1:35 PM WOOD Alison * DAS <<a href="mailto:Alison.WOOD@das.oregon.gov" target="_blank">Alison.WOOD@das.oregon.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="EN-US">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hello!<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">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.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">The current wait list criteria is:<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<ul type="disc">
<li>
Must have a /20 or less in total IPv4 holdings.<u></u><u></u></li><li>
May request up to a /22.<u></u><u></u></li><li>
Removed from list if IPv4 received via 8.3/8.4 transfer.<u></u><u></u></li><li>
Received ip space is eligible for needs-based transfer after five years.<u></u><u></u></li></ul>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p>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?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">The working group appreciates your feedback.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Thank you!<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</div></blockquote></div>
<span>_______________________________________________</span><br><span>ARIN-PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</span><br></div></blockquote></div></blockquote></div>