I agree too .. the the policy should be written cleared so both sides can understand it.<br><br><br><div class="yahoo-signature"><a style="font-size:12px" href="https://mail.onelink.me/107872968?pid=nativeplacement&c=Global_Acquisition_YMktg_315_Internal_EmailSignature&af_sub1=Acquisition&af_sub2=Global_YMktg&af_sub3=&af_sub4=100000604&af_sub5=EmailSignature__Static_&af_ios_store_cpp=9d3a686e-218d-4849-8298-b480188dc8ac&af_android_url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.yahoo.mobile.client.android.mail%26listing%3Demail_signature">Sent from Yahoo Mail for iPhone</a><br></div><br><p class="yahoo-quoted-begin" style="font-size: 15px; padding-top: 15px; margin-top: 0">On Friday, September 18, 2026, 7:18 PM, June Slater <june@rezero.org> wrote:</p><blockquote class='iosymail'><div id="yiv4006111786"><div dir="ltr">Kaitlyn,<div><br></div><div>The lack of a specific policy is itself a policy. I understand that what is written reflects staff interpretation; however, I believe that interpretation is inaccurate. </div><div>Adding an explicit clause to the current policy to match the current interpretation materially changes the policy, restricting both the options of opinionated applicants and the room for case-by-case interpretation by ARIN staff.</div><div><br></div><div>I appreciate that community feedback to an ARIN staff question prompted this policy draft. <span style="background-color:transparent;">Absent clear evidence of what I would interpret as misuse (ex. mass exodus of space to shell corporations for use abroad), I do not believe this policy change is justified from an impact perspective. Has there been evidence of this sort of misuse?</span></div><div><span style="background-color:transparent;"><br></span></div><div>I do not believe there is a good way to word the policy while avoiding ambiguity, exploitability, and complications for legitimate users of the space. </div><div><br></div><div>I remain opposed to the policy proposal.</div><div><br></div><div>Regards,</div><div>June Slater</div><div><br></div><div><br></div></div><br><div class="yiv4006111786gmail_quote"><div dir="ltr" class="yiv4006111786gmail_attr">On Fri, Sep 18, 2026 at 1:45 PM Kaitlyn Pellak <<a rel="nofollow noopener noreferrer" ymailto="mailto:kaitlyn.pellak@gmail.com" target="_blank" href="mailto:kaitlyn.pellak@gmail.com">kaitlyn.pellak@gmail.com</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;" class="yiv4006111786gmail_quote"><div dir="ltr">June and Quantum,<br><div><br></div><div>Thank you both for providing your feedback and concerns with this policy.</div><div><br></div><div>June I believe your first question is regarding the necessity of such a change to 4.10 space. First, I would like to note that IPv4 allocations made from 4.10 have historically been interpreted by ARIN staff to be used strictly within the ARIN service region. This policy does not intend to make any material changes to how 4.10 space is currently being allocated, only to make that process explicit to the community by including it directly in the Number Resource Policy Manual.</div><div><br></div><div>Regarding the need for this change, at the ARIN55 policy meeting the COO presented his Policy Implementation and Experience Report. One of the topics covered was staff's interpretation of how 4.10 space should be used. Specifically, ARIN was looking to understand whether or not the community felt that 4.10 space should be allowed to be used outside of the ARIN service region. Several community members spoke up in agreement that 4.10 space should only be used in the ARIN service region. This policy proposal was the result of that community feedback. </div><div><br></div><div>More broadly, if the opposite path was desired (i.e. to change ARIN staff's interpretation of this policy, and make some 4.10 out of region usage acceptable) that would likely require an entirely new policy proposal. If you would like to see that change made I would strongly encourage you to submit a draft proposal, which the Advisory Council would be happy to work on with you. </div><div><br></div><div>To point two, I can appreciate that the wording seems ambiguous. Is there a better wording that you would suggest to make this policy clearer? </div><div><br></div><div>I will be noting both of these concerns during the presentation at the upcoming Public Policy meeting this October as well. If you are able, I would strongly encourage you to please voice these concerns during the meeting either at the mic or from online.</div><div><br></div><div>Thank you again for your feedback here,</div><div>Kaitlyn</div><div>ARIN Advisory Council Member</div></div><br><div class="yiv4006111786gmail_quote"><div dir="ltr" class="yiv4006111786gmail_attr">On Thu, Aug 20, 2026 at 9:44 PM Quantum via ARIN-PPML <<a rel="nofollow noopener noreferrer" ymailto="mailto:arin-ppml@arin.net" target="_blank" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;" class="yiv4006111786gmail_quote"><u></u>
<div>
<div>On 2026-08-20 16:58, June Slater wrote:<br>
</div>
<blockquote type="cite">
<pre>2. Echoing Owen's concerns, the wording seems ambiguous. The staff
interpretation seems to have deviated into the intent and not the
actual wording - facilitating deployment within the service area is
not necessarily the same as being used within the service area.
Given how ambiguous 4.10 already is (and how it necessitates judgement
calls from ARIN staff), I'm concerned at the possibility of
introducing yet more ambiguity.
Absent data showing a need, opposed in principle. Regardless, opposed
as written.</pre>
</blockquote>
<p>Hi June (and cc Owen),</p>
<p>I agree with your concerns about the current wording as well as
whether this policy is needed in the first place.</p>
<p>I want to bring your attention to Draft Policy ARIN-2025-3:
Change Section 9 Out Of Region Use Minimum Criteria, which,
despite the name, will implement this proposal and more. Thus, if
ARIN-2025-8 fails and ARIN-2025-3 passes, your opposition here is
for naught.</p>
<p>If you oppose ARIN-2025-8, then you must also oppose the current
iteration of ARIN-2025-3, as it bans out-of-region justification
for sections 4.1.8 waiting list, 4.4 micro-allocations, <i>and</i>
4.10 IPv6 transition. It's basically ARIN-2025-8 on steroids,
bundled into a seemingly unrelated policy.</p>
<p>Best regards,<br>
Quantum</p>
</div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a rel="nofollow noopener noreferrer" ymailto="mailto:ARIN-PPML@arin.net" target="_blank" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a rel="nofollow noopener noreferrer" target="_blank" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a rel="nofollow noopener noreferrer" ymailto="mailto:info@arin.net" target="_blank" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a rel="nofollow noopener noreferrer" ymailto="mailto:ARIN-PPML@arin.net" target="_blank" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a rel="nofollow noopener noreferrer" target="_blank" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a rel="nofollow noopener noreferrer" ymailto="mailto:info@arin.net" target="_blank" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<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 (ARIN-PPML@arin.net).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target=_blank>https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a ymailto="mailto:info@arin.net" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br><blockquote>