Summary

  • Draft Policy ARIN-2026-4 would move IPv6 fairness language into general NRPM Section 1. Staff says the sentence is not a definition or a requirement to justify a particular request.
  • ARIN’s Policy Development Process already requires fair, impartial administration under unambiguous guidelines and criteria. That is a policy-level standard, not proof that current decisions are unequal or an individual right to receive resources.

Analysis

The clause is moving to a different level

A small sentence is doing more work than its heading suggests. The current Number Resource Policy Manual places fairness in Section 6.3.6, among the goals for IPv6 address-space management. Draft Policy ARIN-2026-4 proposes a new Section 1.5, putting the principle beside the manual’s general statements about registration, conservation, routability and stewardship. The wording is largely carried forward, but the location changes the apparent scope: the proposal describes a principle for the manual as a whole rather than a goal inside the IPv6 section.

That is the right place to begin, because a move from Section 6 to Section 1 is not just a page-layout decision. The draft’s stated purpose is to harmonise overlapping principles and remove duplication without making meaningful changes. Whether the new placement changes how readers understand fairness depends on how it relates to ARIN’s existing policy-development rules.

What the September review says—and what it does not

The staff and legal review dated 25 September makes three separate points. First, staff reads the draft as a clarification exercise. Second, it suggests removing the examples of location, nationality, size and “any other factor” from the proposed fairness sentence because the list could distract from the simpler rule. Third, it draws a bright boundary: Section 1.5 is not a definition or a justification requirement. Staff separately describes current ARIN practice as fair and impartial for existing and potential members participating in the ARIN region.

Those are statements about intent, drafting and the staff’s account of current practice. They are not a sample of allocation decisions, an audit of outcomes, or evidence that a particular applicant has been treated differently. The review does not publish case-level records or a method for measuring consistency. A careful reading therefore supports a question about how the principle will be expressed and implemented, not an allegation that the current system has failed it.

The draft remains under discussion. ARIN’s published meeting agenda places it in the 22 October ARIN 58 policy block. The September review is an input to that process, not an adoption notice.

Fair treatment does not mean identical eligibility

ARIN’s existing Policy Development Process already gives the fairness principle a practical frame. Section 1.4.1 says number-resource policy must enable fair and impartial administration according to unambiguous guidelines and criteria, and that policy statements should be clear, complete and concise. The same document says the Internet community includes people with different interests and that not every policy statement applies to every member.

That qualification matters. A policy can apply to a defined class of requests, resource types or operating circumstances without treating applicants unfairly, provided the distinction is clear and applied consistently. A request that fails a published technical-need criterion does not become eligible merely because its applicant invokes fairness. Equally, an administrator cannot use a vague or shifting criterion and call the outcome fair simply because the same words appear in the manual.

The distinction is between the rule governing administration and the criteria governing a particular request. The proposed Section 1.5 can state the former. The PDP’s unambiguous-guidelines test helps explain how the rule is assessed. Neither text, on the evidence available, creates a new route to resource space or a request-specific justification procedure.

The geography question needs careful wording

The draft’s examples name location, nationality and size. Staff proposes deleting that list, while describing current application as covering participants in the ARIN region. The public record does not explain whether the proposed sentence was intended to add a separate cross-border guarantee, to illustrate neutral administration, or simply to echo language already present in Section 6.3.6.

This gap should not be filled by inference. The review does not say that applicants outside the region are excluded from every policy, nor does it establish that location affects a particular decision. The PDP itself cautions that policies need not apply identically to every member. A useful clarification would say how the broad language in Section 1.5 coexists with policy-specific eligibility and ARIN’s service-region boundaries, without presenting different criteria as evidence of unequal treatment by themselves.

Implementation is where a principle becomes legible

Staff marks the text implementable as written and expects no impact on registry services or operations; legal review identifies no material legal impact. Yet the implementation estimate is three months, with staff training, public documentation, and internal procedures or guidelines listed as requirements. “No service impact” does not mean that no operating explanation is needed. It means the review does not expect a change to the services ARIN provides.

If the draft advances, the public record could connect Section 1.5 to PDP 1.4.1, identify which language in Section 6.3.6 is being moved or retired, and explain how staff training and policy guidance will use the standard. That would help members distinguish a general commitment to fair administration from a case-specific resource criterion. It would also let later readers test whether the sentence was intended to change process, scope or only placement.

One version detail deserves preservation: the policy page labels its current text 9 July, while the staff review says it assessed the 25 August draft. The page history also lists a 25 August draft version. This record does not show that the fairness wording changed between those versions; it does show why review notes should identify the precise text they assessed.

The measured conclusion is narrow. ARIN is considering a general fairness statement, staff says it is not an individual justification rule, and the PDP already requires clear criteria and impartial administration. The next useful evidence is a versioned explanation of how those pieces fit—not a claim about outcomes the public record does not measure.

Sources