Summary

  • The Address Supporting Organization publishes a page titled "ASO Procedures for Empowered Community Powers", and a snapshot of it was retained on 2 November 2026; that page is the one solid piece of institutional evidence this review could hold.
  • The governing principle the page is reported to cite is narrow and consequential: a Decisional Participant Representative must act solely as directed by its Decisional Participant, under processes that participant develops.
  • The decision route the retrieval summary describes runs through the NRO Secretariat and the NRO Executive Council, not through the body named in the page's title.
  • What a registry member still cannot see from the published record is timing, threshold and a dated instance of exercise; the ICANN Bylaws provisions that would fix the clock were not obtained here, and their absence from this article is a retrieval fact rather than a finding about the institution.

A notice lands in a registry's inbox with a title that sounds procedural and a question that is not. It asks the Regional Internet Registry community to consider something called an Empowered Community rejection action. A member reading it wants two things, in this order: who inside the number community would actually decide, and by when. The first is answerable from a published document. The second, on the record assembled here, is not.

That asymmetry is the subject of this article. It is not a scandal, and nothing in the retained material supports reading it as one. It is the ordinary condition of a governance system whose decision architecture is public at one layer and whose operating clock sits at another — and it matters because the difference between those layers is the difference between a right that a member can follow and a right that a member can only be told about.

The entry point is the notice recorded against this subject in the directory. The directory entry for this notice Only for Strategic Circle files it as a registry-type identity in region AN, carries a role card naming a RIPE NCC registry function at a confidence of 0.85, and — to its credit — states its own data gap: registry function, service territory, governance relationships and role boundary all remain to be verified. That card is a directory projection, not an institutional finding, and it is treated as such here. The notice's own text, its date, its stated request and its addressee were not obtained in this review, so no claim is made about what it says.

What was obtained is a different document, and a more revealing one.

What the Empowered Community is, in the words the retrieval reported

The Address Supporting Organization publishes, on its own site, a page titled ASO Procedures for Empowered Community Powers. A snapshot of that page was retained on 2 November 2026. That much is metadata rather than interpretation: the page exists at that address, and the review holds a copy of what the retrieval returned.

The retrieval reported an excerpt from the page, and the provenance of that excerpt matters for how it is used here. It was reported by the retrieval, not read line by line by this author in this session. So it is quoted as reported, and only as reported.

In the wording the retrieval reported, the Empowered Community is "the nonprofit association formed under the laws of the State of California consisting of the ASO, the ccNSO, the GNSO, the ALAC and the GAC".

That single sentence does a lot of structural work, and it is worth slowing down over. Five participants. One of them is the Address Supporting Organization — the body whose procedures page this is. The other four are the country-code names organisation, the generic names organisation, the At-Large Advisory Committee and the Governmental Advisory Committee. A rejection action is therefore not something the number community does alone, and it is not something done to the number community alone. It is a joint instrument, exercised by an association whose members are organisations, each of which has its own internal machinery.

That is the first layer of the answer to "who". The number community's share of an Empowered Community decision is held by the ASO as one of five. The ASO is not the association; it is a participant in it.

The sentence that carries the weight

The second reported sentence is the one that makes this article necessary.

In the same reported wording, the page states that, per the Empowered Community governing principles, Decisional Participant Representatives "must act solely as directed by their Decisional Participant and in accordance with processes developed by their Decisional Participant for the use of the Empowered Community powers".

Read that twice, because both halves bite. A representative does not act on personal judgement; the representative acts solely as directed. And the direction is not free-form: it arrives through processes developed by the participant itself. The architecture is deliberately indirect. The association holds the power; the participant directs its use; the representative carries the direction into the room.

For a registry member, this is simultaneously reassuring and deflating. Reassuring, because it means the person in the room cannot freelance: the representative is a conduit, and the direction has to come from an organisation with a process. Deflating, because it relocates the real question. If the representative merely carries a direction, then everything that matters happens upstream — in the process that produces the direction. And the sentence that binds the representative tells you that such a process must exist. It does not tell you what it is.

That is precisely where a published procedures page either earns its name or does not. A page that establishes the conduit and leaves the upstream process to be discovered elsewhere is a real document, and it is not nothing. It is also not a decision procedure in the sense a member needs, because a member's practical question is not "who carries the direction" but "who forms it, on what trigger, by what majority, and within what window".

The route the retrieval summary describes

Alongside the excerpt, the retrieval returned a summary of the page, and the summary describes a route. The provenance rule for this part is stricter than for the quoted sentences, so it is stated plainly: the following is what the retrieval's summary describes, not the page's own wording, and it is not quoted.

