Summary

  • The Empowered Community certified the two amendments on 3 July 2026 with four supporting Decisional Participants, one abstention and no objection recorded: support one above the floor of three, with the single tolerated objection unspent.
  • The approved text moves the Customer Standing Committee's effectiveness review from every three years to every five, and starts the IANA Naming Function Review cycle from the previous team's final report rather than from the day it convened.

The document that settled it runs to one page. The Empowered Community Administration's certification, dated 3 July 2026, certifies that the Address Supporting Organization, the At-Large Advisory Committee, the Country Code Names Supporting Organization and the Generic Names Supporting Organization approved the Fundamental Bylaws amendments to Article 17 and to Article 18, Section 18.2(b), and it names the two Board resolutions that produced them. Read the certification itself; the word 'approved' is doing all the work, and it is doing it four times.

ICANN's action record keeps the ledger: 'ACTION STARTED ON 11 MAY 2026 - TERMINATED ON 03 JULY 2026', with links to the Administration's approval notice and to each participant's recorded position — GAC abstention, GNSO support, ALAC support, ASO support, ccNSO support. Four supports. One abstention. Nothing recorded as an objection.

The test the Bylaws set

Annex D of the ICANN Bylaws fixes the arithmetic. Approval of a Fundamental Bylaws amendment requires the support of at least three Decisional Participants — including the relevant policy-development participant where the Board's notice contains a policy-development statement — and no more than one objection. A participant that does not notify the Empowered Community Administration is deemed to have abstained. Article 25.2(b) adds the Board's own side of the gate: such an amendment takes effect 'only upon approval by a three-fourths vote of all Directors and the approval of the EC'. A timely Approval Notice puts the amendment 'in full force and effect as part of these Bylaws' as soon as the Secretary receives it.

That is a bounded veto, not a consensus test, and the distinction matters more than the outcome. Three supporters carry the day. One objection is absorbed. Two objections kill it. Silence is not a block; silence defaults into the abstention column and is counted there.

The arithmetic, done at the boundary

The recorded result sat one step from the edge on both sides. Four supports against a floor of three: one to spare. Zero objections against a tolerance of one: the slot unspent. Reverse either figure by a single participant and the same amendment fails — a second objection defeats it on the identical record. This is our arithmetic on the stated threshold, not a figure any of the publishers prints, and it is the most useful number in the file. A gate that passes at four-to-nothing-toward-one passes without demonstrating agreement. It demonstrates sufficiency.

From the Secretary's notice of 11 May 2026 to the certification of 3 July 2026 is fifty-three days. That is our count from two stated dates. It covers a Community Forum, a re-opened decision period, and five separate participant determinations.

What the two amendments do

The Board's approved resolutions of 3 May 2026 carry the substance. Resolution 2026.05.03.11 approved the Article 18, Section 18.2(b), amendment; Resolution 2026.05.03.12 approved the Article 17 amendments; Resolution 2026.05.03.13 approved related Customer Standing Committee Charter updates and made them effective only if the Article 17 amendments cleared the Empowered Community process.

Article 17, as the ASO's follow-up notice describes it, lets the Registries Stakeholder Group and the ccNSO each identify one alternate CSC member and lets selecting entities name alternate liaisons; it moves attendance and vacancy detail into the CSC Charter; and it changes the regular effectiveness review from three years to five, measured from delivery of the prior review's final report, with an earlier review available on request from specified bodies. Article 18, Section 18.2(b), does one thing: it measures the five-year periodic IANA Naming Function Review cycle from the previous team's submission of its final report to the Board instead of from the team's convening. Purpose, scope, composition and powers are unchanged.

The Board's stated rationale ties each change to a recommendation — Article 17 to the Second CSC Effectiveness Review, Article 18 to the Second IANA Naming Function Review's recommendation on review timing — and records that the ability to initiate a Special IFR is preserved.

Here is the fact: the intervals lengthen as a matter of text. Here is the interpretation, and it is ours: on the old cadence, fifteen years implied five effectiveness reviews; on the new one, three. Fewer checkpoints per decade is a consequence of the amendment, not a claim about anyone's motive, and the Board's stated purpose — giving review teams room to finish and to see recommendations implemented — does not repeal the consequence. Both statements can be true at once. Only one of them is written into the Bylaws.

Who decided for the number community

The number community's yes was produced by a procedure that predates this episode by six years. The ASO's Procedures for Empowered Community Powers, a page that states it was last modified on 3 March 2020, classify Fundamental Bylaws amendments as Approval Actions requiring a Community Forum, require the NRO Secretariat to arrange an NRO Executive Council teleconference at least three days before the ASO decision deadline, and assign the Council the determination of whether the ASO supports, objects or abstains, with the ASO's Administration representative carrying that position into the Empowered Community.

The Administration's mailing list put the Community Forum on Thursday, 11 June 2026, 08:00–09:15 UTC. The follow-up notice of 12 June 2026 states that the Forum had been convened during ICANN86 and that a fresh 21-day decision period had opened, closing at 23:59 PST on Thursday, 2 July 2026 — 06:59 UTC on 3 July. It also states that the NRO Executive Council would consider RIR community input before fixing the ASO's position.

What this review did not obtain: the Council's own deliberation or vote record; any ASO or NRO record of RIR community input actually received during the comment window; and the GAC's reasoning for abstaining. Those are retrieval boundaries, not findings about the documents. What is established is narrower and sufficient: the Bylaws counted a position, and the position was produced elsewhere, by a body whose route to it is not part of the certified record. The gate counts yeses. It does not collect derivations.

Three dates that do not agree

The paperwork is not seamless. The follow-up notice refers to the earlier notice as published on 29 May 2026, while the ASO notice and the NRO-hosted copy are both dated 12 May 2026. The action page labels the Administration's correspondence as dated 3 July 2025; the linked certification says 3 July 2026, and so do the action's own start and termination lines. The Secretary's notice attaches amendment pages still carrying 'Draft for Public Comment' and 'Discussion Draft' labels, while its text states the approved amendments are identical to the versions previously posted for comment.

None of the three changes the outcome. All three are the kind of drift that accumulates when a process runs through five institutions and four calendars. Read them as a reminder that a certified result is a compiled document, assembled by people under deadline.

What the record will and will not carry

Rely on this: the amendments are in force, they were approved through the mechanism the Bylaws prescribe, and the margin was one support and one tolerated objection wide. Do not rely on this: that a community consensus endorsed them, that any participant examined anything in particular, or that longer intervals serve review quality — the last of which the text does not assert even though the Board's rationale gestures at it.

A reader who treats 'community approval' as a check on institutional change now has a cleaner view of what the check is. It is a headcount with a veto attached, run on a clock, executed by procedures each participant writes for itself. That is not a complaint. It is the design, and on 3 July it worked exactly as designed, at exactly the width the design allows. The directory entry holds the underlying notice and its record.