Hello
Surely it should be restricted and meet in-region justification and
usage, otherwise it would be yet another too loose policy for
appearances. If the resources are allocated by a given RIR it should be
for primary usage within the region.
Should anyone need to use resources in other regions, go and request or
transfer resources within that region. What is the issue with doing that ?
On 14/07/2025 15:02, WOOD Alison * DAS 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 [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.