As summarised, the ASO's route for rejection actions runs like this. The NRO Secretariat informs the NRO Executive Council of Board notices or petitions. The Executive Council holds teleconferences to determine whether to accept or support a petition. Decisions are communicated to the RIR communities. ASO Empowered Community representatives act under NRO Executive Council direction.

The same summary attributes to the NRO Executive Council the authority to accept, reject or summarily dismiss petitions.

This is a coherent and, in its own terms, sensible arrangement. A coordinating body's secretariat receives the trigger and routes it to the body's executive; the executive deliberates; the outcome is communicated outward to the registries; the representative in the Empowered Community acts on the direction received. Anyone who has watched inter-registry coordination will recognise the shape. It is the shape of a system that has to produce one position from five organisations that do not share a board.

It is also, structurally, a delegation. The body named in the page's title — the Address Supporting Organization — is not where the summary places the operative decision. The decision sits with the NRO Executive Council. The ASO's representative acts under that council's direction. The ASO Address Council, the standing body most readers would expect to find at the centre of an ASO decision, does not appear in the summary at all.

That absence is worth naming carefully, and only as far as the evidence goes. It is not evidence that the Address Council has no role. It is evidence that the retrieval's summary of this page does not describe one. A summary is a compression, and compressions drop things. What can be said is narrower and still useful: on the material reviewed, the route that a reader would reconstruct from the ASO's own procedures page runs to the NRO Executive Council, and the ASO's Empowered Community representative is bound to that council's direction.

Why "who" is easier than "when"

The summary answers the first question a member asks. It names the actors and orders them: secretariat, executive council, registries, representative. A reader can now point at a body and say: that is where the decision would be taken.

The second question is untouched. Nothing in the retained material fixes a period. Nothing states a quorum, a voting threshold, an abstention rule, or what "summarily dismiss" requires by way of record. Nothing indicates whether the Executive Council's determination is published, minuted, or merely communicated.

This is not a gap the article can fill by inference. Timing rules for a rejection action are exactly the kind of thing that lives in a constitutive instrument — periods for petition and for decision, thresholds for concurrence among participants, requirements for transmission of a notice. Those provisions were not obtained in this review. Three separate retrieval attempts on the ICANN Bylaws rejection-action provisions and the related annex returned nothing usable: two consecutive provider failures followed by a run that reported the retrieval as unable to complete.

Under the retrieval discipline applied to this article, that class was closed rather than retried indefinitely.

So the honest statement is bounded on both sides. The clock is not in the document that was read. The clock is not therefore absent from the system. What a reader can conclude is that the published procedure, on the record reviewed, does not carry the timing rules — which means a member cannot learn them from the page the ASO publishes about its own Empowered Community powers.

That is a smaller claim than it first appears, and a more durable one. Claims that an institution has no deadline, no threshold or no published record are the kind of absolute negatives that a review of this scope cannot earn. Claims about what a specific published page does and does not contain, in a dated snapshot, are checkable by anyone with the URL. The second kind is what this article makes.

What a member can and cannot test

Put the two layers side by side and the practical consequence becomes concrete.

A member can now test the actor chain. Given a Board decision, the member can say: the notice would reach the NRO Secretariat; the Secretariat would inform the NRO Executive Council; the Executive Council would deliberate; the outcome would be communicated to the registries; the ASO's representative would carry the direction. That is a real gain in legibility. Before the page was read, the actor chain was a guess.

A member cannot test the timing chain. Confronted with a claim that a rejection action window opened on a particular date, or that one closed, or that one lapsed for want of a decision, the member has no published reference point from this document. Nor can the member test whether a decision met whatever threshold applies, because the threshold is not stated. Nor, finally, can the member test whether the route has ever been used, because no dated record of an ASO-route exercise was obtained.

That last point deserves emphasis, because it is where analysis most easily slides into accusation. An absence of a dated record in this review is not evidence that no exercise ever happened. It is evidence that this review did not find one. There is a difference between "the record is empty" and "I did not obtain the record", and the whole discipline of this article sits in keeping them apart. What can be said is that the published material reviewed does not, by itself, let an outsider reconstruct an exercise history.

Here the interpretive limit is worth stating as plainly as the finding. What the record supports is a characterisation about disclosure and auditability: the actor chain is visible, the trigger-to-decision chain is not equally visible, and that limits an external reader's ability to test whether a particular action was timely or authorised under the applicable threshold. What the record does not support is any claim about motive, about the lawfulness of the arrangement, or about whether rules exist elsewhere.

A neutral division of labour and a disclosure asymmetry are not mutually exclusive descriptions; the first is about who does what, the second about what an affected reader can verify.

Where "on behalf of" stops

