Summary
- The only instrument the Empowered Community Administration (ECA) issued on 3 July 2026 certifies approval, not refusal: under Annex D Section 1.4(b) of the ICANN Bylaws, it certifies that ASO, ALAC, ccNSO and GNSO approved the Fundamental Bylaws Amendments to Article 17 and Article 18, Section 18.2(b), proposed in Board resolutions 2026.05.03.11 and 2026.05.03.12 of 3 May 2026.
- The ALAC Rejection Action Petition — against the Standard Bylaws Amendment adding Section 27.6, "Timing for Specific Reviews" — was never granted. On 9 June 2026 the ECA certified, under Annex D Section 2.2(d)(ii), that the Rejection Process "has been terminated" because no other Decisional Participant supported it before the support period expired at 06:59 UTC on 9 June 2026.
- The refusals are dated and named: ccNSO notified ALAC on 7 June 2026 that its Council "decided NOT to support the Rejection Action Petition"; the ASO notified ALAC on 9 June 2026 that the NRO Executive Council consulted the RIR communities via the CCG mailing lists, that no input in support was received from the RIR communities, and that the ASO would not support the petition.
- The same window produced an asymmetric record: a Board-initiated amendment passed with four supports and one abstention (the GAC abstained on 2 July 2026), while a community-initiated rejection died with zero second participants. The rejection power remains formally alive but is conditional — it depends on recruiting at least one additional Decisional Participant inside a fixed support window.
- AFRINIC's documented connection is structural, not nominal: the ASO's refusal notice records a consultation of the RIR communities that drew no supporting input, and the NRO/ASO notices were re-published on the AFRINIC-Announce list. AFRINIC is not named in the operative text of any located instrument.
The instrument that certified a failure
Start with the operative words of the 9 June 2026 letter, because they are the decisive text. Pursuant to Section 2.2(d)(ii) of Annex D of the ICANN Bylaws, the Empowered Community Administration wrote that it "hereby certifies that the Rejection Process relating to the Empowered Community's consideration of the Standard Bylaws Amendment to Article 27 of the ICANN Bylaws has been terminated." ([ECA to the ICANN Secretary, 9 June 2026 — https://itp.cdn.icann.org/en/files/correspondence/eca-to-jeffrey-09-06-2026-en.pdf]) The certificate then states the mechanism: ALAC's Rejection Action Petition Notice was sent to the ECA on 1 June 2026, and "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."
Three features of that sentence matter. First, the deciding body certified the failure itself — this is not a rival community's characterization of an outcome, but the administration's own memorialization that the required support never arrived. Second, the operative effect is termination, not adjudication: nobody ruled the petition wrong on the merits. The instrument records a procedural death for want of a second signature. Third, the window is fixed and short: a support period that opened on 1 June and closed at 06:59 UTC on 9 June 2026 gave every other Decisional Participant roughly one week to co-sign.
Two of them declined in writing inside that window. On 7 June 2026 the ccNSO Council notified ALAC that it "decided NOT to support the Rejection Action Petition" after a special Council meeting that considered ccTLD community comments. ([ccNSO to ALAC, 7 June 2026 — https://itp.cdn.icann.org/en/files/correspondence/ccnso-to-alac-07-06-2026-en.pdf]) On 9 June 2026 the ASO notified ALAC that the NRO Executive Council had consulted the RIR communities through the CCG mailing lists, that no input in support of the petition had been received from the RIR communities, and that the ASO would not support it. ([ASO to ALAC, 9 June 2026 — https://itp.cdn.icann.org/en/files/correspondence/aso-to-alac-09-06-2026-en.pdf]) The petition's subject was narrow and technical: the Standard Bylaws Amendment adding Section 27.6, "Timing for Specific Reviews," whose structure — as the ccNSO Chair's later confirming letter of 3 July 2026 records — provides for a 12-month resumption and a maximum 24-month pause of specific reviews.
The instrument that certified a success, eight days later
Now place beside it the certificate issued on 3 July 2026 — the only ECA letter of that date located on the public record. Under Section 1.4(b) of Annex D, the ECA certified "that the following Decisional Participants of the Empowered Community have approved the Fundamental Bylaws Amendments to Article 17 and Article 18, Section 18.2(b), proposed by the ICANN Board of Directors in their Resolutions 2026.05.03.11 and 2026.05.03.12, adopted at the Board's meeting held on 3 May 2026: Address Supporting Organization; At-Large Advisory Committee; Country Code Names Supporting Organization; Generic Names Supporting Organization." ([ECA to the ICANN Secretary, 3 July 2026 — https://itp.cdn.icann.org/en/files/correspondence/eca-to-jeffrey-03-07-2026-en.pdf]) The letter requests posting on the ICANN website; ICANN's correspondence index dates its publication at 7 July 2026. ([ICANN Empowered Community correspondence index — https://www.icann.org/en/correspondence/empowered-community]) An ECAdmin staff notice records that the Approval Action Decision Period expired at 23:59 PDT on 2 July 2026 with the threshold met — four in support, one abstention, the GAC having abstained on 2 July 2026. (ECAdmin notice, July 2026; correspondence index)
Read together, the two certificates describe two tracks through the same institution in one eight-week span. On the approval track, a Board-initiated amendment gathered four of five Decisional Participants, and a single abstention was structurally irrelevant because the threshold counts supports. On the rejection track, a community-initiated petition needed at least one additional participant beyond its sponsor and received none. Nothing in the operative text of either instrument suggests the outcomes were co-determined; they are independent instruments about independent amendments.
But the juxtaposition is the finding: in the same quarter, the approval path closed with a comfortable bloc while the rejection path closed with zero coalition partners.
What the refusals did and did not say
The precision of the negative record matters for anyone assessing the rejection power's usability. The ASO's notice does not argue the merits of Section 27.6; it records a consultation that produced no supporting input and a consequent refusal. The ccNSO's notice records a Council decision, not a reasoned opinion. Neither refusal is a merits position on any other instrument — and the same two organizations, ASO and ccNSO, appear as approving participants in the 3 July 2026 certificate. Non-support on one track cannot be transposed into approval or opposition on another; each instrument speaks only to its own subject.
The GAC's abstention on the Articles 17/18 amendments invites the same discipline in the other direction. An abstention certified in a staff notice is a recorded non-position; it neither delayed the threshold nor supplies a reason. The located operative text gives no reasons for any of the abstentions or non-supports, which is itself part of the record: the deciding bodies memorialized outcomes without memorializing motives.
AFRINIC's position in this record
AFRINIC, the regional internet registry for Africa, is not named in the operative text of any located instrument. Its documented connection runs through two channels. Structurally, it belongs to the ASO — the Address Supporting Organization, whose Decisional Participant role is precisely the one that declined ALAC's petition after consulting the RIR communities. Procedurally, the NRO/ASO notices about the rejection process were re-published on the AFRINIC-Announce list ([AFRINIC-Announce — https://lists.afrinic.net/pipermail/announce/2026/002574.html]), which is where the region's resource members would have seen the consultation and its outcome. That means the RIR communities — including AFRINIC's — had a documented opportunity to supply supporting input for the petition, and the ASO's certificate records that none arrived.
For an AFRINIC member reading this record, the practical question is not whether AFRINIC could have unilaterally changed the outcome — it could not; the ASO acts as the Decisional Participant, and its refusal was collective — but whether the absence of any supporting input from the RIR communities was a considered regional position or a default. The instruments do not say. What they do establish is that the consultation happened on the CCG mailing lists, that it produced silence, and that the silence was recorded as a reason for refusal.
The conditional character of the rejection power
The certified record supports one structural conclusion. The Empowered Community's rejection power is a coalition remedy with a clock: a single Decisional Participant cannot activate it, the support window is measured in days, and the deciding body itself certifies the outcome — including a failure to activate. As of the located instruments of June–July 2026, the power remains formally intact but has demonstrated its conditional character in practice: when ALAC invoked it alone, ccNSO declined, the ASO declined after an unproductive consultation of the RIR communities, and the process terminated on schedule.
In the same period, the approval path ran to completion with four participants and one abstention.
Whether that asymmetry reflects the design of the procedures, the relative urgency of the two amendments, or the politics of the moment cannot be determined from the operative text. The certificates record what was decided; they do not record why. Any judgement about the health of the Empowered Community's check on the ICANN Board must therefore rest on the plain fact of the two certified outcomes — one coalition assembled, one coalition never formed — and on what future instruments show about whether the rejection power can ever find a second signature when it matters.
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance
