Summary

  • ICANN’s Bylaws now record 10 June 2026 as the effective date of Section 27.6, which pauses the obligation to conduct the four named Specific Reviews without deleting Article 4.6’s underlying review architecture.
  • The pause normally runs for 12 months and cannot exceed 24. A further pause requires one of two stated predicates and supporting rationale; neither a calendar maximum nor a community discussion automatically extends it.
  • The Board approval passed through public comment and an Empowered Community rejection-action period. ALAC’s petition and the ASO’s decision not to support it are separate events, neither of which may be substituted for the entire institutional sequence.
  • If the old duty resumes, Section 27.6 provides a staged restart path. Later review initiation, final reports, recommendation implementation and operational effect remain separate facts that need their own evidence.
  • A compact public state record would let readers see the live legal state without converting a temporary coordination rule into a permanent suspension, a generic claim of accountability or a conclusion about review quality.

A pause that changes a duty without deleting it

The word pause creates an easy but misleading picture: a process stopped, a clock frozen, an institution waiting. ICANN’s current rule is more specific. The current Bylaws, amended on 3 July 2026, place Section 27.6 in Article 27, the Transition Article. They give the clause an effective date of 10 June 2026. From that date, ICANN’s obligation to conduct four named Specific Reviews is paused: the Accountability and Transparency Review, the Security, Stability and Resiliency Review, the Competition, Consumer Trust and Consumer Choice Review, and the Registration Directory Service Review.

That wording matters because the rule changes an obligation to initiate or conduct named reviews; it does not announce that accountability, security, registration data, competition or consumer trust have ceased to matter. Nor does it repeal Article 4.6 in the ordinary sense. The public-comment proceeding described the proposed Transition Article as leaving the text of Article 4.6 intact while creating a bounded transition path around its current timing problem. The distinction is deliberately legal as well as editorial.

A future reader needs to be able to locate the pre-existing obligation, the transition clause that temporarily changes its operation, and the event that determines which one governs on a particular date.

The background is not a mystery, but it is not a blank cheque either. In its 3 May resolutions, the Board recorded that Article 4.6 had called for three of the four Specific Reviews every five years, measured from the convening of the prior review team. It also recorded that ATRT4 was supposed to have been convened in 2023 and had been deferred twice; the next SSR and RDS review iterations had likewise been deferred while the future of those reviews was being considered. The Board’s explanation was workload and overlap, insufficient time for implementation between review cycles, and ongoing community work through the Review of Reviews Cross Community Group.

Those facts justify neither of the two convenient stories. The first says that a delayed obligation no longer exists because it has proved inconvenient. The second says that a bounded amendment created only to make the path legible is proof that every previous or future delay is improper. The live record says something narrower: a prior duty remains visible, the institution adopted a temporary rule through a defined amendment process, and that rule has its own limits and return path. Its quality depends on whether later readers can reconstruct the state changes without guessing.

The effective date is an institutional fact, not a decorative date

The approved 3 May text was marked “Subject to Empowered Community Process.” That qualification is not a footnote. It distinguishes the Board’s adoption of a proposed Standard Bylaws amendment from the later point at which the amendment takes effect. Section 27.6’s current text supplies the operative answer: 10 June 2026.

Between those two dates, public bodies made distinct moves. The ASO’s 3 June notice says that ALAC, acting as an Empowered Community Decisional Participant, issued a Rejection Action Petition against the Board-approved amendment. It describes ALAC’s concerns in terms of accountability reviews, formalized delay, long gaps and the treatment of public-comment input. That is evidence of a petition and of a stated objection. It is not proof that the amendment was rejected, that the ASO agreed, or that all Decisional Participants reached one conclusion.

The ASO’s 9 June follow-up adds another bounded fact. The ASO consulted the RIR communities, received no input supporting the petition through that consultation process, and said that it would not support it. That is an ASO result. It should not be inflated into a total account of the Empowered Community’s procedure. A robust public record can show the petition, the ASO’s consultation and position, the current in-force Bylaws text, and any separately documented completion event without treating any one of them as a proxy for all the others.

The practical lesson is simple. Every transition rule needs a state chain. For this one, at minimum: the Board’s approval date; the amendment path; public comment and its summary; petition notice; each relevant Decisional Participant’s public action where available; the effective date in the current Bylaws; and the current version of the clause. A link collection is not enough. The record should identify what proposition each document proves and what it cannot prove.

Twelve months is a default resumption point, not an automatic continuation right

Section 27.6 creates an initial twelve-month pause from its effective date. It then says that the obligation resumes unless one of two circumstances exists. The first is a Board acceptance of community-developed recommendations issued after the effective date on how any or all Specific Reviews should be modified, accompanied by a direction to implement them. The second is a statement supporting a further pause from four of the seven Supporting Organizations and Advisory Committees named in the Bylaws. The total pause cannot exceed twenty-four months, and any extension must be accompanied by supporting rationale.

Each component answers a different question. The twelve-month date is a default deadline. The twenty-four-month figure is a maximum outer limit, not a permission that automatically fills itself. A community draft is neither accepted recommendation nor implementation direction. Four SO/AC statements are a distinct extension predicate, not a shorthand for the Empowered Community’s separate formal powers. Supporting rationale is not merely a press release; it is the stated reason that allows a reader to see why a particular predicate was treated as satisfied and what work still remains.

