Summary

  • The Address Supporting Organization published a follow-up notice to the RIR community stating that it will not support the At-Large Advisory Committee's Empowered Community Rejection Action Petition against a Board-approved Standard Bylaws Amendment that would add Section 27.6, "Timing for Specific Reviews", to the ICANN Bylaws.
  • The notice names the consultation channel — the NRO Executive Council reached out to the RIR communities through their respective CCG mailing lists — and reports the result as one aggregate sentence: no input in support of the petition was received from the RIR communities through that process.
  • The ASO's own published procedures, as reported in the retrieval used here, give the NRO Executive Council the decision whether to accept or reject a petition, record authority to dismiss petitions that are baseless, vexatious or redundant, and assign the NRO Secretariat a duty to inform the RIR communities of the final decision. The text obtained here reports the support outcome without stating whether the peer request was handled under that menu, or how the announced considerations were applied.

The gap is documentary. The notice announces a decision in the future tense a press office uses when the matter is already settled, and the pipeline that carried the request worked. What the public record does not carry is the formal classification, the response denominator, and the reasoning that tied the outcome to the criterion the council had announced.

A notice that reports an outcome

The document at the centre of this story is not a resolution, a minute or a determination. It is a notice, published by the Address Supporting Organization on its own site, addressed to the regional internet registry community, and titled as a follow-up (ASO follow-up notice to the RIR community). Four sentences of it do the substantive work.

The first identifies the petitioner and the instrument. "Following that notification, the At-Large Advisory Committee (ALAC), acting as an ICANN Empowered Community Decisional Participant, issued a Rejection Action Petition concerning the proposed Standard Bylaws Amendment to add Section 27.6, 'Timing for Specific Reviews,' to the ICANN Bylaws" (ASO follow-up notice). The second places the ASO on the receiving side of that flow: "The ASO subsequently received a request to consider supporting the Community Rejection Petition." The third describes what was done with the request — the NRO Executive Council "reached out to the RIR communities through the respective CCG mailing lists to seek input on whether the ASO should support the Community Rejection Petition." The fourth supplies the result and the conclusion: "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."

That is a complete account of what happened to the request in the ordinary sense of a news report. A body was asked; it put the question to its constituents; it recorded no input in support; the body declined. The same outcome reached the petitioner in correspondence filed in ICANN's public repository under a file name that pairs the ASO with the ALAC and carries the date 9 June 2026 (ASO correspondence to ALAC). The extracted text of that letter is visibly mangled by the retrieval, so it is not quoted here for content; the notice carries the same sentence independently.

What the notice does not contain is equally specific. There is no tally. No registry is named as having responded, in favour or against. No quoted comment appears. Nothing states whether the NRO Executive Council treated the request as accepted, as rejected, or as dismissed on one of the grounds its procedures contemplate. The words "no input in support" are doing a great deal of work in a single clause.

What the ASO's own procedure says a decision looks like

The reason that omission matters is that the ASO has published what it thinks the shape of this process is. Its procedures page for ICANN Empowered Community powers — the two organisations' own published account of the process — describes rejection actions as "initiated by the community via petition to one of the Empowered Community Decisional Participants," and as producing a Community Forum "if supported by a second Decision Participant," with the underlying Board action void if the Empowered Community ultimately approves the petition (ASO procedures for ICANN Empowered Community powers).

The same page, as reported in the retrieval used here, sets out a decision function with more structure than the notice displays. The NRO Executive Council, sitting as the ASO's decisional body for these purposes, decides whether to accept or reject a petition, and holds authority to dismiss petitions that are baseless, vexatious or redundant. Acceptance is described as producing outward consequences: the council informs the Empowered Community Administration and ICANN, and requests support from other Decisional Participants.

And the secretariat is given a continuing information duty — informing the RIR communities of notices, of the receipt of petitions, and of "the final decision of the ASO regarding support for or objection to the rejection."

Read those two documents against each other and a quiet structural fact appears. The procedure contemplates a decision with a nameable disposition. The notice reports an outcome with no disposition. Both can be true at once: a request can be declined in substance while its procedural label is left unstated. But the second sentence of that pair is the one a reader outside the NRO Executive Council cannot reconstruct from the public record.

A second entrance the published procedure does not describe

There is a second seam between the procedure and the notice, and it is visible in the prepositions.

