Summary

  • The Empowered Community has five Decisional Participants. ALAC petitioned against the Article 27 Standard Bylaws Amendment; no other participant supported the petition, so the process terminated automatically under Annex D §2.2(d)(ii) without ever reaching a threshold count.
  • The documents obtained print two different support thresholds, and the operative Annex D §4.1(a) sentence was not obtained in this review — but neither number was tested, because the pair gate came first. The three budget and plan tracks ended on a different ground entirely: no petition at all.

The Board approved four things on 3 May 2026: a Standard Bylaws Amendment to Article 27, the IANA FY27 Operating Plan and Budget, the ICANN FY27 Operating Plan and Budget, and the ICANN FY27-31 Operating and Financial Plan. The ASO Secretariat's notice to the RIR Community, dated 12 May 2026, opened the Rejection Action Petition Period and printed an end date of 1 June 2026 at 06:59 UTC. It invoked Section 25.1 of the ICANN Bylaws for the amendment and Section 22.4(b)(v) for the budgets and plan, and told readers that any individual could petition any Decisional Participant during the window, with petitions to the ASO going to the ASO Secretariat before the deadline.

Then the clock moved. On 29 May 2026 the EC Administration wrote to the ECAdmin list to say that 11 May 2026 would be treated as the Rejection Action Board Notification Date under Annex D §2.2(b), and that the petition period therefore ran to 1 June 2026 at 23:59 PDT — 06:59 UTC on 2 June 2026.

Two institutional messages, two dates. The Empowered Community Administration's certificate later records the ALAC petition notice as sent on 1 June 2026 with no time of day attached. Whether it landed inside the ASO's printed deadline or inside the Administration's revised one cannot be settled from the documents obtained in this review, and nothing in the termination turns on it. File the discrepancy; it is not the finding.

Seven days, one partner, no takers

On 2 June 2026 the EC Administration reported the petition: one Rejection Action Petition Notice from the At-Large Advisory Committee on the Standard Bylaws Amendment. Under Annex D §2.2(d)(i), that opened a Rejection Action Petition Support Period expiring at 23:59 PDT on 8 June 2026, or 06:59 UTC on 9 June.

That same message disposed of the rest of the docket. The four 21-day petition periods had expired, no other petitions were received, and the rejection processes for the IANA FY27 Operating Plan and Budget, the ICANN FY27 Operating Plan and Budget and the ICANN FY27-31 Operating and Financial Plan were terminated under Annex D §2.2(c)(ii). Three of the four Board actions died at the filing gate.

The fourth died at a different gate, and the message printed it plainly: if the petitioning participant cannot obtain support from at least one other EC Decisional Participant during the support period, the rejection process is automatically terminated per Annex D §2.2(d)(ii). One partner, seven days, or nothing.

On 9 June 2026 the Administration closed the file. The support period expired; no notices of support from other Decisional Participants were received; the rejection process for the Standard Bylaws Amendment was automatically terminated. The certificate addressed to John Jeffrey carries the same finding and five signatures — Germán Valdez for the ASO, Jonathan Zuck for ALAC, Alejandra Reynoso for the ccNSO, Jennifer Chung for the GNSO, Nicolás Caballero for the GAC.

Read that signature block for exactly what it is. Each seat certified a procedural outcome. Signature is not assent to the instrument under review, and the certificate does not claim it is.

Two thresholds, and the one that governs is not in hand

Here the record gets interesting in a way that no press release would choose.

ICANN's 2018 rejection actions procedure handbook sets out two support thresholds. A Rejection Action Supported Petition on a Standard Bylaw Amendment needs three or more Decisional Participants, with no more than one objecting. On any other Rejection Action, it needs four or more, again with no more than one objecting. The same handbook describes the machinery around them — a 21-day petition period, a seven-day support period, a community forum period, a 21-day decision period, and the rule that a participant which does not communicate a decision is deemed to have abstained.

The Bylaws page obtained in this review gives the body's composition — a California nonprofit association made up of the ASO, ccNSO, GNSO, ALAC and GAC, each a Decisional Participant — and, in the Article 6.3(e) GAC carve-out, refers to an EC Decision under Annex D §4.1(a) requiring four or more, with the carve-out substituting three or more and no more than one objecting.

