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.
Scott > On Jul 14, 2025, at 11:03 AM, WOOD Alison * DAS <[email protected]> > wrote: > > > Hello Community!! > > > 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. > > We’d like to hear your thoughts on the following question: > > 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? > 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. > > Looking forward to your input! > _______________________________________________ > ARIN-PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > https://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues.
_______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
