Summary

  • The ICANN Board approved the ICANN FY27–31 Operating and Financial Plan, the FY27 Operating Plan and Budget, the IANA FY27 Operating Plan and Budget and a Standard Bylaws Amendment to Article 27 at its regular meeting on 3 May 2026, according to ICANN's record of the process — decisions that opened a fixed period in which anyone could ask a Decisional Participant to reject them.
  • The ASO community's notice to the RIR community put the close of the Rejection Action Petition Period at 1 June 2026, 06:59 UTC. The FY27 rejection action was then recorded as expired and the plans took effect as adopted; a separate petition against the Article 27 amendment was not supported by the ASO, a decision announced on 9 June 2026.

The decisions that started the clock

The Board's 3 May 2026 meeting produced four outcomes on one day: the ICANN FY27–31 Operating and Financial Plan, the ICANN FY27 Operating Plan and Budget, the IANA FY27 Operating Plan and Budget, and the Standard Bylaws Amendment. The same record indicates that the plans were scheduled to take effect on 1 July 2026 provided no Empowered Community rejection process was pending. That single condition is what turned a budget approval into a timed procedure.

The notice to the RIR community is where the procedure became public. The ASO's notice record describes a Rejection Action Petition Period covering both the standard bylaws amendment and the FY27 plans, closing on 1 June 2026 at 06:59 UTC, with petitions fileable with the ASO secretariat. The window is short, fixed and public, and nothing in it requires a petitioner to be a member of anything.

Who actually decides

A petition filed with the ASO secretariat commits the ASO to nothing. Under the procedure as described in the address community's own material, the Chair of the NRO — who also chairs the ASO — acts as the Empowered Community Decisional Participant Representative and acts on the consensus of all five NRO Executive Council members. That procedure account makes the internal gate explicit: the five regional internet registries must agree before the ASO accepts a petition, so any one of them can prevent the ASO from moving at all.

The consequence is that the effective decision point is not the petition form, the secretariat inbox or the calendar. It is a consensus conversation inside the NRO Executive Council, informed by whatever the RIR communities say when they are asked.

What a successful rejection would require

Even an accepted petition is not a rejection. The described procedure sets out a sequence: a 21-day petition period, a seven-day window for a second Decisional Participant to endorse, a Community Forum convened within 21 days, and a 21-day voting period. The thresholds differ by subject. To reject a standard bylaws amendment, at least three Decisional Participants must support the action with no more than one objecting. For other rejection actions — budgets and operating plans among them — four or more must support, again with no more than one objecting. If that support is absent, the challenged decision simply proceeds.

Two features of the arithmetic deserve emphasis. First, the ASO is one participant among several, so an ASO decision to accept a petition is a step in building a coalition, not an outcome. Second, the "no more than one objecting" limit means the instrument is designed for near-consensus conditions. Combined with the five-member consensus rule inside the NRO EC, a challenge can be extinguished twice over before any vote is counted.

The amendment the ASO declined to challenge

The second live matter was the amendment itself. The At-Large Advisory Committee issued a Rejection Action Petition Notice opposing the proposed addition of Section 27.6, citing further delays to important accountability reviews, the formalisation of existing delays, excessive gaps between review cycles and insufficient consideration of community input. The amendment, as described in the same material, creates a Transition Article that pauses and resets the obligation to initiate Specific Reviews, with an initial 12-month pause extendable to 24 months, reporting obligations on the Reviews Cross Community Group, and measures aimed at preventing overlapping reviews if they restart.

The NRO Executive Council, acting for the ASO, asked the RIR communities whether to support that petition. No input in favour arrived. The ASO therefore declined to support the rejection action, and its announcement of that decision to the Empowered Community Administration is dated 9 June 2026. Precision matters here: this was a decision not to challenge a bylaws amendment, and it is a different matter from the FY27 budget rejection action that expired on 2 June.

The Article 27 amendment is also the more consequential of the two subjects for accountability watchers, because it changes the timetable of the reviews meant to test ICANN's own performance. An instrument designed to let the community block a Board decision was pointed at exactly that kind of change, and it was not used.

What the record does not show

Several things that would settle the analysis are not in the public record retrieved here. No petition text, no filer identity and no threshold count for the FY27 rejection action were available. The 2 June letter is described as recording expiry — bookkeeping about the calendar, not a finding that a petition was inadequate or that a decision was endorsed on the merits. Nor was an NRO Executive Council deliberation record or a tally of RIR community responses retrieved; the statement that no supportive input was received is the ASO's own account and is reported here as such.

This briefing therefore rests on the published notices and on descriptions of the governing procedure rather than on direct inspection of the Bylaws annex or of the letters themselves. Exact article numbers and quoted wording should be confirmed against the Bylaws and the underlying correspondence.

There is also an interpretive gap no document closes. Whether the lapses reflect community acquiescence, procedural failure, or simply the absence of organised opposition is not resolved by the record. A rejection action that expires looks identical on paper in all three cases.

What would show the check is real

Three observable conditions would move this from a formal right to a demonstrated constraint. The first is a rejection action that reaches a Community Forum, or at least a recorded vote. The second is publication of petition counts and of the identity of supporting Decisional Participants, which would make coalition arithmetic auditable rather than inferred. The third is an NRO Executive Council that publishes its reasoning when it declines a petition, alongside a documented record of the RIR community consultation it ran. Until one of those appears, the FY27 episode supports a narrower finding: the mechanism exists, it was invoked, and it did not change an ICANN Board outcome. The directory entry for the notice is the anchor document for that finding.