Summary

  • Resolution 2026-05-04 authorises APNIC’s Secretariat, acting through the Director General, to adopt, amend, suspend or retire service terms only when they are operational or administrative and do not amend Internet number resource policy.
  • The same resolution makes materiality consequential: material service-term changes must be notified to the Executive Council, while a separate branch governs Privacy Statement amendments.
  • The checked public record publishes the authority but not a change-level record joining an exact diff to those classifications, to APNIC-112 official-document review, and to notice and effective dates.

Two short clauses in APNIC’s May 2026 Executive Council minutes perform a large amount of institutional work. The first delegates authority. The fourth defines when the Council must be told that the authority was used. Between them sit two questions that cannot be answered by looking at a current web page alone.

Was this change merely operational or administrative, or did it amend Internet number resource policy? Was it material?

The public minutes do not leave the delegation vague. Resolution 2026-05-04 authorises the APNIC Secretariat, acting through the Director General, to adopt, amend, suspend and retire terms and conditions governing APNIC services. That authority is available only where the terms are operational or administrative in nature and do not amend Internet number resource policy. The Secretariat must notify the EC of material service-term changes made under the delegation.

That is not a blank cheque. It is a practical division of labour. A registry needs to maintain products, accounts, interfaces and service rules without asking its board or policy community to approve every low-risk adjustment. The resolution also protects the other side of the line: the administrative route cannot be used to amend number-resource policy.

The question is narrower. How does the public record preserve the reason that a specific change fell on one side of that line?

One resolution, three different classifications

The resolution’s Privacy Statement provisions show why the verbs matter. The EC adopted an updated statement and allowed APNIC Legal Services to make administrative amendments needed for publication. It then delegated non-material amendments required by administrative or legal needs to the Director General. An amendment that may pose material legal, financial or reputational risk to APNIC must instead be referred to the EC for approval. Every Privacy Statement update approved under the delegation must be reported to the Council.

Service terms take a related but different route. The Director General’s delegated authority is conditioned on operational or administrative character and on not amending Internet number resource policy. Material changes are notified to the EC. The text does not say that notification is prior approval, and it would be inaccurate to convert it into one.

The resulting state model has at least three axes:

Classification question Why the answer matters
Operational or administrative? Determines whether the delegated service-term route is available
Does it amend Internet number resource policy? Preserves the boundary between service administration and community policy
Material or non-material? Determines whether EC notification or, in the Privacy branch, EC approval is engaged

These are predicates, not slogans. A change could be operational in implementation yet materially affect users. A legal wording update could be non-policy but still alter how a right is exercised. A document could combine service instructions with terms that describe a legal relationship. The public value lies in recording how the institution classified the exact diff, not in assuming that one label answers every question.

No checked source proves that APNIC has applied these predicates incorrectly. No checked source identifies a post-resolution service-term change that escaped notice or crossed into policy. The institutional gap is about reproducibility before a dispute supplies a dramatic example.

APNIC-112 creates a second boundary

The APNIC Document editorial policy, APNIC-112, defines official documents as documents created by APNIC to describe policies, membership rights and obligations, and legal relationships. It excludes reports, proposals, presentations, brochures, forms and general website content. For official documents, it describes public drafting and comment, incorporation of comments, final publication and version labelling.

That scope does not mean every service term must enter the Policy Development Process. APNIC-112 distinguishes document maintenance from policy authority, and its public review can begin for reasons other than a new consensus decision, including correcting errors and improving wording or presentation. Nor does a term become an official document merely because it sits on APNIC’s website.

But the intersection matters. Some service terms may describe legal relationships or membership obligations; others may be ordinary instructions for a product. Resolution 2026-05-04 uses one classification—operational or administrative, not number-resource policy—while APNIC-112 uses another—official document or excluded material. The checked public sources do not publish a change-level join between them.

This is especially relevant because APNIC’s Standard Membership Agreement says APNIC Documents may be amended under the Document Review Policy, that such amendments bind the member, and that the documents as they exist from time to time form an integral part of the agreement. The Non-Member Resource Services Agreement contains the same general structure for organizations receiving services without membership.

Those agreements do not prove that every service term is an APNIC Document. They prove why classification is not clerical decoration. Depending on the document, version state can sit close to the boundary between product administration and a binding relationship.

A current page proves less than a change record

The current APNIC Privacy Statement supplies positive evidence of notice discipline. It says changes will be announced on APNIC’s website and records 14 May 2026 as its last update, the second day of the EC meeting.

That is better than an undated page. It establishes a current date and a commitment to announce changes. It does not, on the page itself, show the prior version, clause-level diff, materiality decision, approving role or EC notification identifier. The absence of those fields does not prove that no announcement or internal record exists elsewhere. It only shows that a reader cannot reproduce the decision path from the current page alone.

The same distinction should govern service terms. Publication of a current version answers “what applies now?” It may not answer “what changed?”, “which authority was used?”, “why was this outside policy?”, “was APNIC-112 engaged?”, or “when did an affected user receive notice?”

Those questions do not require a new oversight institution. They require a receipt.

The receipt can stay small

A useful public change-classification record would begin with identity: a stable change ID, affected service, document title and version, hashes for the prior and new texts, and a clause-level diff. It would then record a bounded effect statement rather than reproduce privileged advice.

The next fields would answer the institutional tests. Is the change operational or administrative? Why does it not amend Internet number resource policy, and which policy surface was checked? Is the document an APNIC-112 official document? If so, what review path applied; if not, what category excludes it? Is the change material, and which risk dimensions were considered?

Finally, the record would join decision to time: approving role, approval timestamp, EC approval or notification where required, affected-party notice channel, effective date, transition window, current-version pointer, and any later correction, supersession or rollback.

Receipt layer Minimum public evidence
Identity Change ID, service, document/version, prior and new hashes
Effect Clause diff and a plain, source-faithful effect summary
Authority boundary Operational/administrative reason and policy non-amendment statement
Document boundary APNIC-112 status and review path or non-applicability reason
Materiality Classification, risk dimensions, approving or notifying role
Time Notice, effective time, transition and correction lineage

The reason can be narrow. “Changes the authentication retry interval; does not change eligibility, delegation size, transfer conditions or resource-holder obligations” tells a reader more than a generic administrative badge. Where legal advice is privileged, the receipt can state the tested category and outcome without publishing the advice. Where security detail is sensitive, the public diff can identify the rule’s effect without revealing attack parameters.

This design also preserves reversibility. Adopt, amend, suspend and retire are four different events. A current-document link can represent only one state at a time. An append-only change relation can show that a suspended term was restored, a version was corrected, or a retirement was superseded without pretending that the earlier state never existed.

What the record does not establish

The public PDF says proposed procedures were presented to the EC. Across the frozen 93 pages, however, the service-term language appears only in the agenda and Resolution 2026-05-04. That does not prove that an internal procedure is absent. It means the procedure is not available in this public PDF for a reader to apply.

There is no evidence here of unlawful delegation, a hidden policy change, a member harmed by a new term, a failure to notify the EC or an attempt to evade APNIC-112. There is also no basis for declaring that every user-facing term is policy or that every administrative edit needs a month-long consultation.

The concern is institutional memory. Resolution 2026-05-04 publishes a carefully bounded authority. A change-classification receipt would preserve that care at the unit where it can be tested: one change, one exact text transition, one reasoned route and one effective state.

Sources