Summary

  • Version 3 requires engagement with all RIR communities after a Temporary Emergency Continuity Arrangement begins, but says the RIRs may elect additional engagement after renewal.
  • A renewal still needs a published decision, rationale and scope; under the external route it also needs ICANN and two-thirds of the other RIRs, after discussion with the affected RIR and its community where reasonably possible.
  • A compact renewal receipt can preserve emergency speed while showing elapsed time, scope changes and why renewed community engagement was or was not opened.

The first 90 days and the next 90 days do not carry the same participation rule.

That is the small but consequential switch inside Article 5.1 of the recommended RIR Governance Document Version 3, published by AFRINIC and the Number Resource Organization on 1 September. The text describes a Temporary Emergency Continuity Arrangement, or TECA, for circumstances in which a Regional Internet Registry cannot adequately provide all or part of its registry services. A qualified temporary operator may then provide the affected services.

This is a recommended final draft, not proof that the document has been adopted, has replaced ICP-2 or is in force. Nothing in the inspected sources says that AFRINIC—or any other RIR—is presently subject to such an arrangement.

The rule changes at renewal

Article 5.1 offers two starting routes. An affected RIR may initiate an arrangement for all or part of its own services. A TECA may also be initiated or renewed with the agreement of ICANN and two-thirds of the other RIRs, following discussion with the affected RIR and its community where reasonably possible.

One interval may not exceed 90 days unless renewed under the same section. ICANN must promptly publish the decision to initiate or renew, including its rationale and scope. Those are meaningful controls: renewal is not meant to be an invisible extension.

Participation then divides into three different surfaces. After initiation, a community-engagement process must be opened with all RIR communities as soon as reasonably practicable. The affected RIR and its community sit inside the initiation-or-renewal discussion, subject to the emergency qualification. ICANN engages its own community as appropriate under its bylaws and procedures.

After renewal, however, the draft says the RIRs “may elect” to conduct additional engagement with the RIR communities. The first global process is compulsory; another global process is discretionary. That does not mean renewal can evade the affected community, or that ICANN can dispense with publication. It means that one particular cross-regional feedback circuit changes state at the boundary.

The boundary matters because time is not the only variable that can move. Article 5.1(f) permits the temporary operator’s service scope to increase or decrease during an arrangement or upon renewal. A second interval can therefore continue for longer and cover something different from the first. The inspected text gives each interval a 90-day limit but states no numeric cumulative cap on renewals.

Speed is the strongest defence

Emergency continuity exists because delay can be more damaging than procedural imperfection. Allocation, registration, directory, reverse-DNS or related technical services cannot wait for an elaborate consultation cycle if operational capacity has failed. The first all-community process may still be open when the renewal decision arrives. Its evidence may remain current. Repeating the entire exercise automatically could generate noise, invite tactical delay or distract the people restoring service.

The draft also retains other protections. The renewal decision, rationale and scope must be published promptly. The external renewal route needs a two-thirds vote of the other RIRs alongside ICANN. Discussion with the affected RIR and its community is required where reasonably possible. ICANN’s own engagement duties do not disappear. And once the arrangement ends, Article 5.2 requires a joint post-event review with a public report, an assessment of the temporary operator, community feedback and recommendations for improvement.

The answer is therefore not a referendum at every 90-day mark. It is a record that lets communities see how discretion was used.

A renewal receipt

Each renewal should publish a compact receipt beside the decision. It would identify the arrangement and interval number; the initiating authority; the start, end and cumulative elapsed time; the temporary operator; the service scope before and after renewal; and the reason for any scope change.

It would record when the affected RIR and affected community were approached, or the bounded reason discussion was not reasonably possible. It would link the most recent all-RIR-community process and state whether a new one was opened. If not, it would explain whether the earlier process remained live, the scope was unchanged, restoration work made delay unsafe, or some other reason controlled the choice. It would also show ICANN’s engagement state, the restoration test and the next decision date.

Sensitive continuity information does not belong in that receipt. Credentials, private registration data, exploitable architecture and protected incident evidence can remain withheld. Nor should the receipt become an approval gate. Its purpose is narrower: keep renewal authority, community participation and service scope in the same reconstructable record.

Version 2 already contemplated a 90-day emergency period, community engagement and renewal. Version 3 makes the renewal decision route more explicit, lowers the external threshold and draws the initial-versus-additional engagement distinction in the operative text. The NRO’s rationale describes the revision as a way to respond faster while retaining the 90-day limit and adding transparency safeguards.

That is a credible design objective. But a time limit restrains emergency power only if each reset remains visible. When a mandatory public process becomes an elective one, the decision not to reopen it is itself part of the emergency record.

Sources