<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
The policy properly differentiates between allocations for IXPs
which do NOT need global reachability and allocations which do -
however it places a too-onerous restriction on the initial
allocation:<br>
<br>
<blockquote type="cite">
<p style="box-sizing: border-box; margin-top: 0px; margin-bottom:
1rem; overflow-wrap: break-word; line-height: 1.5; caret-color:
rgb(51, 51, 51); color: rgb(51, 51, 51); font-family: system-ui,
-apple-system, "Segoe UI", Roboto, "Helvetica
Neue", Arial, "Noto Sans", "Liberation
Sans", sans-serif, "Apple Color Emoji",
"Segoe UI Emoji", "Segoe UI Symbol",
"Noto Color Emoji"; font-size: 16px; font-style:
normal; font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;">4.4.1 Micro-allocations for Internet
Exchange Points (IXPs)</p>
<p style="box-sizing: border-box; margin-top: 0px; margin-bottom:
1rem; overflow-wrap: break-word; line-height: 1.5; caret-color:
rgb(51, 51, 51); color: rgb(51, 51, 51); font-family: system-ui,
-apple-system, "Segoe UI", Roboto, "Helvetica
Neue", Arial, "Noto Sans", "Liberation
Sans", sans-serif, "Apple Color Emoji",
"Segoe UI Emoji", "Segoe UI Symbol",
"Noto Color Emoji"; font-size: 16px; font-style:
normal; font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;">An IXP requesting an initial IPv4
allocation from this reserved space will be assigned a /26 by
default. An IXP requesting an allocation larger than a /26 must
show an immediate need to utilize more than 25% of the requested
allocation size upon initial commissioning.</p>
<br class="Apple-interchange-newline">
</blockquote>
<br>
I wonder how much automation software will break when you take away
the assumption that the first three quads of a dotted-quad will be
unique per-IXP? (I am not suggesting this is good practice, I am
suggesting that good practice is not a good assumption).<br>
<br>
But more importantly, I wonder what the percentage of Existing,
Functional and wildly successful IXPs have actually reached 128
participants yet? <br>
<br>
This policy would force EVERY successful IXP to have a renumbering
event on their horizon. And if you think that that won't matter
because "we're at peak IXP anyway" then the policy is pointless
anyway.<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 2023-06-20 10:05 a.m., Matthew
Wilder via ARIN-PPML wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGbMP+gg54L8V1fEEsUWWtqfOZTgGUaBFFZFuKVa10rDfsm1hw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Owen,
<div><br>
</div>
<div>It sounds as though your opposition to this draft policy
includes a concern that it is not technically sound.</div>
<div><br>
</div>
<div>In what ways do you believe that this change would break
the Internet or contort it? </div>
<div><br>
</div>
<div>Thanks,</div>
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">Matthew</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jun 20, 2023 at
9:45 AM Owen DeLong via ARIN-PPML <<a
href="mailto:arin-ppml@arin.net" moz-do-not-send="true"
class="moz-txt-link-freetext">arin-ppml@arin.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">We’re
12 years past IANA runout and only 50% of this reservation has
been depleted.<br>
<br>
Seems to me that things are working as intended.<br>
<br>
There is no plan or expectation that n IPv4 free pool will
last indefinitely into the future, nor should we be making
attempts to do so on any level.<br>
<br>
I oppose this proposal and suggest that those that think that
parceling out IPv4 in ever smaller chunks and breaking more
and more of the internet contorting it to adapt to the whims
of those who have failed to implement IPv6 should find a way
to encourage those failing to deploy IPv6 to get off the dime
already.<br>
<br>
Owen<br>
<br>
<br>
> On Jun 20, 2023, at 08:54, ARIN <<a
href="mailto:info@arin.net" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">info@arin.net</a>>
wrote:<br>
> <br>
> 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" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.arin.net/participate/policy/drafts/2023_2</a><br>
> <br>
> You are encouraged to discuss all Draft Policies on PPML.
The AC will evaluate the discussion to assess the conformance
of this draft policy with ARIN's Principles of Internet number
resource policy as stated in the Policy Development Process
(PDP). Specifically, these principles are:<br>
> <br>
> * Enabling Fair and Impartial Number Resource
Administration<br>
> * Technically Sound<br>
> * Supported by the Community<br>
> <br>
> The PDP can be found at:<br>
> <br>
> <a href="https://www.arin.net/participate/policy/pdp/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.arin.net/participate/policy/pdp/</a><br>
> <br>
> Draft Policies and Proposals under discussion can be
found at: <a
href="https://www.arin.net/participate/policy/drafts/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.arin.net/participate/policy/drafts/</a><br>
> <br>
> Regards,<br>
> <br>
> Eddie Diego<br>
> Policy Analyst<br>
> American Registry for Internet Numbers (ARIN)<br>
> <br>
> <br>
> Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for
IXPs<br>
> <br>
> Problem Statement: <br>
> <br>
> Per NRPM Section 4.4, ARIN has reserved a /15 for
micro-allocations for critical internet infrastructure, such
as internet exchange points (IXPs) and core DNS service
providers. The majority of these allocation requests are made
by IXPs. As of the last ARIN report, roughly half of this
reservation is allocated (see Statistics & Reporting
Projections from ARIN staff suggest that at current allocation
rates, the remaining reserved space may be exhausted in the
next few years.<br>
> <br>
> In parallel, an analysis of PeeringDB data conducted by
the RIPE Address Policy Working Group shows that approximately
70% of global IXPs have fewer than 32 members registered with
that site. An IXP this size could readily operate with a /26
allocation, which would provide 100% overprovisioning beyond
their existing peer count. (Source: <a
href="https://github.com/mwichtlh/address-policy-wg"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/mwichtlh/address-policy-wg</a>
)<br>
> <br>
> Unlike other types of allocations, IXP peering networks
are not required by member networks to be globally reachable;
only members of the IXP must be able to reach the prefix. As
such, there is no technical requirement that an IXP allocation
must be no smaller than a /24.<br>
> <br>
> Policy statement:<br>
> <br>
> Existing text:<br>
> <br>
> 4.4. Micro-allocation<br>
> <br>
> ARIN will make IPv4 micro-allocations to critical
infrastructure providers of the Internet, including public
exchange points, core DNS service providers (e.g.
ICANN-sanctioned root and ccTLD operators) as well as the RIRs
and IANA. These allocations will be no smaller than a /24.
Multiple allocations may be granted in certain situations.<br>
> <br>
> Replace with:<br>
> <br>
> 4.4 Micro-allocation<br>
> <br>
> ARIN will make IPv4 micro-allocations to critical
infrastructure providers of the Internet, including public
internet exchange points (IXPs), core DNS service providers
(e.g. ICANN-sanctioned root and ccTLD operators) as well as
the RIRs and IANA. These allocations will be no smaller than a
/26 for IXPs, or a /24 for other allocations that require
global reachability of the assigned allocation. Multiple
allocations may be granted in certain situations.<br>
> <br>
> 4.4.1 Micro-allocations for Internet Exchange Points
(IXPs)<br>
> <br>
> An IXP requesting an initial IPv4 allocation from this
reserved space will be assigned a /26 by default. An IXP
requesting an allocation larger than a /26 must show an
immediate need to utilize more than 25% of the requested
allocation size upon initial commissioning.<br>
> <br>
> An IXP requesting an allocation under this section must
have also requested, or already received, an IPv6 allocation
for the same purpose under Section 6.10.1.<br>
> <br>
> An allocation made to an IXP under this section may only
be used for the operation of its public peering LAN. No other
uses are allowed.<br>
> <br>
> An IXP that has received an IPv4 allocation under this
section may request a larger allocation once they have
utilized more than 50% of their existing one. Upon receiving
the larger allocation, the IXP must migrate to the new
allocation and return their previous one to ARIN within 6
months.<br>
> <br>
> Comments:<br>
> <br>
> This proposal mirrors RIPE policy proposal 2023-01 (see <a
href="https://www.ripe.net/participate/policies/proposals/2023-01"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.ripe.net/participate/policies/proposals/2023-01</a>)
which is currently under consideration in that region and
appears to have sufficient community support for adoption at
the time of this writing.<br>
> <br>
> Timetable for implementation: Immediate<br>
> <br>
> <br>
> _______________________________________________<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"
moz-do-not-send="true" class="moz-txt-link-freetext">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" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">info@arin.net</a> if you
experience any issues.<br>
<br>
_______________________________________________<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"
moz-do-not-send="true" class="moz-txt-link-freetext">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" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">info@arin.net</a>
if you experience any issues.<br>
</blockquote>
</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>
<br>
<pre class="moz-signature" cols="72">--
Ron Grant
Balan Software/Networks
Network Architecture & Programming
604-737-2113
ca.linkedin.com/in/obiron</pre>
</body>
</html>