I note and welcome the comments by Kat Hunter & John Curran regarding 
appropriate language and the use of clauses such as "grandfathered in" as per 
the text suggestion which was submitted.



For clarity, this was recognized and reflected in the "ADDITIONAL TEXT" section 
of the post below where it said "the full text of the policy...."

I reproduce this section as follows:



The full change to the policy will thus be:



Problem Statement

https://www.arin.net/participate/policy/nrpm/#9-out-of-region-use  of the NRPM, 
Out of Region Use, requires organizations to use at least a /22 in the ARIN 
region before they can justify out of region use. This harms smaller 
organizations that have less than a /22 in region but do require some out of 
region use.

Policy Statement

Modify the following text in  
https://www.arin.net/participate/policy/nrpm/#9-out-of-region-use :

FROM: 

IPv4: At least a /22 used in region.

TO:

 IPv4: At least a /24 used in region.




ADDITIONAL TEXT:

Out of Region usage justification can only be used to acquire IPv4 addresses 
from the transfer market.  

Any organization already on the Waiting List at the time this policy is 
implemented will be exempted and shall remain eligible under the rules in 
effect at the time of its placement on the Waiting List.



[Organizations on the Waiting List at the time this policy takes effect shall 
be exempted and will not be affected by this change.]


OR

Out-of-Region Usage Justification may not be used to receive IPv4 address space 
from the ARIN Waiting List (4.1.8), the Micro-allocation Pool (4.4), or the 
Dedicated IPv4 Block to Facilitate IPv6 Deployment (4.10). 

Any organization already on the Waiting List at the time this policy is 
implemented will be exempted and shall remain eligible under the rules in 
effect at the time of its placement on the Waiting List.



[Organizations on the Waiting List at the time this policy takes effect shall 
be exempted and will not be affected by this change.]




Note the text in square brackets suggests the intent of the last sentence, and 
may be considered for substitution for brevity.






Thank you to Kat Hunter and John Curran for the clarifications to the community 
regarding wording, clarity of language and intent of terminology used in 
policy.  Furthermore, I applaud their keen insight, careful eye, and vigilance 
on this issue.





Let's keep the comments and discussions going.



---- On Mon, 13 Jul 2026 14:45:54 -04:00 < mailto:[email protected] > wrote ----




Kat -  



That’s an excellent reminder - Let me jump in here and be fairly specific in 
the concerns: 



a)  Terminology: best to avoid term "grandfathering in” – it’s unnecessary 
gerontological terminology so just omit.



b)  Regarding handling existing entries on the wait list – be explicit 
regarding their handling if changing policies that affect wait list processing. 
 Entries on the list can be handled differently (out of respect for existing 
status) or may handled according
 to updated policy – just be clear about the intention either way.




Thanks!

/John



John Curran

President and CEO

American Registry for Internet Numbers






On Jul 13, 2026, at 1:42 PM, Kat Hunter < mailto:[email protected] > wrote:



I would highly recommend removing any language that refers to "grandfathering 
in". Perhaps "will be exempt until they are removed from the waitlist" but 
grandfathered in will not pass a staff and legal/community review. We have seen 
this turned
 down for a number of reasons in the past. 



Kat Hunter

Comcast/AC Chair

 







On Mon, Jul 13, 2026 at 12:54 PM Tom Fantacone via ARIN-PPML < 
mailto:[email protected] > wrote:



Correction - my last sentence should have read:



"Using the term "transfer market" as in Option 1 is bound to create ambiguity 
since the term is not defined anywhere in the NRPM."



Speaking of ambiguity...













From: Tom Fantacone via ARIN-PPML < mailto:[email protected] >

 To: "Gerry George"< mailto:[email protected] >

 Cc: "ARIN PPML"< mailto:[email protected] >

 Date: Mon, 13 Jul 2026 10:48:48 -0600

 Subject: Re: [arin-ppml] Request for Comment & Feedback: Draft Policy 
ARIN-2025-3: Change Section 9 Out Of Region Use Minimum Criteria




Gerry,



Thanks for the clarifications.  



I support the policy as written in Option 2.  It's very clear and explicit.



Using the term "transfer market" as in Option 2 is bound to create ambiguity 
since the term is not defined anywhere in the NRPM.



Regards,



Tom Fantacone







From: Gerry George via ARIN-PPML < mailto:[email protected] >

 To: "ARIN PPML"< mailto:[email protected] >

 Date: Mon, 13 Jul 2026 08:11:45 -0600

 Subject: [arin-ppml] Request for Comment & Feedback: Draft Policy ARIN-2025-3: 
Change Section 9 Out Of Region Use Minimum Criteria












_______________________________________________ 

ARIN-PPML 

You are receiving this message because you are subscribed to 

the ARIN Public Policy Mailing List ( mailto:[email protected] ). 

Unsubscribe or manage your mailing list subscription at: 

https://lists.arin.net/mailman/listinfo/arin-ppml  

Please contact mailto:[email protected]  if you experience any issues. 


Good day and greetings, ARIN community.



