<div><div><div dir="auto">Actually, I expect the genesis of this proposal was the very similar proposal in the RIPE community RIPE-2023-02 <span style="font-family:"Open Sans",Helvetica,Arial,sans-serif">Reducing IXP IPv4 assignment default size to a /26. That proposal followed a presentation at RIPE 86 last fall and a discussion on their </span>address-policy-wg mailing late last year. The conversation started with a reduction to /29, and a reasonable compromise of /26 that was written in to a formal proposal earlier this year. That proposal is progressing through their process and just finished their Discussion Phase last week, and has entered their Review Phase, and at least seems to be heading towards being policy in the RIPE community.</div></div><div dir="auto"><br></div><div dir="auto">While I do not support this proposal, especially as written, it is nevertheless an important and timely conversation for the ARIN community to have and I for one appreciate it being brought forward to our community as a proposal. </div></div><div dir="auto"><br></div><div dir="auto">Thanks.</div><div><div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 21, 2023 at 03:19 Matt Peterson <<a href="mailto:matt@peterson.org" target="_blank">matt@peterson.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr"><div dir="ltr">It's clear this proposal did not receive feedback from those of us who operate IXP's <i>(or those who lived through the <a href="http://ep.net" target="_blank">ep.net</a> era).</i> Renumbering events are often multi-year efforts for an IXP, this "savings" is not worth the operational overhead. I'm not in support of this proposal. This is a solution looking for a problem, we have both the appropriate pool size and a method to refill.<div><br></div><div>If anything, the 4.4 requirement language around <i>"other participants (minimum of three total)" </i>could use some attention. ARIN's service region has many "shadow IXP's", which may have 3 unique ASN's <i>(say a route server, route collector, and management network) </i>- but are all operated by the same organization. That does not seem like a legitimate definition of an exchange point, especially when that operator is the only participant over several years.</div><div><br></div><div>--Matt</div><div><div><br></div></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 20, 2023 at 8:54 AM ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">On 15 June 2023, the ARIN Advisory Council (AC) accepted “ARIN-prop-320: /26 initial IPv4 allocation for IXPs” as a Draft Policy.<br>
<br>
Draft Policy ARIN-2023-2 is below and can be found at:<br>
<br>
<a href="https://www.arin.net/participate/policy/drafts/2023_2" rel="noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2023_2</a><br>
</blockquote></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>
</blockquote></div></div>
</div>
</div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div>