Summary
- The Empowered Community is five Decisional Participants — the ASO, the ccNSO, the GNSO, the ALAC and the GAC — each entering one position. The Bylaws set the rejection thresholds as counts: three of five for a Standard Bylaw Amendment, four of five for anything else.
- ALAC's petition notice is dated 29 May 2026 and reached the Empowered Community Administration on 1 June 2026. The support period expired at 06:59 UTC on 9 June 2026 with no support from any other participant, and the Administration terminated the process.
- The ASO's own procedure gives its position to the NRO Executive Council, not the Address Council, on a clock timed to a stage the June 2026 process never reached.
This briefing started as a different article
I reserved it to compute a printed vote share: so many votes to start a petition, so many to carry a rejection, and the distance between the ASO's share and each bar. The instrument does not work that way. The ICANN Bylaws, as amended 3 July 2026, do not divide the Empowered Community into percentages of anything. Section 6.1(a) provides that it "shall be a nonprofit association formed under the laws of the State of California consisting of the ASO, the ccNSO (as defined in Section 10.1), the GNSO (as defined in Section 11.1), the ALAC (as defined in Section 12.2(d)(i)) and the GAC (each a 'Decisional Participant' or 'associate,' and collectively, the 'Decisional Participants')" (ICANN Bylaws).
Five institutions. ICANN's glossary says the same in fewer words — five Decisional Participants, the three Supporting Organizations plus the At-Large Advisory Committee and the Governmental Advisory Committee — and attaches no weight to any of them (ICANN acronyms and terms). The arithmetic the record permits is 1 of 5, 3 of 5, 4 of 5. That arithmetic is mine, and labelled as mine, because the Bylaws print only the counts.
Three of five, four of five
The thresholds sit in Annex D. A Rejection Action Supported Petition on a Standard Bylaw Amendment "is supported by three or more Decisional Participants ... and is objected to by no more than one Decisional Participant"; on any other rejection action it "is supported by four or more Decisional Participants" under the same objection limit (Annex D rejection-action text). The Bylaws also carry a carve-out that turns a four-participant requirement into three "with no more than one Decisional Participant objecting" where its conditions apply (ICANN Bylaws). ICANN's own handbook of 6 March 2018 states the same two counts and supplies the sequence around them (rejection actions handbook).
One caveat bears on every threshold above. The Annex D text I read is a reproduction hosted on an ICANN mailing list, not the body of the canonical Bylaws page; that page's table of contents places Article 6 and Annex D in the same instrument, but the fetch returned Article 1 and stopped there (canonical Bylaws page). I did not diff the reproduction against the 3 July 2026 amendment. Its currency is a gap in this record, not a finding about it.
The clock the notice landed inside
Annex D runs four periods in sequence: twenty-one days for the petition, counted from the Rejection Action Board Notification Date; seven days for support; twenty-one days for a Community Forum; twenty-one days for the decision, at the end of which a participant that has not informed the EC Chairs Council "shall be deemed to have abstained" (Annex D).
Now the dates, each from a named document. ICANN's Board approved the Standard Bylaws Amendment adding Section 27.6, "Timing for Specific Reviews", on 3 May 2026, as the ASO's own notice states (ASO notice, 3 June 2026). ALAC's Rejection Action Petition Notice is dated 29 May 2026 and cites Article 25, Section 25.1(f) and Annex D, Article 2, Section 2.2; its text puts the twenty-one-day petition period at 11 May to 1 June 2026 (ALAC petition notice). The Empowered Community Administration records that notice as sent to it on 1 June 2026 (ECA termination notice).
The ASO's notice to the RIR community is dated 3 June 2026. It reports that the ASO "has received a request concerning the ICANN Board-approved Standard Bylaws Amendment to add a new Section 27.6, 'Timing for Specific Reviews,' to the ICANN Bylaws", and that "The NRO EC will review the request taking into account the interests of the RIR communities and the ASO's role within the ICANN Empowered Community in accordance with the applicable ASO procedures for ICANN Empowered Community Rejection Actions powers" (ASO notice).
Mine, from those dates: the request for regional consideration went out two days after the petition period closed and six days before the support period expired (ECA termination notice). The notice therefore opened a consultation inside a seven-day window, not the twenty-one-day one that had just ended.
Who answers for the ASO
The participant is not the decider. The ASO's Procedures for Empowered Community Powers provide that "Upon receipt of notice from another Decisional Participant requesting support for a Rejection Action Petition, the NRO Secretariat will arrange a teleconference for the NRO to determine whether or not to support the petition", and that where "the NRO EC decides to support the petition, then the ASO EC Administration Representative will inform the EC Administration and ICANN of the support" (ASO procedures). The body that decides support, objection or abstention, and that may summarily dismiss a petition, is the NRO Executive Council. The Address Council is not named in that role. The same procedure sets the teleconference at least three days before the ASO's deadline, and places that deadline twenty-one days after the Community Forum.
That is the mismatch worth naming plainly. The ASO wrote its decision clock for the late stage of a rejection action. June 2026 ended at the early stage. The procedure's own decision point was never reached, so no teleconference timed to the forum deadline was ever the operative instrument; the outcome was published six days after the question was asked.
The outcome, recorded as two different absences
Two documents dated 9 June 2026 describe what happened, and they describe different silences.
The ASO's follow-up notice reports that "No input in support of the petition was received from the RIR communities through this process. As a result, and in accordance with the ASO's consideration of Empowered Community matters, the ASO will not support the Community Rejection Petition." It also records that the NRO EC sought RIR community input through the respective CCG mailing lists (ASO follow-up notice). The Empowered Community Administration's notice, dated the same day, reports that "The Rejection Process was terminated as no support from any other Decisional Participants in the Empowered Community were received within the prescribed Rejection Action Petition Support Period that expired at 06:59 UTC on 9 June 2026" (ECA termination notice).
Read them side by side. One records an absence of input from five regional communities. The other records an absence of support from four institutional participants. Neither is a tally. The notices reviewed here print no count of responses, no position for any individual registry or registry community, and no reasoning for the outcome. The ASO's notice carries a date but no time of publication, so whether it preceded the 06:59 UTC expiry is not established from this record.
What a reader can do with this
A rejection action is legible from its own documents if you read three things in order: the count in the clause, the stage the clock is in, and the sentence that records the outcome. The first tells you that a single participant cannot carry anything. The second tells you whether the consultation you are reading about happened at the stage its own procedure was built for. The third tells you whether you are looking at a decision or at an absence.
For the next such notice, that reading yields specific questions with answers that can be published. Does the notice print the support deadline, or only the date it was issued? Does the deciding body publish a count of the input it received on each mailing list? Does the outcome record name a decision, or only state that no input arrived? None of those questions accuses anyone of anything. They are the difference between a record that can be audited later and one that cannot.
The notice itself sits in the directory as Notice to the RIR Community: Request for ASO Consideration of ICANN Empowered Community Rejection Action, published by the Address Supporting Organization.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






