Summary

  • ARIN’s 23 February 2026 review assessed the 25 March 2025 text of ARIN-2025-3 and anticipated higher Waiting List request volume and staff ticket workload.
  • A revised 20 August 2026 text bars out-of-region use as a justification for IPv4 from the Waiting List, the Micro-allocation Pool and the block dedicated to IPv6 deployment. The 11 September review assessed that later text and entered “None” for its impact on ARIN Registry Operations and Services.
  • The new label is not an observed workload count, and the old forecast was not a measured outcome. The public record does not explain whether the changed Waiting List rule accounts for the change in assessment.

Analysis

The dates are part of the evidence

Two short entries appear to answer the same question differently. They do not, however, examine the same text.

The first Staff and Legal Review is dated 23 February 2026. Its final line identifies the policy language assessed as text from 25 March 2025. Staff then described a possible increase in IPv4 Waiting List requests. The review gave a concrete path: an organization could seek an initial /22 from the list, use one /24 in the ARIN region and justify three /24s outside it, subject to the policy requirements. Staff expected more requests and more ARIN space used out of region, and the operations-and-services field anticipated an increase in ticket workload.

The later review is dated 11 September 2026 and assesses the revision published on 20 August. That text changes the route. Out-of-region usage may not be used to obtain IPv4 space from the Waiting List, the Micro-allocation Pool or the dedicated block for IPv6 deployment. Organizations already on the Waiting List when implementation occurs keep the rules that applied when they joined.

That difference could matter to the earlier forecast. If one route that staff expected to attract requests is no longer eligible for the new justification, the projected ticket increase attached to that route may no longer apply in the same way. But ARIN does not say that this is why the later review records “None.” It is a plausible reading of the sequence, not a reported explanation.

“None” is a field, not a measurement

The 11 September review still treats the potential scope of the policy seriously. Staff says that neither current Section 9 nor the draft sets a maximum amount of IPv4 space that can be justified for out-of-region use when an organization meets the in-region /24 test. The review says the text is implementable as written, estimates three months for implementation, and lists staff training, public documentation and internal-procedure updates.

Those statements can coexist. A policy may require one-time changes to training and documents while staff expects no continuing effect on the registry’s services. The problem is not that “None” logically rules out every implementation task. It is that the public page does not tell readers what the impact field is measuring, which assumptions changed, or how the earlier forecast was retired.

The earlier phrase is not a count of tickets that arrived. It is staff’s expectation. The later entry is not proof that no applicant, holder, transfer market or network could be affected. It is the answer recorded under a narrower heading: impact on ARIN Registry Operations and Services. Neither document reports an actual application, approval, issuance, deployment or ticket count.

The draft remains a draft

The revised text changes the general IPv4 threshold from /22 to /24, while retaining a requirement for a real and substantial connection with the ARIN region, proof of that connection, and use of the same resource type with lineage to an ARIN allocation or assignment. Those three exclusions remain separate from the general threshold change. The IPv6 and ASN criteria are not changed by this proposal.

On 22 September, the Advisory Council advanced ARIN-2025-3 to Recommended Draft Policy status. That is a later stage in the policy process, not Board adoption. The policy page still presents the recommendation for discussion. For an operator making a request now, the existing Number Resource Policy Manual remains the operative source; a recommended draft is not a new eligibility rule.

A small public addition could close the documentary gap without adding a new approval hurdle or a new resource rule. The staff review could identify the exact version it assessed, note that the Waiting List path described in February was removed from the August text, and explain whether that change is the reason the later impact field says “None.” If it is not, ARIN could state what the field covers and what the assessment deliberately leaves outside its scope.

That explanation would not need to publish applicant identities or invent a measure that the policy has not adopted. Its job would be simpler: let a reader compare the two staff judgments without guessing which policy change, operational assumption or definition of impact connects them. Until that bridge is published, both entries should be read as dated assessments of different texts—not as proof of increased workload, zero workload or a contradiction.

Sources