Summary

  • ARIN-2026-4 is a Draft Policy under discussion, not a Recommended Draft Policy or adopted rule.
  • The proposal moves registration, conservation, routability/scalability, fairness and conflict-of-goals language into Section 1, retires 6.3.2 and 6.3.3 as redundant, and retains IPv6-specific aggregation language in 6.3.4.
  • BTW recommends a public semantic-diff ledger linking each old clause to its proposed destination, actor, scope, modal verb and unresolved interpretation.

The proposal text is dated 9 July 2026. On 20 August, the ARIN Advisory Council voted unanimously to move ARIN-prop-352 to Draft Policy; ARIN announced that status on 25 August. At the 6 September 2026 reporting freeze, the evidence establishes discussion status only. It does not establish consensus, Last Call, staff or legal review, a community presentation, Board adoption or implementation.

ARIN-2026-4 says Sections 1 and 6.3 contain redundant and incongruous principles and goals. Its stated intent is clarification and harmonization without meaningful policy change, and it asks reviewers to flag analysis suggesting otherwise. That stated intent is important, but it is not proof that every clause has the same meaning after consolidation.

The proposed architecture puts registration, conservation, routability/scalability, fairness and conflict-of-goals language in Section 1. It retires 6.3.2 and 6.3.3 as redundant, while retaining IPv6-specific aggregation language in 6.3.4. The proposal also preserves the statement that ARIN allocation or assignment does not guarantee routability by any particular network operator and keeps aggregation as the most important goal when managing IPv6 address resources, with general conflict-of-goals language in new Section 1.6.

The review should begin with the words most likely to disappear inside a harmonization narrative. Current Section 1.1 says registration “guarantees” uniqueness. The proposal says provisioning a public registry is “necessary” to ensure uniqueness of allocated resources. The current text shown in the draft says ARIN “will apply practices” to maximize the potential for contiguous subsequent IPv6 allocations; the older 6.3.4 wording quoted there says RIRs “should apply practices.” The frozen sources do not decide whether these pairs are equivalent or inequivalent.

They establish questions about actor, resource scope, modal strength and document location.

A consolidation can improve coherence while still deserving clause-level review. The issue is not hidden intent, nor an allegation of immediate operational change. It is whether future readers can see what moved, what changed in grammatical force and what remains unresolved. The frozen sources establish neither a policy effect, an allocation outcome nor a legal consequence.

The publication date shown here is the editorial date scheduled for 6 September 2026 in Asia/Shanghai. At the reporting freeze, the actual publication timestamp was not yet set.