Summary

  • ARIN-2026-4 moves shared principles into the general NRPM section and keeps an explicit “most important” aggregation sentence in the IPv6 section.
  • The draft remains under discussion. ARIN staff expects no operations or service impact, and no allocation, routing or operator outcome has changed.

Analysis

One set of principles, two different jobs

ARIN’s Number Resource Policy Manual currently asks readers to find related principles in two places. Section 1 covers registration, conservation, routability and stewardship for Internet number resources generally. Section 6.3 then restates several of those ideas for IPv6, alongside goals particular to address management: uniqueness, registration, aggregation, conservation, fairness and minimized overhead.

The duplication is not merely editorial. The two sections describe conflict differently. Section 1.4 says its goals may sometimes conflict and asks for balance in light of resource availability, resource size and technical dynamics. The IPv6-specific Section 6.3.8 says the goals will often conflict, names the Internet registries that evaluate allocation and assignment requests, and says they must balance an applicant’s needs against those of the wider Internet community. It then gives IPv6 aggregation the highest stated priority.

ARIN-2026-4 proposes a cleaner map. It moves IPv6 conservation language into general Section 1.2, moves generic hierarchy and routing-scalability language into a new Section 1.3, and adds general Sections 1.5 on fairness and 1.6 on conflicts. It proposes retiring IPv6 uniqueness and registration as redundant, while retaining IPv6 aggregation and minimized overhead in Section 6. The stated objective is clarification and removal of duplication, not a meaningful change in policy goals.

That structure preserves a useful distinction: the general manual can describe principles common to number resources, while the IPv6 section can retain a priority that is specific to IPv6. In the proposed text, Section 1.3 explains why hierarchical distribution can help aggregate routing information and limit table growth; Section 6.3.4 keeps the sentence that aggregation should be considered the most important goal when managing IPv6 resources. Neither statement guarantees that a particular operator will route an allocation, and the draft retains the warning that subsequent contiguous space cannot be guaranteed.

One other edit deserves equal attention. The current contiguous-allocation sentence says RIRs “should apply” practices that maximize the potential for later allocations to sit next to existing space. The proposal says ARIN “will apply” those practices, then keeps the express caveat that contiguous allocation cannot be guaranteed. The named actor becomes more specific and the verb sounds firmer, while the outcome remains uncertain. That is a visible change in wording to reconcile with the staff assessment of no operational impact; it is not proof that a particular holder will receive contiguous space.

The seams matter as much as the headings

The published draft contains a precise wording question that a heading cleanup does not answer. Current Section 6.3.8 says that IPv6 aggregation “is considered to be” the most important goal. The proposal’s replacement says it “should be considered” the most important. That may be intended as a stylistic restatement. But “is considered” describes the policy’s present formulation; “should be considered” reads more directly as guidance. The text alone does not establish whether ARIN intends a change in force, so the difference is a question for the policy process rather than proof of a new allocation rule.

There is also an internal cross-reference worth testing. The displayed proposal says to retire Section 6.3.8 as redundant to new Section 1.6, “which now calls out the IPv6-specific priority of conflicting goals.” Yet the displayed Section 1.6 is a general conflict-of-goals statement. The explicit IPv6 aggregation priority remains in Section 6.3.4. Readers should ask whether the retirement note points to the wrong subsection, whether a sentence is missing, or whether the intended relationship is simply that general balancing and the IPv6 priority operate together. The draft does not resolve that by itself.

The staff and legal review, dated 25 September, adds another implementation-level seam. Staff says the draft is implementable as written, sees no registry-operations or service impact and no material legal impact, and estimates three months for staff training and updates to public documentation, internal procedures and guidelines. It nevertheless recommends making the intended retirement of IPv6 Sections 6.3.5 and 6.3.6 explicit after their content moves to Section 1.

That is a useful reminder that a “retired” label and a moved paragraph are different pieces of evidence: the final manual should leave no ambiguity about which operative text survives.

The review also questions the proposed fairness qualifier—“regardless of their location, nationality, size or any other factor”—as potentially extraneous. Staff says fairness is not a definition or justification requirement and describes current practice as fair and impartial to participants in the ARIN region. The proposal keeps the qualifier. Whether it remains may matter to how clearly the principle travels across different actors and resource contexts, but the review does not identify a present unequal-treatment finding or say the qualifier changes current eligibility.

Consolidation does not mean identical scope

The main analytical test is not whether Section 1 becomes shorter or Section 6 loses repeated clauses. It is whether a future reader can identify three things without reconstructing the proposal history: which principles apply across number-resource types; which additional priority applies specifically to IPv6; and who must exercise judgment when the principles conflict.

The draft improves the first distinction by moving shared concepts into one place and retaining aggregation in the IPv6 section. Its treatment of the third is less explicit. The old IPv6 text names “all IRs evaluating requests” and says they “must make judgments.” New Section 1.6 instead says that “care must be taken” to balance goals, without naming the actor in that sentence. A general section may be meant to reach every resource type, but a passive instruction can make responsibility harder to locate unless another provision supplies it. That is not an operational change by itself; it is a drafting question about traceability.

Staff’s review is a check on the practical stakes. It assesses the draft as implementable and expects training and documentation work rather than changes to registry services. The proposal’s own problem statement invites reviewers to identify unintended policy changes. A close reading can therefore accept the stated cleanup objective while still testing its seams: the modal verb in the IPv6 priority, the reference to Section 1.6, the actor in the balancing clause and the explicit status of moved subsections.

Participation can find ambiguity; procedure determines the rule

ARIN’s Policy Development Process gives comments a defined role without making a meeting or mailing-list exchange equivalent to adoption. Community feedback can be submitted through the Public Policy Mailing List, Public Policy Consultations and recognized meetings. The Advisory Council may revise a draft and may advance it when it meets the process criteria and has staff and legal review. A Recommended Draft Policy then proceeds through consultation and Last Call; advancing it to the Board requires a two-thirds affirmative Advisory Council roll-call vote. The Board may adopt or reject it.

Only adoption integrates a policy into the NRPM for staff implementation.

The record so far is limited. The Advisory Council’s 20 August minutes show ARIN-prop-352 advancing to Draft Policy by a motion carried unanimously on the recorded roll call. September results list ARIN-2026-4 among drafts still under Council work. ARIN’s current page labels it “Under Discussion.” The 8 October ARIN 58 announcement schedules discussion for 22 October at 2:15 p.m.; on the 12 October editorial date, that session has not happened. None of these facts is an adoption decision.

The distinction is practical. Participation is where a reader can point to ambiguous language, show how a clause could be read, or test it against allocation experience. Authority is exercised through the specified steps and votes. Counting attendees or comments cannot substitute for the Council’s advancement decision or the Board’s adoption. Conversely, a formally valid step does not make the wording self-explanatory. A good process needs both an accessible channel for criticism and a final record that shows what was decided.

For network operators and resource holders, the immediate operational conclusion is modest: continue to read the NRPM currently in force. ARIN states that this draft has no expected impact on registry operations or services. It does not alter current allocation eligibility, create a routing guarantee, promise contiguous allocations or report a measured change in routing tables. Its consequence, if adopted, would first be a reorganized statement of principles and updated staff and public materials; any later operational effect would need separate evidence.

Sources