<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Feb 26, 2025 at 5:01 PM William Herrin <<a href="mailto:bill@herrin.us">bill@herrin.us</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">On Wed, Feb 26, 2025 at 1:50 PM Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>> wrote:<br>
> IXP Utilization (which has nothing to do with "routing")<br>
><br>
> What exactly is the question staff utilization analysis wise? Not in the experience report and not in the policy review. In fact, there is no policy review yet.<br>
<br>
Howdy,<br></blockquote><div><br></div><div>Good afternoon, William;</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The main question here is: if the applicant requests more than a /24,<br>
how should ARIN determine whether the request is justified? The draft<br>
lays out qualification for a /24 but is mute on qualification for more<br>
than a /24.<br>
<br></blockquote><div><br></div><div>It's not mute, it doesn't set a limit. And neither does the policy:</div><div><br></div><div>The proposal says this: Assignments from this pool will be no smaller than a /24.</div><div>The policy says this: These allocations will be no smaller than a /24. Multiple allocations may be granted in certain situations.</div><div><br></div><div>The data shows ARIN has been doing just fine figuring out how to analyze use.</div><div><br></div><div>If someone meant to ask something else it should've been spelled out more clearly. Such as: everyone knows ARIN has handed out 2 x /24 for some IXP requests. If a request says I'm asking for 2 x /24 for a peering lan and will use a /24 for ops infrastructure and they have been saying yes, keep saying yes. There's no design question. And we defined IXP as CI (we have a policy). <br></div></div><div class="gmail_quote gmail_quote_container"><br></div><div class="gmail_quote gmail_quote_container">However, yes, I can see if you have a /24 for ops and only used /27 and then you need another peering lan /24 the utilization is going to be off if the ops /24 is included in the analysis. Perhaps the operational /24 is important enough resiliency wise but is a one time opportunity if asked and doesn't count towards peering fabric utilization? Still has to meet 80% AFAIK.</div><div class="gmail_quote gmail_quote_container"><br></div><div class="gmail_quote gmail_quote_container">Thanks, HTH</div><div class="gmail_quote gmail_quote_container"><br></div><div class="gmail_quote gmail_quote_container">-M<</div><div class="gmail_quote gmail_quote_container"><br></div><div class="gmail_quote gmail_quote_container"><br></div><div class="gmail_quote gmail_quote_container"><br></div></div>