The operative §4.1(a) sentence itself did not come back in the page text obtained. So the state of the evidence is this: a 2018 handbook that summarises the Bylaws and predates the 3 July 2026 version obtained, and a cross-reference inside a carve-out. A reader who wants the version-bound governing sentence for a Standard Bylaws Amendment will not find it in these documents, and this article does not supply one by inference.

What the documents do support is arithmetic, and only arithmetic. Five seats. Under a four-or-more rule with at most one objecting, four participants must affirmatively support and at most one may decline. Under a three-or-more rule, two may decline. The documents state a count, not a weighting; the ASO holds one of the five seats; the record records no votes inside the ASO or any other seat.

And neither number was reached. Not three, not four. Zero.

What the ASO actually put on the record

The sequence on the number-resource side is short and unusually explicit. The ASO's 3 June 2026 notice recorded that ALAC, acting as a Decisional Participant, had issued a Rejection Action Petition Notice opposing the amendment, and set out ALAC's stated concerns: that the amendment could further delay accountability reviews, formalise existing delays, widen the gaps between review cycles, and insufficiently address community input from the public comment process. It recorded that the ASO had been asked to consider exercising its rejection powers and had referred the request to the NRO Executive Council.

The ASO's 9 June 2026 letter reports the outcome: following the request, the NRO Executive Council reached out to the RIR communities to ask whether the ASO should support the petition, no input in support was received through that process, and the ASO would not support the petition. The follow-up notice to the RIR community repeats it — "the ASO will not support the Community Rejection Petition" — and discloses the method: consultation through the RIR communities' respective CCG mailing lists, with threads linked for AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC.

That is a documented institutional disposition, and it is all the record gives. "No input in support" is not a tally of five community decisions. It does not distinguish a community that stayed silent, one that abstained, one that could not form a view inside the window, one that opposed the petition outright, or a thread where the argument simply ran out of days. Nor do the documents show the rule by which the Executive Council converted five consultations into one seat's position. The seat spoke; the underlying arithmetic of the canvass is not on the record.

What the count decided, and what it did not

Separate two things that the word "rejection" fuses together.

A support count is an authorization rule. It decides whether a challenge may proceed to a later decision stage. It says nothing about whether the amendment, the budgets or the plans were good, bad, necessary or wasteful. On this record, the Board actions were never rejected and were never collectively endorsed on the merits either. The amendment to Article 27 stands because no supported petition was ever certified, not because five participants pronounced it sound.

Nor should the four tracks be merged into a single zero. Three died because nobody filed a petition — a filing gate. One died because nobody else would support a filed petition — a coalition gate. Same headline, different rule, different institution of last resort.

The certificate's five signatures establish certification of that procedural outcome. They do not, without more text, establish that the five participants agreed on substance. And because the record discloses no reasons from the four non-supporting participants, their judgements cannot be praised or condemned here; the record simply does not contain them.

Where the veto actually lives

Here is our reading, and it is an editorial judgement built on the record above rather than a quotation from any instrument.

A rejection power in this architecture is a counting rule before it is a right. The leverage sits at coalition formation, not at the printed majority. A petitioner must find one partner inside seven days or the process ends before the number that everyone argues about is ever asked for. Any one of the other four seats could have supplied that partner. No single non-supporter was independently dispositive; the block was collective zero. That is a design fact about where a veto lives — in the second signature, not in the final count.

This is not a complaint about the participants and it is not a compliment to the Board. It is the mechanism, stated plainly: the procedure assigns an automatic consequence to a count, so a challenge can fail without any merits vote being held, and the record cannot distinguish a considered refusal from an unanswered question. The gap between those two things is the price of an early gate — and it is a price paid in silence, since nothing in the record requires anyone to explain it.

What would move this from gate to judgement

The operative Annex D §4.1(a) sentence on the current Bylaws, version-bound and complete, would settle which threshold governs a Standard Bylaws Amendment. The five RIR consultation threads would show whether any community recorded a position and what it was. A published rule for how the Executive Council aggregates a canvass into an ASO position would make the seat accountable to a method rather than to a summary sentence. Reasons from the four non-supporting participants would convert a count into a set of decisions.

Each of those is a document, and each would change what this article can say. Until one arrives, the finding is narrower and it is firm: the heavy threshold was never tested because the light one was never met. One partner, seven days, no takers.

The full record behind this briefing, including the four Board actions and the petition window, sits in the BTW directory entry.