<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">IMO ARIN handles this well already and no policy updates are needed. They require an in-region nexus (and in-region usage on any needs justification), but don’t subsequently care what you do with the addresses unless you come back for more. <div><br></div><div><div><div dir="ltr"><div>Scott</div></div><div dir="ltr"><br><blockquote type="cite">On Jul 14, 2025, at 11:03 AM, WOOD Alison * DAS <Alison.WOOD@das.oregon.gov> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Hello Community!!</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
The Policy Experience Report Working Group (PERWG) would like to get the community’s input on a potential issue. Currently, IPv4 space allocated via the 4.1.8 waitlist must meet in-region justification at the time of request. However, the policy isn’t entirely
clear on what happens after the initial allocation — specifically, whether additional acquired 4.1.8 space could be used outside of the ARIN service region.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
We’d like to hear your thoughts on the following question:</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Should all IPv4 space allocated from the 4.1.8 waitlist be explicitly restricted to use within the ARIN region, not just the initial allocation but on all subsequent allocations? </div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
We’re interested in whether such a restriction aligns with the original intent of 4.1.8 and how the community feels this should be handled going forward.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Looking forward to your input!</div>
<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 (ARIN-PPML@arin.net).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span>https://lists.arin.net/mailman/listinfo/arin-ppml</span><br><span>Please contact info@arin.net if you experience any issues.</span><br></div></blockquote></div></div></body></html>