Summary

  • An ARIN holder’s compliance note can misstate its position if it treats the NRPM’s “not property” sentence as the whole account and omits the RSA’s express contractual rights.
  • ARIN-2026-3 would remove that IPv6 sentence while leaving the RSA unchanged, so operators still need both documents to describe the service terms.

Analysis

A network operator assessing the terms of ARIN registry services cannot answer from one sentence alone. The RSA makes those services subject to the agreement and published policies, and names them together as the “Service Terms.” Yet the NRPM’s IPv6 clause says space is allocated for use rather than owned, while RSA §7 gives the holder express contractual rights. A compliance review that treats the policy sentence as the whole relationship—or calls the contract rights ownership—misstates how the Service Terms fit together. ARIN-2026-3 would remove that policy sentence, not amend the RSA.

The draft would retire §6.4.1 of the Number Resource Policy Manual. That sentence appears in the IPv6 chapter and addresses globally unique IPv6 unicast space. Its problem statement says rights language belongs in the Registration Services Agreement rather than the policy manual. The proposal remains under discussion; no change has taken effect.

The current RSA, version 14.0, defines “Included Number Resources” to cover IP address space and ASNs issued or to be issued by ARIN, as well as specified legacy resources. Section 7 gives holders express contractual rights to those included resources. The two documents therefore meet at the holder’s relationship with ARIN, but they do different work: one states an IPv6 policy boundary; the other describes contractual rights across the resources covered by the agreement.

If adopted as written, ARIN-2026-3 would remove the NRPM sentence. It would not amend the RSA or add replacement wording. The record does not say that holders would gain ownership, and it does not support a legal conclusion about property. For a holder explaining its registration internally, the immediate effect would be on the written guidance available in the IPv6 policy chapter, not on a contractual change established by this draft.

The archive offers a useful contrast, not a causal history. ARIN-2022-9, “Leasing Not Intended,” proposed moving a broader property statement into NRPM’s general principles, extending it across Internet number resources, and adding language about leasing. ARIN later marked it abandoned. The 2026 proposal goes the other way: it would remove a sentence limited to IPv6 and points to the RSA for rights language. The two records show different drafting choices; they do not explain why the earlier proposal was abandoned or why views changed.

That leaves a concrete choice for the current discussion. Keeping the sentence gives readers an explicit boundary beside the IPv6 allocation rules. Removing it avoids repeating rights language in a policy manual when the RSA is the agreement that describes the holder’s rights. Either choice leaves a reader-facing task: make it easy to follow the relationship between policy and contract without treating their different wording as a contradiction.

The next useful signal is whether the draft’s discussion adds a clear cross-reference or explanation before the sentence is retired. The question is not whether one sentence settles ownership; the documents do not say that. It is whether a holder can move from the IPv6 rule to the relevant contractual account without having to infer that one replaces the other.

Sources