Summary

  • ICP-2, accepted on 4 June 2001, assigns the approval of new RIRs to ICANN, declares all ten criteria essential, and contains no vote or consent by an existing registry in the retrieved text.
  • The two-thirds registry gate appears only in the 1 September 2026 recommended draft, whose amendment clause already requires unanimous agreement of ICANN and the RIRs.

Read the sentence, not the debate

"It is the responsibility of ICANN to approve the establishment of new RIRs." That is the operative line of ICP-2 as published. The same text calls the criteria "the minimum guidelines needed when evaluating applications", numbers them one to ten, and then removes any ranking: the numbering "is not significant" and "all criteria are considered essential". The support test asks for a "very substantial majority" of ISPs and LIRs in the region — a phrase about an applicant's standing in its own region, not about what other registries think. No existing registry casts a vote or grants a consent anywhere in the retrieved text.

The provenance is equally explicit. ICP-2 records that it was developed through ICANN's Address Supporting Organization "with the assistance of APNIC, ARIN, and RIPE NCC" and recommended by the ASO Address Council. The 24 April 2001 transmittal shows what recommendation meant in practice: a letter from the Address Council to Vint Cerf and Stuart Lynn, signed by Hans Petter Holen as Chair "on behalf of the ASO Address Council", asking the Board to adopt the document as the "Requirements and policies for the approval of additional RIRs" under paragraph 9 of the ASO Memorandum of Understanding, and to authorise ICANN staff "to conduct the evaluation of new RIR applications for final Board approval".

Four verbs, four actors. The Council recommends. The Board adopts. Staff evaluate. The Board approves. A signature is not a decision.

Where the gate came from

The replacement begins with unanimity. Version 2, dated 28 August 2025 and labelled DRAFT, routes a candidate's written Proposal for Recognition to both the RIRs and ICANN; each registry assesses independently and publishes its recommendation; a unanimous recommendation is required for referral, and anything short of unanimity is deemed rejected, subject to a Recognition Review and a narrow path back for a single dissenting registry.

Version 3, published 1 September 2026 and labelled FINAL DRAFT under the title "ASO AC Recommended Draft RIR Governance Document", keeps the architecture and changes the arithmetic. A candidate still files with the registries and with ICANN, and both must publish notice of receipt. Each registry still assesses independently, may conduct due diligence, and sends ICANN a Recognition Assessment with a recommendation, the questions and answers, and a statement of actual, potential or perceived interests. ICANN still decides, still issues a Notice of Decision with reasons, and on approval still issues a Notice of Pending Recognition with a Transition Plan.

Then Article 3.7, in its own words: "ICANN shall have no power to Recognize a Candidate RIR unless it has received a Proposal to do so that is supported by at least two-thirds of the RIRs submitting Recognition Assessments."

The denominator is the story

Read the last four words again: the RIRs submitting Recognition Assessments. The threshold is two-thirds, but of the registries that file an assessment — not of the registries that exist. A registry that stays silent is not counted against a candidate; it is simply absent from the sum. The draft's publishers describe this as a two-thirds support threshold, which it is, but a fraction only means what its denominator says it means.

The same article then hands the deciding body a discretion with conditions attached. ICANN may exclude from the threshold the negative recommendation of any registry "whose Service Region or revenue would be materially impacted" by the candidate's approval — but only after that registry has been notified in writing of its potential exclusion, given ICANN's reasoning and its finding of materiality, afforded a reasonable opportunity to respond, and had that response fairly considered. Even excluded from the count, the inputs of all registries "should be considered by ICANN on an informational basis".

Two more thresholds sit in the same document, and they are not the same rule. Derecognition requires that ICANN have received a Proposal "supported by the Derecognition Assessments of at least 2/3s of the RIRs, excluding the subject RIR". Amendment requires "the unanimous agreement of ICANN and the RIRs, after consulting their respective communities". Article 7.2 then bars amendment altogether during a Temporary Emergency Continuity Arrangement or while a Proposal for Derecognition is pending.

Set the three side by side. Admission: two-thirds of those who file. Removal: two-thirds of everyone except the registry being removed. Amendment: all of them, plus ICANN. The lock is absolute on the rule and conditional on the door.

Publication is not adoption

On 28 July 2026 the ASO Address Council formally delivered the recommended draft to the NRO Executive Council, and responsibility for the document passed to the Executive Council for its consideration. On 1 September 2026 the NRO published the draft with a redline against Version 2 and a rationale report, announcing that any further community input would be announced by the Executive Council and that further updates would be coordinated by it.

The NRO's own process page supplies the detail that matters most to anyone deciding what binds: ICP-2 was not developed through the RIRs' policy development process and does not fit the definition of a Global Policy under the ASO MoU. The instrument that governs whether a new registry may exist is not a policy at all. It is a Board-accepted statement of requirements, now being rewritten by a draft that the same page lists, in its timeline, as "Approval and Adoption | Q4 2026 | Upcoming" — on a page whose displayed modification date is 04/09/2026.

Two clocks, two publishers

The second clock is ICANN's. The Monthly Board Report for August 2026, in its Policy Status table, records: "ICANN and the RIRs are now expected to begin their respective approval processes in Q1 2027 (previously Q4 2026)." The Consolidated Policy Scorecard of 21 September 2026 marks the ICP-2 revision "TIMELINE ADJUSTED", gives an expected Board delivery date of January 2027, and repeats the Q1 2027 start.

So the summary page of the body holding the pen still says Q4 2026 and Upcoming; the deciding body's own board report says the quarter after. Print both, name each publisher, and notice that neither document is an adoption.

What October showed

At ICANN 87, the Board-ASO session slides of 21 October 2026 record that the NRO EC had provided the document to ICANN for consideration, and list what came next: a last call on the final draft, a public comment process, adoption of the document by the RIR and ICANN Boards, and development of implementation procedures by the RIRs and ICANN. Milestones, in the future tense, some seven weeks after publication.

The NRO Executive Council minutes index lists 29 April 2026 as its latest meeting, published 17 September 2026, with nothing later. The RIPE NCC General Meeting transcript for October 2026 describes the same sequence: last call, then ICANN's public comment process, then adoption by the RIRs and ICANN boards. The APNIC Executive Council minutes for 6-7 September 2026 record only that an update on the document's status was provided and that the EC "noted the update".

No ICANN Board resolution adopting the document, and no NRO Executive Council approval decision, was obtained in this review. The approved-resolutions page for the Board's 22 October 2026 meeting was listed but not read, so nothing here asserts that no resolution exists. It asserts what the record obtained shows.

The instrument that controls is the one this review could not read

The NRO page states that the PDF version is authoritative and should be used in the event of discrepancies. That NRO-hosted PDF could not be obtained in readable text for this review. A LACNIC-hosted copy of the same title carries an internal cover label of "Version 3.4 (ASO AC Final Draft)", while the NRO's public pages and announcements call it Version 3. Whether the internal draft number and the public label describe the same bytes was not established here, and the provisions quoted above are therefore labelled as coming from the HTML text and indexed extracts.

It is the ordinary condition of governance reporting: the copy everyone links is not always the copy that controls.

What this means for a region without a registry

The question a candidate registry, or a government that wants one, actually needs answered is not whether the incumbents would consent. It is that consent is not currently required — not by ICP-2, which names ICANN and prints no registry vote, and not yet by any adopted successor. The consent gate is a recommendation sitting in a draft, awaiting a last call, a comment process and two boards.

That is a fragile kind of power: real in the conversation, absent from the text. It becomes real on the day a board adopts it. Until then, the printed rule is the one from 2001, and it is one sentence long. Background on the body that holds the pen is in the BTW directory.