There is a temptation, writing about a delegation like this, to say that the ASO's representative acts on behalf of every registry member. The retained material does not support that sentence, and it is worth explaining why the distinction is not pedantry.

What the material reports is that ASO Empowered Community representatives act under NRO Executive Council direction, and that decisions are communicated to the RIR communities. That establishes a route inside the ASO. It does not establish a mandate running from each individual registry member to the representative. Those are different relationships with different accountabilities: a route can be followed without every member having authorised the traveller.

The correct phrasing is therefore narrower — the representative acts within the ASO route — and the narrower phrasing is actually more useful to a member, because it tells the member what to go and ask about. If the relationship were direct agency, the member's question would be about its own instruction. Because the relationship is a route, the member's question is about the process that generates the direction: where it is written down, who participates, and whether a member's input has any channel into it.

That question is answerable in principle, and it is not answered by the page reviewed here. The page's own reported principle says the processes are "developed by their Decisional Participant". So the ASO is the author of its own process. Whether that process is published, and whether it gives a registry member a way in, is a separate document question — one this review could not settle.

The notice itself, and what it is not

The subject of this article is a notice, and it would be reasonable for a reader to expect the notice's contents here. They are not, and the reason is not coyness.

The notice is listed in the directory record's own evidence basis at its RIPE NCC address, and it is cited in this article only for the bounded statement that no readable text was obtained from it in this review. Its date, its stated request, its addressee and its deadline — if it has one — are all outside what this review established. Several attempts to retrieve it, both as a supplied document and as a search target, produced no readable text.

That has a consequence for how the article must be read. The notice is treated as the entry point the directory records, not as evidence that a rejection action was initiated, supported, declined or decided. A notice requesting consideration is a request. It is not a decision, and the difference is the entire point of a procedure that distinguishes the two.

A reader who wants the notice's actual terms can go to the notice as recorded and read them. This article's contribution is not a substitute for that reading; it is an account of what the surrounding procedure does and does not make checkable.

What the record does establish

Set against the test this article was commissioned to run, the result is partial and worth stating in its own terms.

The negative proposition — that notices circulate to the RIR community with no published ASO decision procedure and no dated record of the ASO considering or casting an Empowered Community decision — does not survive. A procedure is published. It is on the ASO's own site, it describes a route, and it names the bodies that would act. Whatever else is true, the number community's route into an Empowered Community rejection action is documented at the level of actors.

The positive proposition — a published procedure plus a dated public record showing the ASO considering, supporting or declining a specific rejection action — is only half met. The procedure exists. The dated record of exercise was not obtained.

That is the finding, and it is a genuine one rather than a consolation. A governance mechanism that has a published actor chain and no publicly reconstructable exercise history is in a different condition from one with neither. The first can be audited by asking a specific question of a specific body. The second cannot be audited at all. The step this record has taken is the step from opaque to partially legible, and partial legibility is where most institutional accountability actually lives.

The boundary, stated once

The retrieval boundary is a dated fact and belongs in the record rather than in a footnote. Over a single working window on 2 November 2026, the review obtained one source snapshot of institutional substance: the ASO's own procedures page. Three instrument classes were closed after repeated provider failures rather than pursued further — the ICANN Bylaws rejection-action provisions and related annex, the NRO Executive Council's own documentation, and the notice text itself. No NRO Executive Council minute or resolution was obtained. No ASO Address Council resolution or dated action record was obtained.

No Empowered Community Administration notice was obtained. No publication date or version marker was captured for the procedures page, so its currency is unknown here.

The consequence of that boundary is a single-source article, and a single-publisher source at that. The page is the ASO describing its own arrangements. That is a perfectly good thing to read, and it is not independent corroboration of itself. Where the article relies on the page, it says so. Where it relies on a summary rather than wording, it says that too. Where it relies on nothing, it declines to conclude.

What would change the picture

Four developments would move this subject from partially legible to legible, and each is specific enough to watch for.

A dated ASO Address Council or NRO Executive Council record naming a specific rejection action and the decision taken would convert the actor chain into an exercise history. A revision of the ASO procedures page carrying a version marker or date would let the delegation route be read as current text rather than as an undated summary. Any Empowered Community Administration notice fixing petition or decision periods for a live action would supply the clock this review could not obtain.

And any registry-level statement describing how its own member input reaches the ASO's Empowered Community representative would answer the question the reported principle leaves open.

Until one of those appears, the position of an ordinary registry member is this. The route is published. The direction is real. The representative is bound. And the timing — the thing that decides whether a member's view arrives in time to matter — sits in an instrument the member does not hold.

Sources: ASO Procedures for Empowered Community Powers; the notice as recorded in the directory evidence basis; directory entry for this notice Only for Strategic Circle.