Summary

  • ARIN's five-year waiver lets a 3X-Small organisation receive registry services for up to /36 of total IPv6 space without moving into the 2X-Small billing category; it expires on 31 December 2026.
  • From 1 January 2027, aggregate holdings will determine the applicable category. ARIN says affected customers may move up one tier and will be contacted about the fee effect and available options.
  • The 9 July notice does not state the beneficiary count, contact timetable, delivery evidence, option list or planned aggregate results. A privacy-safe transition ledger should close that gap before and after expiry.

The prefix stays still while the invoice state moves

The externally archived announcement describes a simple clock. The waiver began with the 2022 Fee Schedule as a five-year incentive for smaller organisations to adopt IPv6. It allows an account in the 3X-Small category to receive service for as much as /36 of aggregate IPv6 space without being charged at 2X-Small. The concession ends on 31 December 2026.

On 1 January, the underlying resource does not expand, migrate or become less unique. What changes is the rule used to classify the account. ARIN says Registration Services Plan billing will follow aggregate Internet number-resource holdings and that organisations now benefiting from the waiver may move from 3X-Small to 2X-Small.

That distinction matters. This is not a new allocation policy and not a recall of IPv6 space. It is a scheduled change in the recurring price attached to an existing registry-service state. A public record should therefore describe the billing transition precisely rather than allow the word expiry to stand in for every case.

The deadline is not a surprise. In a 2023 NANOG explanation, Jon Lewis quoted the 31 December 2026 end date and described the mechanism as permitting a 2X-Small quantity of IPv6 space while retaining the 3X-Small annual charge during the waiver period.

The fair question is therefore not whether ARIN may honour a published end date. It is whether the institution will make the execution of that end date observable.

We will contact customers is a plan, not yet a ledger

ARIN's July notice says it will contact impacted customers, explain the possible effect on their 2027 fees and tell them how to ask about available options. That is useful advance warning. It is also only the first state in a longer process.

A notice can be generated but not delivered. It can reach a mailbox whose contact has left. It can be delivered but not understood. An account can receive it and still lack the facts needed to compare options. A customer may request a correction before the new category is applied. Another may keep the resource and accept the charge. Those outcomes are not interchangeable.

The announcement does not say how many organisations are currently covered by the concession. It does not give a date for the individual notices, identify delivery and acknowledgement measures, list the options or their deadlines, or promise grouped results after the change. Those are observations about the notice, not assertions about what ARIN knows internally.

The minimum public ledger can remain compact:

Transition field What the public record should show
Population Aggregate number of organisations benefiting from the waiver at a dated snapshot
Notice Send window, channel mix, delivery failures and corrected contacts
Choice Available options, eligibility, deadline and the evidence required for each
Application Counts projected to remain 3X-Small or move to 2X-Small before billing
Correction Number of disputed or corrected classifications and time to resolution
Outcome Grouped final category changes, resource changes, unresolved cases and non-renewals

No row requires a customer name, Org ID, prefix or invoice. Aggregation protects commercial and operational privacy while still answering whether the transition worked.

A known rule can still have uneven weight

The historical discussion is a warning against reading a published fee as economically uniform. One NANOG participant argued that a modest annual registry charge can be a real headwind in lower-income parts of ARIN's service region. Another operator response pointed to non-profits that operate under tight budgets. These are practitioner observations, not a representative measure of all beneficiaries, and they do not prove that the 2027 transition will cause harm.

They do establish why aggregate reporting should not stop at notices sent. The same category change can be immaterial to one holder and budget-relevant to another. ARIN need not publish balance sheets to recognise the difference. It can group outcomes by transition path, show how many accounts sought an option or correction and report whether a notice failed before billing changed.

Terminology has already caused confusion once. In 2023, ARIN President John Curran acknowledged on NANOG that fee waiver was not an ideal label and explained that the public wording had been expanded. The concession never meant that all IPv6 service was free. It meant that a specific range of holdings could remain in a lower category for a defined period.

That clarification is a useful precedent. When a label is broader than the state change it describes, publish the state change.

Closing an incentive requires an outcome record

ARIN says the arrangement was intended to support IPv6 adoption. An incentive with a purpose creates two different accountability questions. The first is administrative: were beneficiaries identified, notified, given accurate options and billed under the correct category? The second is evaluative: did the concession change requests or deployment in the way its designers intended?

The first can be answered from registry and billing operations. The second cannot be inferred from the first. An allocation is not proof of deployment; a retained /36 is not proof of traffic; a returned block is not proof that a network abandoned IPv6. Any future evaluation would need carefully defined evidence and a baseline.

That is why the 2027 closure record should resist easy claims. Publish counts for notification and classification. Publish resource-change counts if they occur. Label adoption effects unknown unless measurements support them. A good ledger makes modest facts visible without manufacturing a success or failure story.

Heng Lu's Bill of Rights of Uniqueness Coordination argues that scarcity does not give a registry an unlimited claim on institutional rent and that common coordination should remain thin. Applied here, that doctrine does not imply a permanent subsidy or a zero fee. It asks for proportionality and attribution: what registry service is priced, which published rule changes the price, who is affected, what remedy corrects an error and what evidence shows the change was carried out as announced.

ARIN has already supplied the date. Before 31 December, it should supply the count, milestones, option map and correction route. After the affected 2027 billing cycles, it should publish the grouped disposition of the transition. The waiver can end on schedule without leaving its implementation off the public record.

Sources