The ASO Rejection Petition That Drew Zero Input, and Why That's the System Working

A governance notice that reports nothing happening is easy to skim past. On 9 June 2026 the RIPE NCC published exactly that: a follow-up notice to the RIR community confirming that the Address Supporting Organization would not support a Community Rejection Petition against a recent ICANN Bylaws change. The reason given runs to one sentence. No input in support of the petition was received from the RIR communities. Read that as the whole story and it looks like a non-event. The stakes sit one layer down, in what the silence actually proves.

I sat with that notice longer than its length warrants, because the headline read I keep seeing in operator chat is the wrong one. People treat "zero input, ASO declines" as the accountability mechanism failing, a check on the ICANN Board that nobody bothered to pull. I read it the other way around. For the specific path the ASO sits on, silence is not a failed vote. It is the absence of the affirmative mandate the ASO is structurally required to have before it can act at all. The mechanism behaved as designed, on a change that did not clear the bar of mattering enough.

That distinction is worth getting right, because the next bylaws amendment might be one you actually want stopped. If you have mismodelled how this lever works, you will reach for it too late.

What actually happened, stripped to the timeline

The chain of events in the notice is short, and I want it on the record without embellishment, because the original coverage of this event padded it with figures that have nothing to do with the petition.

On 3 May 2026 the ICANN Board approved a Standard Bylaws Amendment to Article 27, creating a temporary pause-and-reset mechanism for ICANN's Specific Reviews, the periodic organizational audits ICANN runs on itself. On 12 May the ASO Secretariat published a notice telling the RIR community that this approval was subject to the ICANN Empowered Community rejection process, and that during the applicable Rejection Action Petition Period any individual could submit a petition to any Decisional Participant.

The At-Large Advisory Committee (ALAC), acting as a Decisional Participant, then issued a Rejection Action Petition against the proposed addition of Section 27.6, "Timing for Specific Reviews." The ASO subsequently received a request to consider supporting that petition. The NRO Executive Council put the question to the five RIR communities, AFRINIC, APNIC, ARIN, LACNIC, and RIPE NCC, through their respective CCG mailing lists. Nobody wrote back in support. The ASO declined to support the petition.

That is the entire event. No financial barrier, no market forecast, no data-center electricity figure belongs anywhere near it. The story is a procedural reset to ICANN's self-review schedule, met by an address community that looked at it and chose not to expend a rejection.

Why "no input" is a quorum signal, not a consent signal

Here is the modelling error I want to correct. In an ordinary deliberative body, silence is dangerous because a measure passes unless enough members object, so not showing up effectively votes yes. People import that intuition into the Empowered Community and conclude the Board "got away with" the amendment because the address community was asleep.

But the ASO does not sit on a path where it blocks Board actions by default and needs objections to stay quiet. It sits on a path where it can *support a rejection* only when its communities give it an affirmative mandate to do so. The Empowered Community accountability framework that came out of the 2016 IANA stewardship transition deliberately makes rejecting a Board action a high-threshold, multi-participant act rather than a low-threshold veto any single constituency can trigger on a quiet afternoon. The bylaws themselves carry that design philosophy through to adoption. A Standard Bylaws Amendment needs a two-thirds Board supermajority to pass, precisely so that changes are sticky and not easily whipsawed.

So when the NRO Executive Council asks the five communities "should the ASO support this rejection?" and gets nothing back, the wrong reading is "the community consented to the amendment." The accurate one is narrower: no community produced the mandate the ASO would have needed to join the rejection. Those are different claims. The first imputes a position the source never records. The address community did not endorse Section 27.6; it simply did not move to reject it.

The second claim is just the mechanism reporting its own input count. The notice itself is careful on this point. It states only that the ASO will not support the petition. It does not say the amendment is ratified, auto-accepted, or validated by the address community's quiet. Neither should we.

The judgement call operators actually made

There is a more interesting story under the procedure than "nobody cared," and it is one I have sympathy for as someone who watches RIR mailing lists for a living. Community attention is a finite resource. Every consultation that lands on the CCG lists competes with policy proposals, transfer-process changes, charging-scheme debates, and the day-to-day of running address space. Supporting a rejection petition is not free. It asks a community to form a position, articulate it on the record, and spend coordination effort against the ICANN Board.

Against that cost, what was on the table? A timing-and-reset mechanism for ICANN's Specific Reviews. That is genuine ICANN-internal governance plumbing, but it does not touch the number-resource policy that RIR communities are constituted to defend. It does not change allocation rules, transfer policy, RPKI trust anchors, or the relationship between the RIRs and the IANA functions. Read that way, "no input" reads less like apathy and more like a community correctly declining to spend a rejection on a change outside its core mandate.

I think that is defensible, and I would not want to live in a world where the address community reflexively fired a rejection at every Board action it could reach. A check used indiscriminately is a check that gets discounted. The real risk runs the other way, and it is worth naming: a community that has talked itself into "the rejection path never works anyway" will be slow and out of practice the day a Board action genuinely threatens number-resource governance. A lever sits unused at a cost. The lesson of this notice is to keep the triage sharp, not to keep the trigger finger itchy.

Reading the next rejection-period notice

When the next ASO Secretariat notice lands announcing a Board action open to rejection, the useful question is rarely "should someone object" in the abstract. The one that decides things is whether this particular action clears the bar for the address community to spend a mandate. The way I work that out is less a checklist than a short chain of conditions, and it runs in order because each one can stop the process cold.

The first condition is timing. Before anything else, confirm the action is inside its active Rejection Action Petition Period, because outside that window there is no procedural path regardless of merit. The second is routing. A petition goes to a Decisional Participant, and the participants behave differently: ALAC can act on end-user concerns on its own initiative, while the ASO needs an affirmative mandate from the RIR communities. Knowing which door you are knocking on changes who has to assemble what.

The third condition is the one that decides most cases. Does the action touch number-resource policy, IANA functions, RPKI, or the RIR, ICANN relationship? If it does, it sits in the ASO's lane and is worth a position. If it is ICANN-internal plumbing, the silence that met Section 27.6 is probably the right answer again. And running underneath all three is a clock: the cost of forming a community position is real, so the decision has to land before the window closes. A mandate assembled after the period expires is worth nothing.

Walking that chain does not exist to make rejection easier. Its job is to make the *decision* deliberate, so that when the address community does stay silent, the silence is a choice rather than an accident.