<div></div><div style="font-size:inherit" dir="auto"><span style="font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)">Remember what ARIN is and their policies, and backwards “grandfathered.” It will not ever be a retired word, will always be enforced for us legacy.</span></div><div style="font-size:inherit" dir="auto"><span style="font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"><br></span></div><div style="font-size:inherit" dir="auto"><span style="font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)">ARIN must and does manage both, it was never as simple as switching over to v6. Somehow we do need to get there, sooner than later. Decades old repetition here with no date or resolution in sight.</span></div><div style="font-size:inherit" dir="auto"><span style="font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"><br></span></div><div style="font-size:inherit" dir="auto"><span style="font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)">Do you have a successor, John? You’ve been at the helm a long time and still we are reliant on ipv4 over 6.</span><span style="font-size:inherit;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"> </span></div><div style="font-size:inherit" dir="auto"><span style="font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important;background-color:rgba(0,0,0,0);border-color:rgb(0,0,0);color:rgb(0,0,0)"> </span></div><div><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">On Thu, Sep 24, 2026 at 4:39 PM Daryll Swer via ARIN-PPML <<a href="mailto:arin-ppml@arin.net">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"><div dir="auto">> <span style="font-size:inherit;word-spacing:1px">Further, any belief that ARIN is likely to be a continuing source of IPv4 addresses is ill-advised at best. Move on to IPv6. It’s long overdue. </span></div><div dir="auto"><br></div><div dir="auto">+1</div><div dir="auto"><br></div><div dir="auto">I still see way too much effort, energy, time and money spent on: IPv4. Instead of rolling out IPv6.</div><div dir="auto"><br></div><div dir="auto">Of course we need v4, but come on: why aren't we spending as much time and effort, <b>collectively</b>, with 464xlat and MAP-T, instead?<br clear="all"><br clear="all"><div dir="auto"><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">--<br>Sent from my iPhone</div></div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 25 Sep 2026 at 7:07 AM, Owen DeLong via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">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"><div dir="auto"><div dir="ltr"></div><div dir="ltr">That opposition is specious unless the vast majority of your utilization. Is out of region. </div><div dir="ltr"><br></div><div dir="ltr">For example, let’s say you have a /21 from ARIN. You are using a /24 out of region and the other 7 /24s within the ARIN region. The 80+% utilization in region would still count towards qualifying, but the extra-regional utilization would not. </div><div dir="ltr"><br></div><div dir="ltr">I support the policy as currently written. </div><div dir="ltr"><br></div><div dir="ltr">Further, any belief that ARIN is likely to be a continuing source of IPv4 addresses is ill-advised at best. Move on to IPv6. It’s long overdue. </div><div dir="ltr"><br></div><div dir="ltr">Owen</div><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On Sep 23, 2026, at 12:15, Quantum via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<p>Hi Gerry,</p>
<div>On 2026-09-22 13:21, Gerry George
wrote:<br>
</div>
<blockquote type="cite">
<div style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:10pt">
<div style="font-family:Verdana,Arial,Helvetica,sans-serif">As one of the shepherds of this policy, let me assure you,
that the opposition which has been expressed is in no way
being ignored. In fact, this was considered during our last
AC meeting, and this is expected to be vigorously discussed
and hopefully well ventilated on PPML and more so, at the ARIN
58 members meeting when this policy is being presented.<br>
</div>
</div>
</blockquote>
<p>Thanks for considering the arguments opposing the amendments to
ARIN-2025-3 at the AC meeting. I am very curious as to what was
discussed, since the AC meeting minutes are not available on the
ARIN website. I look forward to talking about it with you at ARIN
58.</p>
<p>I would like to bring your attention to the inaccuracies in the
AC's assessment as presented in the original announcement
yesterday, which states:</p>
<p> </p>
<blockquote type="cite">
<pre style="font-family:monospace">The proposal seeks to remove some perceived usage minimums, particularly to the benefit of smaller operators operating within the ARIN service region, by reducing the required minimum space threshold to qualify for allowing use of ARIN IPv4 resource assignments outside of the ARIN region.
<b style="font-family:monospace">This recommendation has been generally supported overwhelmingly by the community, although some community members have expressed a preference to see the elimination of all out-of-region restrictions. The Advisory Council found that this view is not representative of the feedback overwhelmingly expressed by the community and that it maintains key restrictions to prevent attempts to bypass, manipulate, or exploit unintended gaps in this policy to limit potential abuse, and that the policy is suitable to be advanced to recommended status.
</b>
This policy, upon adoption, lowers the minimum IPv4 utilization threshold within the ARIN region required for organizations to qualify to deploy ARIN-assigned IPv4 resources outside the ARIN region.</pre>
</blockquote>
The bolded section of the assessment does not state the crux of the
opposition during the previous round on August 20th, which is the
addition of clause that forbade NRPM section 9 from being used with
the ARIN waiting list. In fact, during that round of discussion,
there was only opposition.
<p></p>
<p>Instead, the assessment states that the "recommendation has been
generally supported overwhelmingly by the community," with the
only opposing argument that it presented was a desire by certain
community members to eliminate all out-of-region restrictions.
While it may be true that the majority of the community disagrees
with that view (including me), that was hardly the strongest
argument anyone's had against the adoption of the policy.</p>
<p>This seems to diverge quite a bit from what happened in the AC
meeting, since you were there and confirmed that better arguments
against the policy had clearly been discussed. As a matter of
public record, and in the interest of transparency, it would be in
everyone's best interest for that assessment to be updated with
the correct arguments against the policy as discussed during the
AC meeting. This will avoid the perception that the AC meeting was
just arguing against a strawman.</p>
<p>Best regards,<br>
Quantum</p>
<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>_______________________________________________<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><span><span style="display:none"><img src="https://mailtrack.io/trace/mail/9a3dc81c5638ef758a63e41d4c5665eea79fafd3.png?u=2153471&isAddon=1" alt="9a3dc81c5638ef758a63e41d4c5665eea79fafd3"></span></span>
_______________________________________________<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>