Summary

  • A BTW directory record files "About the ICANN ASO Address Council" as an internet registry in jurisdiction AB and asserts registration with RIPE NCC on a single cited evidence link, while its own data-gaps field asks that the registry function, governance relationships and current role boundary be verified.
  • The ICANN bylaws page obtained in this review identifies Article 9 as the Address Supporting Organization and stops at the heading; the provision that would state what the Council may do was not obtained, and three further document classes returned no publisher text.
  • The result is a traceability mismatch, not a contradiction: a designation travelling without a located grant, and a piece that says exactly where the chain breaks instead of filling the gap with a claim.

The record first. The BTW directory entry for About the ICANN ASO Address Council is a handful of field values and one citation, and its brevity is itself information. It files the name as an object of type "registry" and a legal type of "registry". It gives "AB" for headquarters country and "AB" again for registration jurisdiction. It states the known role in nine words: "is an internet registry, registered with RIPE NCC." Its legal-name field repeats the page heading the record was drawn from, including the word "About" — a small detail that says where the name came from.

Behind those fields sits a single evidence link: a RIPE NCC page on the Number Resource Organization Number Council, labelled "Public registry record evidence" and carrying a stated confidence of 0.82 (RIPE NCC NRO NC page). The card's Spanish, French and Chinese versions repeat that same single link rather than adding a second source. Read together, four language versions are one citation written four times, not four corroborations.

Then the field that should travel with the label wherever the label is quoted. The record's own data-gaps entry reads: "Verify About the ICANN ASO Address Council's registry function, service territory, governance relationships, and current registry-listed role boundary." A record that classifies a body and then asks for its function, its relationships and its role boundary to be verified is telling the reader precisely what it does not settle. The 0.82 is the record's stated confidence in its own entry, not a calibrated probability that any part of it is legally correct.

The second record is the opposite shape — long, institutional, and quiet exactly where a reader wants it to speak. The retained snapshot of the ICANN bylaws page, retrieved on 18 October 2026, carries a heading fragment in the page's own words: "ARTICLE 9 ADDRESS SUPPORTING ORGANIZATION ... ARTICLE 11 GENERIC NAMES SUPPORTING ORGANIZATION" (ICANN bylaws page). That fragment identifies which article governs the Address Supporting Organization. It does not reproduce the article.

The provider summary accompanying that snapshot states that the bylaws were amended on 3 July 2026, and states that the Address Council's specific powers and the ASO's role in selecting Board directors sit in the full Article 9 text and related annexes. It also states that those operative provisions were not part of what was obtained. The excerpt is recorded as provider-reported rather than as a full-document read, so three different things are in play here: an article number that was located, an amendment date that was reported, and a set of powers that was neither.

Two records, then, with a matching gap in each. One classifies a body without an instrument. The other identifies an instrument without the provision.

Power claims are usually argued at the top and assumed at the bottom; walking up the chain is more useful. A record exists — satisfied twice. The record attributes a designation — satisfied twice: "internet registry, registered with RIPE NCC", and Article 9 naming the Address Supporting Organization. The governing instrument is located — partly: the bylaws page was located and the summary points to Article 9 and its annexes, while the Address Supporting Organization's own governing documents, including its memorandum of understanding (ASO governing documents), returned no publisher text. An operative clause confers or limits a power — not reached; no provision text was obtained. Actual exercise is separately evidenced — not reached; no selection record, resolution or minutes entry was obtained.

The article stops at the last supported link, and the discipline that follows is mostly about verbs. Records list, file, attribute and name. Instruments grant, authorise, confer, require and limit. Conduct is exercised, appointed, selected and voted. Only the first family applies to anything in the two records above.

Not established here:

  • What the Address Council may do, and whether any instrument confers, limits or merely describes its functions.
  • Whether the Council appoints, nominates or recommends ICANN Board directors, or has no role in their selection.
  • How Council members are selected, by whom, and on what term.
  • Any quorum, voting threshold, decision rule or recall procedure.
  • Whether the Council is a legal person, and under which jurisdiction.
  • Whether the Council and the Address Supporting Organization are the same legal subject, related bodies, or different layers of one arrangement.
  • Whether the single cited RIPE NCC page supports the registration field, since that page's text was not obtained.
  • What "AB" denotes beyond the card's own value, and what legal consequence, if any, follows from it.
  • Whether an operative instrument exists at all; only its non-obtainment in this review is established.

Four status labels carry different weight and should not be used interchangeably. "Not obtained" is a collection boundary — the document was sought and no publisher text was retained. "Not verified" is a corroboration gap — a recorded field whose cited support was not read. "Not established" is the present evidentiary conclusion. "Does not exist" or "has no power" would require affirmative evidence, and none was obtained.

What would move it. A full Article 9 and its annexes expressly assigning a power would let a report state that power, its subject, its limits and its conditions with an exact citation, keeping the ASO and the Council distinct if the text does. The ASO's own memorandum or operating procedures identifying legal status, selection method or decision rules would convert those points from open questions into sourced findings. The cited RIPE NCC page, if obtained and supporting the registration field, would let the article say the field is corroborated by the page it cites — though registration alone would still not establish governance powers.

A dated Board-seat selection record, with a call for nominations, a stated evaluation procedure, a recorded selection and a term, would evidence conduct and leave the authorisation question to be asked separately. A minutes entry or resolution recording a Council decision would do the same. And a document conflicting with either record would turn the finding into a documented inconsistency, which would then be attributed to the named sources rather than asserted generally.

Retrieval, dated and counted. On 18 October 2026 this review made four attempts to obtain institutional documents. One returned retained text — the bylaws page above. Three ended in terminal provider failure: one reporting a persistence failure on the provider side, two reporting an invalid account roster. Three document classes returned no publisher text at all: the Address Supporting Organization's own governing documents including its memorandum of understanding, the organisation's descriptive pages, and a second-publisher description at the RIR/NRO layer.

One text obtained plus three provider failures equals four attempts, and the not-obtained set is those three classes.

What the two records together support is narrower than either appears to promise, and it is still worth stating plainly. A reader who meets the Council's name attached to a decision can now check, in one place, what was recorded about the body, what was reported about its governing article, and what was not obtained. That is the distance between an attribution and an instrument, and it is the whole of the finding here.

All three documents above were accessed or attempted on 18 October 2026.