<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">
<blockquote type="cite"><span style="mso-fareast-language:EN-US">
In 4.4 it does say “ARIN will make a list of these blocks
publicly available.” Is that information available with the
IXP name etc? </span></blockquote>
</div>
<div class="moz-cite-prefix">I believe this is the list that ARIN is
currently publishing.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><a class="moz-txt-link-freetext" href="https://www.arin.net/reference/research/statistics/microallocations/#micro-allocations-for-exchange-points">https://www.arin.net/reference/research/statistics/microallocations/#micro-allocations-for-exchange-points</a></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I was going to say it probably would be
helpful if there was a machine readable format for this...but
looks like someone already thought of that...</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><a class="moz-txt-link-freetext" href="https://www.arin.net/participate/community/acsp/suggestions/2019/2019-24/">https://www.arin.net/participate/community/acsp/suggestions/2019/2019-24/</a></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Andrew<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 6/29/2023 8:42 AM, Kevin Blumberg
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:YQXPR01MB53996B02942853EC41AFDE27BB25A@YQXPR01MB5399.CANPRD01.PROD.OUTLOOK.COM">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I
don’t support this policy.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I’ll
echo what other operators have said, renumbering is
non-trivial at an IXP.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Is
ARIN even able to provide reverse DNS delegation for a /26
at this point?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">The
CI pool is in my mind working as intended, the drawn down
from the pool as shown earlier has been reasonable.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">If
the definition of who is an IXP for the purposes of getting
space, that is an entirely different proposal and problem
statement. In 4.4 it does say “ARIN will make a list of
these blocks publicly available.” Is that information
available with the IXP name etc? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Kevin
Blumberg</span><span style="color:#1F497D" lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span
lang="EN-US"> ARIN-PPML <a class="moz-txt-link-rfc2396E" href="mailto:arin-ppml-bounces@arin.net"><arin-ppml-bounces@arin.net></a>
<b>On Behalf Of </b>Matt Peterson<br>
<b>Sent:</b> Wednesday, June 21, 2023 4:19 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<b>Subject:</b> Re: [arin-ppml] Draft Policy ARIN-2023-2:
/26 initial IPv4 allocation for IXPs<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">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" moz-do-not-send="true">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.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">--Matt<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal">On Tue, Jun 20, 2023 at 8:54 AM ARIN
<<a href="mailto:info@arin.net"
moz-do-not-send="true" class="moz-txt-link-freetext">info@arin.net</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">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"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.arin.net/participate/policy/drafts/2023_2</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>