Summary

  • The Address Supporting Organization's website lists three responsibilities for its Address Council: a role in the global policy development process, defining procedures for the selection of individuals to serve on ICANN bodies, and participating in the ICANN Empowered Community.
  • The middle duty is worded as procedure-writing, not as appointment. A provider summary of the same page ties that duty to the ICANN Board directorship reported as Seat 9, but the seat does not appear in the excerpt retained for this review.
  • The ICANN Bylaws text that would settle the seat, the Council's composition and the appointment route was not obtained in this review: two attempts failed on 2 November 2026. That is a fact about this review, not a finding that the instrument is missing.

Three items, and the one carrying weight

The page opens with a heading and a list. Here is the list as it was retained from the Address Supporting Organization's site:

Our Responsibilities

  1. Undertaking a role in the global policy development process (GPDP)
  2. Defining procedures for the selection of individuals to serve on ICANN bodies
  3. Participating in the ICANN Empowered Community

Read the verbs and the asymmetry is immediate. Two of the three describe presence: the Council takes a role in policy development, and it participates in the Empowered Community. The middle item describes production. Somebody has to write down how people get chosen for other institutions, and this page says that somebody is the Address Council.

That is a more consequential sentence than it looks, and it is also a thinner one than a reader might expect. A list of responsibilities tells you what a body is for. It does not tell you who nominates, who votes, who signs, how many positions exist, how a candidacy is judged, or what happens when the outcome is contested. Those are instrument questions, and instruments are where accountability lives.

'Defining procedures' is not the same as choosing

My reading of the middle item — and I label it as a reading, because the page does not characterise the duty this way — is that it is procedural. The Council is described as defining the procedures for selection, not as making the selection. Those are different jobs with different paper trails. The first produces rules; the second produces an officeholder.

Grammar, however, cannot carry a claim about institutional power, and I will not pretend it can. The phrase supports a procedural reading; it does not establish that the Council never nominates, never selects, or never does both under a provision nobody has shown me. What it does establish is narrower and still useful: the published mandate itself puts the Council's influence at the point where rules are designed, and it leaves the appointment mechanics to a document the page does not reproduce.

Coordination has a paper trail; authority needs an instrument

The second retained source is the Number Resource Organization, which describes its own purpose in its site like this:

To actively contribute to an open, stable and secure internet, through:

  • Providing and promoting a coordinated Internet number registry system
  • Being an authoritative voice on the multi-stakeholder model and bottom-up policy process in Internet governance
  • Coordinating and supporting joint activities of the RIRs

Note the vocabulary. The coordinating body claims an authoritative voice for itself, in its own words, on the multi-stakeholder model and the bottom-up policy process. The Council's page, by contrast, describes duties. That difference is worth holding onto, because coordination, contract and public authority are three different things and institutions tend to blur them when the blur is flattering.

A provider summary of the same NRO page goes further than the excerpt: it describes the NRO as the coordinating body for the five Regional Internet Registries, and as the vehicle through which the Address Supporting Organization interacts with ICANN. Neither the count nor the vehicle relationship appears in the retained text, so both travel here as reported rather than confirmed. They are plausible, they are consistent with the excerpt's language about coordinating and supporting joint RIR activities, and they are still summary statements.

The seat arrives as a summary

The most consequential sentence in the material is not in either verbatim excerpt. A provider summary of the Address Supporting Organization's page states that the selection power in that responsibilities list includes selection of the Director for ICANN Board Seat 9.

A seat number does something a duty list cannot: it converts a procedural phrase into a consequence. Fifteen or so people in a committee room writing eligibility rules is an administrative fact. The same committee writing the rules by which a voting director of ICANN's board is chosen is a governance fact, and readers are entitled to check it against the instrument that creates it.

They cannot check it here. The seat attribution sits in a summary of the page, not in the excerpt retained from the page, and a summary of a document is derivative of that document rather than independent corroboration of it. Until the governing text is read, Seat 9 remains reported. That is not a scandal; it is a citation problem, and citation problems are solved by documents.

Two attempts, one boundary

The ICANN Bylaws text governing the Address Supporting Organization was not obtained in this review. Two attempts on 2 November 2026 both failed: the first returned a service-unavailable condition with an unknown outcome at 20:52Z, and the second returned a permission denial at 20:53Z.

I state the boundary plainly because it changes what this article can assert. The instrument that would settle the seat, the composition of the Council and the appointment route is not in hand. Nothing in these two failures establishes that the text is unpublished, unfindable or concealed; it establishes that this review did not reach it, and that the article therefore stops at the edge of what it can show.

What an address holder can actually audit

Here is the practical version, and it is my reading rather than a legal finding. If your address space depends on policies produced through the global policy development process, and if recognition questions sit where the provider summary says they sit, then the surface you can inspect is a procedure. Not a person, not a ballot, not a term sheet — a procedure.

Procedures are auditable, but only through specific furniture: the source of authority, who drafts, who is eligible, in what order decisions are taken, what thresholds apply, what is recorded, who must recuse, who may review, how an appointment is undone, and where a challenge goes. The three-item list supplies none of that furniture, and this review could not reach the instrument that presumably does.

The same summary adds that governance of Regional Internet Registry recognition is linked to the ICP-2 document, which the Council is described as currently updating. Treat that as reported too. If it is accurate, one body is drafting the criteria by which registries are judged and also drafting the procedures by which individuals are chosen for other institutions. That would be a notable concentration of rule-writing, and the interesting question would not be who casts a vote — it would be who drafts the criteria that decide which candidacies and which registries are even arguable.

That is a conditional, and I am keeping it conditional. The narrow point does not need the conditional: a reader relying on the retained record cannot inspect the governing link that would test the consequential claim. The broader claim — that no reader anywhere can inspect it — is not supportable from two failed attempts, and I am not making it.

What would change this reading

Four outcomes would move the analysis, and each is checkable by document rather than by inference.

If the applicable bylaws confirm that the Council selects the Director for Board Seat 9, the summary is substantiated and the excerpt's silence is a matter of documentation layering rather than anything else.

If the bylaws assign the Council only to define a procedure while another actor nominates, selects or appoints, then the summary is shorthand — the kind of compression that turns a rule-writer into an appointing body in a single clause.

If the complete, same-version page carried the seat detail outside the excerpt retained here, the asymmetry is a retention problem, and the fix is a fuller snapshot rather than a revised thesis.

And if the operative procedure names its decision-makers, publishes its records, sets out conflict rules, review and removal, then procedural accountability becomes something to evaluate on the merits instead of something to look for.

The honest sentence available today is short. The institution says the Council defines procedures for selecting individuals to serve on ICANN bodies. A provider summary links that function to ICANN Board Seat 9. The governing bylaws were not obtained in this review, so the seat, the Council's composition and whether the Council appoints, nominates, selects or only writes the rule remain unverified.

A consequential procedure is not self-authenticating. It borrows nothing from the confidence of the institution that publishes a duty list; it has to show its chain from authority to rule to decision to record to remedy. Until that chain is shown, the right posture toward a three-item mandate is neither suspicion nor deference. It is a request for the instrument — and the record of who supplied it. The Address Supporting Organization Address Council Only for Strategic Circle is the entry this reading belongs to; the entry means something different the day that document is on the table.