Summary

  • An excerpt of the ICANN Bylaws obtained for this review states that, notwithstanding any other provision in the same section, disputes relating to internet numbering resources fall outside the scope of reconsideration.
  • The same excerpt assigns ICANN coordination of top-level IP and autonomous system number allocation, and places number-registry policy with the affected community and related tasks as agreed with the regional registries, while the excerpt obtained contains no recognition procedure.
  • A summary of the Address Supporting Organization site reports that recognition procedures for regional registries sit in a memorandum between ICANN and the Number Resource Organization; that memorandum, the ICP-2 criteria document, the full text of Article 9 and the council’s own operating procedures were not obtained in this review.

Start with the practical question, because it is the reason this document matters. If you hold addresses and you dispute a decision taken about them, the excerpt obtained here places Internet numbering disputes outside ICANN’s reconsideration process, expressly. What the same material does not give you is the process that remains. The rules said to govern recognition of the regional registry concerned appear only in a summary of a memorandum this review did not read, so who decides a recognition question, on what criteria, and with what right of reply is not established by anything read here.

That is the position an operator, the lawyer advising one, or a registry facing a continuity question actually occupies: one route named and closed by words, the next described but not produced. The cost of confusing the two is practical. A party that treats the coordination mandate in Article 9 as an appeal route spends the time it needed to find the process that does apply.

The text that matters arrives with ellipses in it. What was obtained is an excerpt of the ICANN Bylaws page, assembled for this review from the page’s own text rather than read end to end, with omitted passages marked. The stored snapshot carries neither a publisher field nor a publication date, so no effective date, version number or amendment history is established — which matters, because the excerpt’s most consequential sentence is a limitation of scope, and a limitation of scope is only as strong as the text it sits in.

Inside the excerpt, under the heading “ARTICLE 9 ADDRESS SUPPORTING ORGANIZATION”, a mission clause reads that ICANN “(iii) Coordinates the allocation and assignment at the top-most level of Internet Protocol numbers and Autonomous System numbers.” The clause continues that ICANN “(A) provides registration services and open access for global number registries as requested by the Internet Engineering Task Force ... and the Regional Internet Registries ... and (B) facilitates the development of global number registry policies by the affected community and other related tasks as agreed with the RIRs.”

Read quickly, that is the familiar architecture: coordination at the top, policy built by the community that uses the numbers, and a set of related tasks agreed with the registries themselves. Read carefully, it is a division of labour stated at the level of function and never at the level of procedure. The excerpt tells a reader who does what in general terms. It does not tell a reader who decides whether a given regional registry continues to be recognised, against what criteria, on whose initiative, or with what right of reply.

The door that is expressly closed

The second passage in the excerpt is the one an address holder would care about most, and it does not say what the architecture above might lead them to expect. Under a clause numbered 4.2(d), “Notwithstanding any other provision in this Section 4.2, the scope of reconsideration shall exclude the following”, and among the listed exclusions is “(ii) Disputes relating to Internet numbering resources” (ICANN Bylaws page).

Two features of that drafting deserve attention. First, it is an express exclusion rather than an omission. A reader is not left to infer that numbering disputes fall outside reconsideration because nobody thought to list them; the text puts them outside. Second, the opening words tell the reader that the exclusion is designed to hold against the section’s other provisions. Whatever else that section provides, the exclusion is meant to govern.

What follows from that is narrower than it may first appear, and the narrowness is the point. The clause establishes that this route — ICANN’s reconsideration process — is unavailable for a dispute about numbering resources. It does not establish that no forum, process or appeal exists anywhere. Other routes were not examined here, and a reader who treats one closed door as an empty building will misread the document and misjudge their own position.

Where the recognition rulebook is said to sit

For the procedures that govern recognition of regional registries, this review relies on a description rather than a text. A summary of the Address Supporting Organization’s site, obtained for this review, reports that the specific governance of registry recognition and the organisation’s operations are detailed in an Address Supporting Organization memorandum of understanding between ICANN and the Number Resource Organization, which represents the regional registries, and that this memorandum outlines procedures for the recognition of regional registries (ASO site).

That is a summary, not a quotation. No verbatim passage from the page was retained, and the memorandum itself was not obtained. So this account cannot say what the memorandum requires, who applies, what evidence is weighed, who decides, whether a decision can be reviewed, or whether recognition can be withdrawn from a registry that already holds it. Each of those questions remains open, and none of them is answered by the material in hand.

The distinction is not pedantry. A constitutional text that assigns coordination and closes one accountability route, alongside a secondary description that points to a contract for the operative rules, describes a system whose decisive documents sit one layer below the one most readers will find. Whether that layering is sound, anomalous or simply ordinary practice cannot be assessed without the lower layer.

The council in the gap

The entity at the centre of this account is the Address Supporting Organization Address Council, which this publication catalogues as a standard body in the global governance record. The excerpt obtained names the Address Supporting Organization; the excerpt obtained contains no passage describing the council’s composition, its powers or its procedures, and the council’s own published operating procedures were not obtained in this review.

What can be said about the council is therefore documentary. Its existence and its place in the structure are not in doubt. What it may decide about recognition, what it may recommend, and what it must record are not established by anything read here.

What the evidence supports

Three functions are in play — coordination, policy development and recognition — and the material obtained supports different statements about each. Coordination is stated in the excerpt. Policy development by the affected community, with related tasks agreed with the regional registries, is stated in the excerpt. Recognition is reported, at second hand, to be governed by a memorandum that was not read.

The defensible finding is an asymmetry in the record rather than a verdict on any institution. On the material obtained, an address holder who disputes a numbering decision cannot take that dispute to ICANN’s reconsideration process, because the text says so expressly. Where they can take it is a question this review can locate but cannot answer, and the difference between locating a question and answering it is the difference between reporting and guessing.

Sources: ICANN Bylaws page (excerpt with ellipses, retrieved 21 October 2026); Address Supporting Organization site (summary, retrieved 21 October 2026).