Summary

  • Draft Policy ARIN-2026-4 is under discussion. It proposes retiring NRPM 6.3.2 and 6.3.3 as redundant to revised general principles in Sections 1.2 and 1.1.
  • The draft says it is not intended to make meaningful changes. Yet the current and proposed texts use different subjects, modal force, beneficiaries and qualifiers.
  • The difference is textual, not proof of a substantive narrowing. A proposition-level scope map would let the community verify whether each old element is retained, relocated, changed or deliberately omitted.
  • This is the inexpensive stage to resolve the mapping. After retirement, the deleted words remain recoverable, but the accepted reason why each proposition was thought equivalent becomes harder to reconstruct.

The shortest comparison in Draft Policy ARIN-2026-4 is also the most revealing.

Current proposition Proposed destination What changes on the page
Every assignment and/or allocation must guarantee uniqueness worldwide Section 1.2 begins from a general requirement for uniqueness A transaction-level subject and mandatory verb become a general premise
Registration ensures uniqueness of each Internet address Section 1.1 says the public registry is necessary for uniqueness of allocated resources The unit moves from each address to a named resource class
Registration supports troubleshooting from RIRs and IRs to end users Section 1.1 provides operational and security contacts for resource holders The purpose and stated beneficiary are related, but not identical
Registration operates within reasonable privacy considerations and applicable laws No matching sentence appears in proposed 1.1 An express qualifier is no longer repeated there

None of those four rows proves that ARIN is changing the substance of its policy. Context may carry the same meaning. Allocated resources may be intended as shorthand for everything named in the sentence immediately above it. Applicable law applies whether or not the NRPM repeats that fact. A public registry can still be operated with privacy controls.

But each row does show why the word redundant needs evidence. Similar purpose is not yet a map of equivalent scope.

A draft that asks to be tested

ARIN-prop-352 was submitted on 9 July 2026. ARIN’s history records its promotion to Draft Policy ARIN-2026-4 on 25 August. Its current status is Under Discussion.

The problem statement is unusually clear about the intended boundary. Sections 1 and 6 contain redundancies and incongruities; the proposal seeks to clarify the language and remove duplication. It is not intended to make meaningful changes to ARIN’s principles and goals. The text adds that analysis suggesting otherwise should be addressed.

That invitation changes the standard of criticism. It would be unfair to point at a changed noun and pronounce a hidden policy reversal. It would be equally weak to answer every difference with intent alone. The useful task is to break the retiring clauses into propositions and show where each one lands.

ARIN’s Policy Development Process provides the right setting. A Draft Policy is presented for community feedback and evaluated by the Advisory Council. It may be revised in response to community, staff and legal review. Before it can become a Recommended Draft Policy, it must support fair and impartial administration, be technically sound, receive community support and undergo staff and legal review.

In other words, this article is not a post-adoption challenge. It is a drafting test at the stage designed for drafting tests.

What 6.3.2 says that a principle may only imply

Current NRPM 6.3.2 is compact, but its grammar does substantial work. Every assignment and/or allocation of address space is within scope. Each must guarantee uniqueness worldwide. The next sentence calls that an absolute requirement and links it to the ability to identify every public host uniquely.

Proposed 1.2 does not abandon uniqueness. It says that, because uniqueness is required, Internet number resources of each type come from a common number space. It then explains conservation through efficient distribution to organisations with technical need.

The proposed language may embody the same architecture at a higher level: unique number spaces make duplicate delegation impermissible, whatever form the delegation takes. If that is the intended reading, it should be easy to state. Yet the replacement no longer assigns the verb must guarantee to every assignment or allocation. It does not repeat worldwide, absolute, or the public-host rationale.

Those may be unnecessary words. They may be explanatory rather than operative. The proposed general principle may be broader and cleaner. The point of a scope map is to distinguish those possibilities without making readers choose by intuition.