The distinction was anticipated in the public-comment summary. Participants supported a limited, exceptional device while asking for regular updates, clearer extension criteria, reasoning, readiness evidence and safeguards against repeating review overload. The NCSG, for example, supported a limited mechanism rather than a general suspension of accountability obligations. Other comments treated a calendar alone as insufficient evidence of readiness. Those views are not legal amendments by themselves. They do show why a status record must distinguish a time boundary from the evidence that would support moving it.

There is a temptation to replace this structure with a single traffic light: green if the Reviews CCG is busy, red if it is not. That is not what the clause says. The CCG’s public workspace records a Draft Report released for public comment on 25 June 2026. Its existence is meaningful evidence of published work. It is not, without another instrument, proof that the Board accepted a post-effective-date community recommendation, directed implementation, amended Article 4.6, or extended the pause. A draft, a consultation, an acceptance, a direction and an amendment are five different governance events.

Restart is a sequence, not a promise that all review work begins at once

The clause’s return path explains why an ordinary clock is too thin a model. If the previous Article 4.6 duties resume, the Accountability and Transparency Review is to be initiated within ninety days. The SSR review then follows within eighteen months of ATR initiation, unless the ATR has not delivered a final report by then, in which case the clock changes to two months after the ATR submits it. The RDS review follows a comparable sequence from the SSR review. The CCT review has its own conditional triggers tied to the 2026 new-gTLD round, application volume and delegation thresholds.

Those are not four identical restart dates. They are a dependency graph. The approved transition text also allows an ATR recommendation to pause an affected later review while that recommendation is considered by the Board and any resulting Article 4.6 amendment process is pending. If the ATR affects SSR but not RDS, the text specifies how the unaffected RDS path proceeds. This is a deliberate refusal to treat “reviews restarted” as a single binary event.

It would be careless to promise that sequencing alone resolves the capacity problem. The public-comment record contains competing views about calendar triggers, implementation capacity, volunteer availability, security and stability attention, data readiness and the risk that a staged schedule recreates congestion in slower form. The rule gives a public baseline for the next steps; it does not certify that the conditions for a useful review already exist.

The same restraint applies at the far end. A review team’s convening is not a final report. A final report is not Board acceptance. Board acceptance is not implementation. Implementation is not evidence of operational effect, and none of those acts automatically validates or condemns the temporary pause that preceded them. Treating them as one event creates precisely the opacity that a transition article ought to reduce.

The missing object is a state record, not a new veto

ICANN does not need a new institution to make Article 27.6 readable. It needs one small, dated public record with one row for each affected Specific Review and a shared row for the transition rule. The record should begin with the old Article 4.6 trigger, identify the Section 27.6 effective date and version, state the present legal state, name the next default expiry and link the instrument that proves it.

If anyone invokes a further pause, the record should name the predicate: Board acceptance plus directed implementation, or four-of-seven SO/AC statements. It should identify the documents, their dates, the issuing bodies, the supporting rationale, the resulting end date and the maximum date that remains. It should not infer the missing predicate from a meeting agenda, a public draft or a commentator’s endorsement.

For the restart path, the record should give each review its own trigger and calculated deadline, then show a separate state for actual initiation. It should link the first ATR disposition that affects a later review and distinguish a pending amendment process from a completed amendment. A later row can record a final report, Board action, implementation status or evidence of operational effect, but it must not retroactively rewrite the earlier pause record.

This is not a demand to publish confidential deliberation, personal votes that are not already public, private assessments of volunteers or a universal score for review quality. Nor does it make the public a replacement Board, an alternate CCG or a shadow Empowered Community. It is a provenance surface. It allows a participant, registry operator, researcher or future reviewer to ask: what rule was active on the date in question; what event changed it; who held that decision right; and what later effect has actually been shown?

The value of a bounded exception is that it can end visibly

The strongest argument for a Transition Article is not that reviews are burdensome. Institutions often call an obligation burdensome precisely when it starts to matter. The stronger argument is that the existing review architecture had accumulated timing and implementation problems, that those problems were publicly discussed, and that a temporary amendment can establish a transparent way to avoid pretending the old schedule is being met while work proceeds on a replacement.

But bounded exceptions acquire legitimacy only by remaining bounded. The effective date must be public. The baseline must remain legible. An extension must be tied to its actual predicate and rationale. The maximum must not become a default. The CCG’s draft work must be kept distinct from acceptance and implementation. And resumption must be visible as a set of review-specific acts, not a ceremonial declaration that accountability has returned.

Section 27.6 supplies much of that architecture in law. A public state record would supply the operational memory. Together they would let ICANN change how it coordinates a difficult review system without asking readers to accept that a pause, a draft and an eventual outcome all mean the same thing.

Sources

  1. ICANN Bylaws, as amended 3 July 2026
  2. Approved Resolutions, ICANN Board regular meeting, 3 May 2026
  3. Transition Article To Address Specific Reviews, approved by the Board 3 May 2026
  4. Public-comment proceeding: Standard Bylaws Amendment – Transition Article on Specific Reviews
  5. Public Comment Summary Report
  6. ASO notice: Request for consideration of Empowered Community Rejection Action
  7. ASO follow-up notice on the Rejection Action Petition
  8. Review of Reviews Cross Community Group workspace