<div><br></div><div dir="auto">Gerry - amazing detail and focus. Thank you! Will comsider.</div><div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Jun 26, 2025 at 15:48 Gerry E.. George <<a href="mailto:ggeorge@digisolv.com">ggeorge@digisolv.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"><div style="font-family:arial,helvetica,sans-serif"><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;white-space:normal;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><div style="font-family:arial,helvetica,sans-serif">Draft Policy ARIN-2023-8 - Reduce 4.1.8 Maximum Allocation</div></div><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;white-space:normal;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif">June 25, 2025</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif">PREAMBLE:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">This draft policy was accepted as a proposal on October 26, 2023 and became a Draft Policy on November 21, 2023.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">It has been revised on 2 previous occasions – February 14, 2024 to correct some typos and to make adjustments to the text/wording, and in September 30, 2024  to make allowance for “grandfathering clause”</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">The last revision – May 2025 was to synchronize the text of the draft policy to be in line with changes to the NRPM (2025.1)</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">The draft policy has also been presented at ARIN 53 (Barbados), 54 (Toronto, Ontario) and 55 (Charlotte, VA).</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">As the lead shepherd assigned with the responsibility for this draft policy, I are attempting determine a definitive direction or preference by the community, in order to move forward.  I have taken the liberty to summarize the various positions, opinions and discussions in this comprehensive (and long) post, in order to have all of the relevant information in one place to help with distilling the various viewpoints and the available options.  I hope this will help distill the associated issues and evoke some guidance from the community.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Proposed Draft Policy (May 2025)</strong>:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">ARIN-2023-8: Reduce 4.1.8 maximum allocation</strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif"><em style="font-family:arial,helvetica,sans-serif">Problem Statement:</em></strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">4.1.8 waiting times are too long, making justifications untimely by the time a request is met. New entrants to the waiting list are expected to wait three years for their need to be met under current policy, with a waiting list of around 700 at this point. Data indicates that reducing the current /22 maximum further to a /24 would significantly reduce this waiting period, and further tightening the requirements by replacing the /20 recipient maximum holdings with a /24, and preventing multiple visits to the waiting list queue.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif"><em style="font-family:arial,helvetica,sans-serif">Policy Statement:</em></strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif"><em style="font-family:arial,helvetica,sans-serif"><br></em></strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">PROPOSED UPDATED TEXT (4.1.8 maximum allocation</strong>)<strong style="font-family:arial,helvetica,sans-serif">:</strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif"><em style="font-family:arial,helvetica,sans-serif">4.1.8. ARIN Waitlist</em></strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">ARIN will only issue future IPv4 assignments/allocations (excluding 4.4 and 4.10 space) from the ARIN Waitlist. The maximum size aggregate that an organization may qualify for is a /24.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Organizations that have ever held any IPv4 space other than special use space received under section 4.4 or 4.10 are not eligible to apply.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Address space distributed from the waitlist will not be eligible for transfer, with the exception of Section 8.2 transfers, for a period of 60 months. This <strong style="font-family:arial,helvetica,sans-serif"><em style="font-family:arial,helvetica,sans-serif">restriction</em></strong> will be applied to all distributions from the waitlist to <strong style="font-family:arial,helvetica,sans-serif"><em style="font-family:arial,helvetica,sans-serif">also</em></strong> include those <strong style="font-family:arial,helvetica,sans-serif"><em style="font-family:arial,helvetica,sans-serif">organizations or requesters</em></strong> currently listed.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Qualified requesters will also be advised of the availability of the transfer mechanism in section 8.3 as an alternative mechanism to obtain IPv4 addresses.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Waiting list recipients must demonstrate the need for a /24 on an operating network.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">The limitation to a single /24 will be enforced for waitlist requests submitted after this policy takes effect, and will only apply to new entrants to the waitlist. Requests received before the policy change will be evaluated based on the policy in place at the time of the request.</strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> Note: Sections 4.1.8.1 Sequencing, 4.1.8.2 Fulfillment and 4.1.8.3 Qualification remain unchanged.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif">[End of Policy]</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">CHANGES</strong>:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">In section 4.2.2 replace the sentence:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">FROM:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">“All ISP organizations without any IPv4 addresses from ARIN automatically qualify for an initial allocation of a /24. ISPs providing a 24-month utilization plan for the request size specified may receive up to a /22. ISPs holding reallocations and/or reassignments must show the efficient utilization of their resources consistent with the requirements in sections 4.2.3 and 4.2.4.”</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif">TO:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">“All ISP organizations without any IPv4 addresses from ARIN automatically qualify for an initial allocation of a /24. ”</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Note: This change is to bring the text of the draft policy in line with changes in the NRPM (2025.1) based on changes adopted</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">In section 8.3</strong> Conditions on the source of the transfer, remove this sentence:<br> “The source entity will not be allowed to apply for IPv4 address space under Section 4.1.8 ARIN Waitlist for a period of 36 months following the transfer of IPv4 address resources to another party.”</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">DISCUSSION:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Following is a summary of the key discussion points and various positions and opinions expressed regarding the draft policy as expressed on PPML threads, at the ARIN Members Meetings and in various discussions and engagements.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Main Objective</strong>: Reduce wait times (~3 years currently) by capping allocations at a <strong style="font-family:arial,helvetica,sans-serif">/24</strong> rather than currently allowing larger blocks (/23 & /22), preventing multiple queue entries, and excluding organizations that previously held non-special IPv4 space.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Suggested Revisions</strong></p><ul style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Feb 2024</strong>:</li><ul style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif">Clarification requiring waitlist applicants to demonstrate a /24 need on an active network</li><li style="font-family:arial,helvetica,sans-serif">Removed several transfer and requeue restrictions to streamline policy</li></ul></ul><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Community Opinions & Feedback</strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif"><br></strong></p><ul style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Mixed community sentiment, </strong> </li><ol style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">No change needed</strong></li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Eliminate the waitlist entirely</strong></li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Keep /22 but weight requests by need/time</strong></li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Proceed with revisions and clarify wording</strong></li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Define treatment for existing wait‑listers</strong></li></ol><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Alternate suggestion</strong>: let applicants specify a desired and minimum acceptable block size, enabling a flexible allocation process</li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Weighted queues</strong>: Prioritize requests by actual need or length of time waiting.</li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Time-based revalidation</strong>: Automatically clear old entries if need is no longer valid.</li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Anti-reduction</strong> There's no spare IPv4 space—shrinking allocations to /24 would harm newcomers without improving fairness; recommends abandoning.</li><li style="font-family:arial,helvetica,sans-serif">IPv4 pool is long exhausted, and this is simply postponing the inevitable and thus prolonging the pain.  Everyone should simply move to IPv6</li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Core questions posed</strong>: Should the policy move forward? Should it include a weighting formula or grandfathering rule?</li></ul><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><ul style="font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Community wants clarity and fairness (grandfathering or equal treatment)<ul style="font-family:arial,helvetica,sans-serif"><li style="margin-left:1in;font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:"Courier New""><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>There was overwhelming support for the addition of a clause to ensure protections for those already on the waitlist. Without this protection clause, there was little to no support for the draft policy.</li></ul></li><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Movement and activity remains mostly deadlocked/stagnant/stalemate.</li><li style="font-family:arial,helvetica,sans-serif"><br></li><li style="font-family:arial,helvetica,sans-serif">Repeated postponement or inaction on waitlist reform has worsened fairness and usability.</li><li style="font-family:arial,helvetica,sans-serif">Reducing to /24 allows ARIN to stretch remaining IPv4 holdings further, giving more organizations a chance to receive space—even if small.</li><li style="font-family:arial,helvetica,sans-serif">The original /22 cap was reasonable when first introduced but no longer reflects current IPv4 availability.</li></ul><div style="font-family:arial,helvetica,sans-serif"><br></div><ul style="font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Circumstances have changed since 2019 when this was first proposed (n a previous recommendation)</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Some persons have changed their position from their initial support of the draft policy</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Waitlist should be abandoned! Alternatively, or refine queue allocation mechanisms entirely</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Is a /24 useful, sufficient, and/or practical for an organization?</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Why still focus on IPv4 with its scarcity when IPv6 is readily available?</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>List is working; Lease market otherwise</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Reducing the allocation from /22 to /24 will not solve any tangible problem, rather create a new one as /24 is too small even for the smaller organizations that are waiting in order to use it properly to connect people and businesses.</li><li style="font-family:arial,helvetica,sans-serif">A /24 is too small for practical enterprise use or for ISPs needing multiple subnets.</li><li style="font-family:arial,helvetica,sans-serif">Suggest abandoning the waitlist entirely, calling it “illusionary.”</li><li style="font-family:arial,helvetica,sans-serif">Claims the policy gives false hope and disadvantages new entrants who need realistic operational space.</li></ul><ul style="font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif">The proposal may be aiming to reduce anxiety from having to wait too long in the waiting list, but the reality is that there aren't IP addresses left to replenish the pool and has been a fact for a while.</li></ul><ul style="font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif"><span style="font-size:10pt;line-height:115%;font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>The wait list is 3 years long (currently much less) and the justifications are two-year projections. There is a fundamental issue with needs-testing here. Does it matter if the needs-tests are accurate at the time of allocation?</li></ul><ul style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif">Support exists for the /24 cap, but the community remains <strong style="font-family:arial,helvetica,sans-serif">divided</strong>—some favor abandonment.</li></ul><ul style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif">Instead of rigid caps, allow applicants to specify both:</li><ul style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Desired block size</strong></li><li style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Minimum acceptable size</strong></li></ul></ul><p style="margin:0px;padding-left:30px;font-family:arial,helvetica,sans-serif">This flexible approach would allow ARIN to better match available inventory to demand, while still giving applicants a realistic fallback.</p><ul style="margin-top:0in;font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif">It should be noted that the issue is not the Waitlist length/size which fluctuates, but wait times have been dropping from a high in excess of 30 months to a current estimate of 18-24 months.</li><li style="font-family:arial,helvetica,sans-serif">It has also been demonstrated (August 2024) that the Waitlist could have been completely cleared on a number of occasions if allocations were limited to /24 cap for all Waitlist recipients</li></ul><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif"><span style="font-family:"Segoe UI Emoji",sans-serif"> </span></strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Based on community input, a <strong style="font-family:arial,helvetica,sans-serif">recommended forward path</strong> is needed.  Opinions and suggestions remains mostly varied.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Future of this Draft Policy </strong>ARIN-2023-8:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Suggestions and Considerations</strong></p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Best case scenario: large IPv4 blocks relinquished/returned,  IPv4 available pool replenished (unlikely)</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Worst case scenario: IPv4 blocks completely run out , Only transfer and lease markets available, or IPv6 transition</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">What happens in the future if demand drops or increases?</p><ul style="font-family:arial,helvetica,sans-serif"><li style="font-family:arial,helvetica,sans-serif">Waiting List is somewhat self-adjusting.</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>Presently, the problem statement may not be completely valid, but this may not continue to be true at some point in the future. If the Waiting List were to expand to where it was before, will it be too late to introduce such a policy?</li><li style="font-family:arial,helvetica,sans-serif"><span style="font-family:Symbol"><span style="font-style:normal;font-variant-caps:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman";font-size-adjust:none;font-kerning:auto;font-variant-alternates:normal;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-east-asian:normal;font-feature-settings:normal"> </span></span>New policy proposal can be submitted if problem continues, unencumbered by any stipulations or requirements which hamper this current proposal.</li></ul><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">There is no perfect fix, though there is interest in allowing more equitable distribution—even in smaller blocks which seeks to provide better support of IPv4 policy goals during exhaustion.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Modify Instead of Abandon</strong>:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Keep the draft alive but revise it to balance fairness, usability, and realism.  This would require significant changes to the text and substantively change the policy and deviate from the initial problem statement.  This, therefore may simply require a new proposal meeting those requirements and incorporating all of those desired changes.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Presently, the statement may not be valid, but this may not continue to be true at some point in the future.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">If the Waiting List were to expand to where it was before, will it be too late to introduce such a policy?</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><br></p><p style="margin:0px;font-family:arial,helvetica,sans-serif">New policy proposal can be submitted if problem continues, unencumbered by any stipulations or requirements which hamper this current proposal.</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p><p style="margin:0px;font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Question</strong>:</p><p style="margin:0px;font-family:arial,helvetica,sans-serif">Should the AC continue working on this policy?</p><p style="margin:0px;font-family:arial,helvetica,sans-serif"> </p></div></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;white-space:normal;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;white-space:normal;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><span style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,128)"><strong style="font-family:arial,helvetica,sans-serif">Gerry E. George</strong></span><br><span style="font-family:arial,helvetica,sans-serif;font-size:small">ICT Consultant and Business Solutions Architect;</span></div><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><span style="font-family:arial,helvetica,sans-serif"><strong style="font-family:arial,helvetica,sans-serif">Digi<em style="font-family:arial,helvetica,sans-serif">Solv</em>, Inc.</strong> [P.O. Box 1677, Castries, Saint Lucia]</span> </div><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><hr style="font-family:arial,helvetica,sans-serif"></div><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><strong style="font-family:arial,helvetica,sans-serif">Mobile</strong>: (758) 728-4858 /<strong style="font-family:arial,helvetica,sans-serif"> Int'l Office</strong>: (347) 450-3444<span style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline!important;color:rgb(0,0,0)"><span style="font-family:arial,helvetica,sans-serif"> </span>/ Skype: DigiSolv</span><br><strong style="font-family:arial,helvetica,sans-serif">Email</strong>: <a href="mailto:ggeorge@digisolv.com" target="_blank" style="font-family:arial,helvetica,sans-serif">ggeorge@digisolv.com</a>    /    <strong style="font-family:arial,helvetica,sans-serif">LinkedIn</strong>: <em style="font-family:arial,helvetica,sans-serif"><a href="https://www.linkedin.com/in/gerrygeorge/" target="_blank" style="font-family:arial,helvetica,sans-serif">https://www.linkedin.com/in/gerrygeorge/</a></em></div></div><div style="font-family:arial,helvetica,sans-serif;font-size:16px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;white-space:normal;text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0)"><span color="#797979" face="Arial" size="3" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;font-family:Arial;font-size:medium;color:rgb(121,121,121)"><br></span><i style="font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;font-size:14px;font-family:"times new roman";color:rgb(0,0,0)"><b style="font-family:"times new roman""><span color="#557a34" style="font-family:"times new roman";color:rgb(85,122,52)">Please consider the environment before printing this email. Thank you.</span></b></i></div></div></div></div></div></div></div>_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div></div>