The procedure describes the entry point as a petition reaching a Decisional Participant — the community knocking, the participant answering. The June matter arrived by a different route. The ALAC, itself an Empowered Community Decisional Participant, issued the petition notice; the ASO, a peer participant, was then "asked to consider exercising its rejection powers" (NRO notice to the RIR community). The NRO's own notice describes the sequence plainly, and adds that its Executive Council "will review the request taking into account the interests of the RIR communities and the ASO's role within the ICANN Empowered Community."

That announced criterion is worth pausing on, because it is the only published statement of the standard applied. It is not a substantive test of whether Section 27.6 would in fact delay specific reviews. It is a compound test — the interests of five communities, plus the institutional role of the ASO inside the Empowered Community. A criterion that broad is not wrong. It is, however, not externally reviewable on the record obtained here unless the deciding body later explains how the two limbs were weighed. The follow-up notice does not do that.

So the obtained record supports a narrow and useful observation. The ASO's published procedure describes one entrance to a rejection action, the June matter used a different one, and the text of the procedure retained in this review does not describe the participant-to-participant request that actually occurred. On the text obtained here, a participant who wants to know how a peer's request will be handled by the ASO cannot read the route off the published procedure. The missing element is an implementation detail rather than an unauthorised path.

Zero is not a finding unless someone counts it

"No input in support of the petition was received from the RIR communities through this process" is a precise sentence about one thing and a silent sentence about several others.

It is precise about the direction of the input. Support, specifically, was absent. It says nothing about input that opposed the petition, input that was equivocal, or input that simply asked questions. A community that answered "we have no position" and a community that answered "we oppose this petition" are indistinguishable in that sentence — and so, for that matter, is a community that never answered.

The obvious response is that a consultation result is a result either way, and that the ASO is entitled to summarise. True. But the summary is the only artefact the five communities and everyone else get. A governance practitioner who wants to know whether the RIR community's silence reflected agreement with the ALAC's stated concerns about review timing, indifference, or simple non-engagement cannot find out. Each of those readings supports a different conclusion about whether the Empowered Community's rejection threshold is doing real work.

There is a sharper version of the same point. The ASO's procedures assign the secretariat the job of informing the RIR communities of "the final decision of the ASO regarding support for or objection to the rejection." The notice informs them. The duty is discharged. Whether it is discharged in a way that lets those communities audit their own representative is a separate question, and the answer turns on counts and reasons the notice does not carry.

What closing the gap would cost

The burden appears modest, which is what makes the omission interesting rather than scandalous.

As a recommendation rather than an existing rule, three additions would convert the notice from an outcome report into a decision record. First, the disposition: whether the request was accepted, rejected, or dismissed, and on which of the procedural grounds the ASO publishes. Second, the response count per community — even at the level of "five lists asked, two replies, none in support" — which would let a reader distinguish silence from opposition. Third, a short statement of reasons tying the outcome to the criterion the NRO Executive Council announced before it decided.

None of that requires new procedure, new authority or a longer consultation. The NRO Secretariat already holds both the duty and the raw material. What it does require is a set of small institutional decisions — what counts as a response unit, what may be published from an open mailing list, and who signs off on the text.

The argument for spending it is not transparency for its own sake. It is that the rejection mechanism is a shared instrument among five Decisional Participants, and each of them will one day be the petitioner asking a peer for support. A participant deciding whether to spend the political capital of a petition needs to know how its peers have handled the last one. A one-line outcome is not a precedent anyone can reason from. A disposition, a count and a reason is.

What the record obtained here does not establish

Several things a reader might expect are missing from this review's evidence, and their absence is a boundary rather than a finding.

The follow-up notice as obtained carries no date inside its text and no approval date for the underlying bylaws amendment; the article therefore does not date either event, and the 9 June 2026 reference rests on a file name rather than a dateline. The ASO Secretariat's earlier notice of 12 May 2026, referenced inside the follow-up notice, and the CCG mailing-list threads for the five communities were attempted and not obtained in this review. What the individual registries were asked, what they answered, and whether anything arrived that the summary does not reflect cannot be stated from the material assembled here.

Nor does anything obtained establish that the NRO Executive Council failed to record a disposition internally, that the announced considerations were never applied, or that anything was deliberately withheld; only that the public artefact does not show them.

The ASO's directory entry for this notice is maintained at the BTW directory record Only for Strategic Circle.