A simple disposition could say: the transaction subject is retained by the phrase Internet number resources of each type; the mandatory effect follows from the common-number-space architecture; the worldwide and host-level language is explanatory and omitted without changing scope. Or the review may find that one phrase should be restored. Either outcome would answer the question more precisely than redundant alone.

Registration carries more than one proposition

Current 6.3.3 is harder to retire by label because it bundles several claims. Internet address space must be registered. The database must be accessible to appropriate members of the Internet community. The record is necessary both for uniqueness of each address and for troubleshooting at every level, from registries to end users. Finally, the goal is bounded by reasonable privacy considerations and applicable laws.

Proposed 1.1 has substantial overlap. It calls for a public registry documenting allocation, reallocation, assignment and reassignment. It supplies operational and security contacts, transparency for efficient use, and data for research and reporting.

That is not a weak replacement. In some respects it is more concrete. It names four kinds of registry action and improves the contact language. Yet its first purpose is written as ensuring the uniqueness of allocated resources. The next purpose centres contacts for resource holders. Research concerns allocation activity.

The opening sentence is broad; the bullets use narrower nouns. A sympathetic reading treats them as ordinary shorthand. A literal reader may ask whether reallocated, assigned and reassigned resources are included in the uniqueness purpose that follows. The text itself does not mark the relation.

The troubleshooting comparison also deserves precision. An operational or security contact can support fault resolution, but it is not the same proposition as maintaining reference information for troubleshooting from RIRs and IRs through end users. One describes a contact entity; the other states a multi-level use of registry information.

Then there is the final qualifier. Deleting the words reasonable privacy considerations and applicable laws cannot delete privacy law. Nor does it prove that ARIN plans broader disclosure. But a consolidation record should still say whether the qualifier is implicit, governed elsewhere, relocated, or intentionally removed as non-operative. Silence leaves four explanations where one would suffice.

Section 2.5 does not make the nouns interchangeable

The current NRPM defines an allocation as a block issued directly by ARIN to a customer. It says Assignment is no longer used to describe IP addresses issued by ARIN. It separately defines reallocation as a subdelegation for further distribution, and reassignment as a subdelegation for the recipient’s exclusive use.

It would be tempting to use that definition as a shortcut: if ARIN no longer calls direct issuance an assignment, perhaps allocated resources covers everything important. The rest of the manual makes that conclusion too quick.

Section 4.3 remains Assignments to End-users. Section 6.5.4 regulates reassignments by LIRs and ISPs. Section 6.5.5 imposes registration duties on both reassignments and reallocations. Section 6.5.8 is headed End-user Allocations, but its subsections still discuss initial assignment criteria, assignment size and subsequent assignments.

This is not evidence that the NRPM is invalid or that staff cannot interpret it. It is evidence that the vocabulary has a history. A consolidated principle should say whether allocated resources is a collective term, a defined class, or a phrase that needs widening. Otherwise an editorial cleanup may preserve meaning for experienced entities while making it less legible to everyone else.

Make redundancy a disposition, not an adjective

ARIN does not need a new governance system to solve this. A short appendix, annotated redline or table attached to the draft could map each retired proposition to a destination.

The minimum record would identify the source span, its subject and responsible actor, the resource or transaction type, modal force, purpose or beneficiary, and any qualifier. It would point to the target span and choose a disposition: retained verbatim, retained by a broader term, changed, relocated, merged, omitted as unnecessary, or unresolved. A sentence of rationale would explain the choice.

That design does not privilege criticism. Retained by a broader term may be the correct result for most rows. A map could give the authors and shepherds stronger evidence that the consolidation does exactly what they intend. It would also let one disputed row be repaired without reopening every principle in Sections 1 and 6.

The distinction matters because a redline answers only where words moved. It does not answer why two differently framed propositions were accepted as equivalent. Version history preserves text; it rarely preserves the community’s semantic judgment at clause level.

The draft proposes other changes beyond these two retirements, including moving conservation, routability, fairness and conflict-of-goals language. Those deserve their own review. This article’s finding is narrower: 6.3.2 and 6.3.3 contain enough separable scope to require more than the label redundant.

Sources