We had a suggestion for some modified text to the Draft Policy, primarily in 
response to feedback and reactions from ARIN 57 and PPML discussions, as many 
of the concerns related to potential gaming of the system to access the ARIN 
address pool for out-of-region
 use.  The brief background and suggested change text is as follows:





As a reminder, this proposal is to modify the following text
 in Section 9:

 

  *   FROM: IPv4: At least a /22 used in region.

  *   TO: IPv4: At least a /24 used in region.

  


The intent is to amend the proposal, including text to specifically
 exclude out of region usage as justification to get IPv4 from the waiting 
list. 

Suggested text - Option 1:

 

Out of Region usage justification can only be used to acquire IPv4 addresses 
from the
 transfer market.  Any organization on the Waiting List at the time this policy 
is implemented will be grandfathered-in.

Suggested text - Option 2:

 

Out of Region usage justification may not be used to receive IPv4 addresses 
from the ARIN Waitlist
 (4.1.8), Micro-allocation pool (4.4) or Dedicated IPv4 Allocation to 
facilitate IPv6 Deployment (4.10).  Any organization on the Waiting List at the 
time this policy is implemented will be grandfathered-in.

 

The first option is shorter, and does not specifically refer to ARIN reserve 
pools, which could change. 
 The second option does not include the term “transfer market”.  That term does 
not appear in the NRPM, and directly mentions the waiting list.

 


The full change to the policy will thus be:



Problem Statement

https://www.arin.net/participate/policy/nrpm/#9-out-of-region-use  of the NRPM, 
Out of Region Use, requires organizations to use at least a /22 in the ARIN 
region before they can justify out of region use. This harms smaller 
organizations that have less than a /22 in region but do require some out of 
region
 use.

Policy Statement

Modify the following text in  
https://www.arin.net/participate/policy/nrpm/#9-out-of-region-use :

FROM: 

IPv4: At least a /22 used in region.

TO:

 IPv4: At least a /24 used in region.




ADDITIONAL TEXT:

Out of Region usage justification can only be used to acquire IPv4 addresses 
from the transfer market.  

Any organization already on the Waiting List at the time this policy is 
implemented will be exempted and shall remain eligible under the rules in 
effect at the time of its placement on the Waiting List.

[Organizations on the Waiting List at the time this policy takes effect shall 
be exempted and will not be affected by this change.]


OR

Out-of-Region Usage Justification may not be used to receive IPv4 address space 
from the ARIN Waiting List (4.1.8), the Micro-allocation Pool (4.4), or the 
Dedicated IPv4 Block to Facilitate IPv6 Deployment (4.10). 

Any organization already on the Waiting List at the time this policy is 
implemented will be exempted and shall remain eligible under the rules in 
effect at the time of its placement on the Waiting List.

[Organizations on the Waiting List at the time this policy takes effect shall 
be exempted and will not be affected by this change.]




Note the text in square brackets suggests the intent of the last sentence, and 
may be considered for substitution for brevity.





Please submit your comments of support, dissent, encouragement or disapproval 
for the policy, and for the proposed text changes. 





Regards






Gerry E. George

ICT Consultant and Business Solutions Architect;


DigiSolv, Inc. [P.O. Box 1677, Castries, Saint Lucia] 


Email:  mailto:[email protected] 

Mobile (WhatsApp):  / Int'l Office: 

Web: mailto:[email protected]   / LinkedIn:  
https://www.linkedin.com/in/gerrygeorge/ 



Please
 consider the environment before printing this email. Thank you.





















Confidentiality: This email is intended only for the named recipient. Please 
notify the sender if you received this in error and delete it immediately.

_______________________________________________ 

ARIN-PPML 

You are receiving this message because you are subscribed to 

the ARIN Public Policy Mailing List ( mailto:[email protected] ). 

Unsubscribe or manage your mailing list subscription at: 

https://lists.arin.net/mailman/listinfo/arin-ppml  

Please contact mailto:[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 ( mailto:[email protected] ).

 Unsubscribe or manage your mailing list subscription at:

 https://lists.arin.net/mailman/listinfo/arin-ppml 

 Please contact mailto:[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 ( mailto:[email protected] ).

 Unsubscribe or manage your mailing list subscription at:

 https://lists.arin.net/mailman/listinfo/arin-ppml 

 Please contact mailto:[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 ( mailto:[email protected] ). 

Unsubscribe or manage your mailing list subscription at: 

https://lists.arin.net/mailman/listinfo/arin-ppml  

Please contact mailto:[email protected]  if you experience any issues. 










Gerry E. George

ICT Consultant and Business Solutions Architect;


DigiSolv, Inc. [P.O. Box 1677, Castries, Saint Lucia] 


Email:  mailto:[email protected] 

Mobile (WhatsApp):  / Int'l Office: 

Web: mailto:[email protected]   / LinkedIn:  
https://www.linkedin.com/in/gerrygeorge/ 



Please consider the environment before printing this email. Thank you.
Confidentiality: This email is intended only for the named recipient. Please 
notify the sender if you received this in error and delete it immediately.

_______________________________________________
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.

Reply via email to