ARIN Community – 



As a co-shepherd on policy 2023-8 (Gerry George & Brian Jones), we are 
soliciting the community for feedback on this policy proposal following the 
discussions and opinions expressed at and since ARIN53. 



They have been distilled into a few main opinions (in no particular order): 

1. Policy not needed (no change). 

2. Do away with the Waitlist completely. 

3. Leave the /22 Maximum Allocation unchanged, but introduce a different method 
or formula of weighting the Waitlist requests to incorporate wait times and 
allocation size. 

4. Continue to work on it, and clarify wording. 

5. If to move forward, MUST address those currently on the Wait List and will 
they be Grandfathered in? (Fairness) 





Questions for the Community: 

a. Do we keep working on this policy? (Y/N - #1, #2) 

b. If yes, should consideration be given for some formula or weighted method 
towards allocations to queue occupants? (#3, #4) 

c. If yes, is there a need to add a clause for dealing with existing waitlist 
occupants? (#4, #5) 

And if so, how should they be handled? 




Note that if such a clause is determined for inclusion (#5), it will likely 
apply to ALL currently on the waitlist as at a specific point in time and they 
ALL would thus be subject to any such clause in the policy, once adopted. 



Thank you. 

Gerry E. George 
ICT Consultant and Business Solutions Architect; 
Digi Solv , Inc. [P.O. Box 1677, Castries, Saint Lucia] 

Mobile : (758) 728-4858 / Int'l Office : (347) 450-3444 / Skype: DigiSolv 
Email : ggeo...@digisolv.com / LinkedIn : 
https://www.linkedin.com/in/gerrygeorge/ 

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

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.

Reply via email to