Summary

  • APNIC's 1 September notice makes the NRO NC's Version 3.4 recommended draft, redline and rationale publicly available.
  • Article 7.2 says the document may not be amended while an RIR is in a Temporary Emergency Continuity Arrangement or while a Derecognition proposal is pending.
  • The stated purpose is to prevent hurried, case-specific rule changes or a weakening of requirements at a difficult moment; the text is a draft, not evidence of a live emergency or an adopted rule.

One of the most revealing provisions in the newly public Version 3.4 RIR Governance Document is also one of its shortest. Article 7.1 would require unanimous agreement of ICANN and the RIRs, after consultation with their communities, to amend the document. Article 7.2 adds a condition: the document may not be amended while an RIR is subject to a Temporary Emergency Continuity Arrangement, or while a proposal to Derecognize an RIR is pending.

APNIC's 1 September notice presents this as part of the NRO Number Council's recommended draft, alongside a redline and a rationale report. That status matters. The notice does not announce final adoption, implementation or an active case. It does not say any registry is in emergency continuity, faces Derecognition, or has sought to change the document.

The accompanying rationale nevertheless explains why the clause is there. It says the new condition is meant to stop hasty changes made for particular circumstances, or an effort to water down requirements at difficult moments. That is a narrow constitutional instinct. A rule meant to govern emergency continuity or Derecognition is most exposed to pressure precisely when an emergency or a Derecognition case is underway. The draft would stop its amendment path during those periods rather than let the parties alter the frame while relying on it.

Article 5 supplies the boundary. A Temporary Emergency Continuity Arrangement is a temporary mechanism for provision of affected RIR services. An affected RIR could initiate one for all or part of its own services; ICANN and two-thirds of the other RIRs could also initiate or renew one after discussion with the affected RIR and its community where reasonably possible. It may not exceed 90 days unless renewed under the same section. ICANN would have to publish the rationale and scope of an initiation or renewal promptly. Those provisions describe a possible procedure, not an event that has occurred.

The amendment lock is useful only if outsiders can tell whether it is active. The draft requires publications at several points, but it does not set out one reader-facing register that connects an arrangement or proposal to Article 7.2's status. A modest public receipt could do that without exposing legal advice, security-sensitive incident detail or negotiations.

It could name the affected RIR, say whether the condition is an emergency-continuity arrangement or a Derecognition proposal, give the decision and effective timestamps, define the scope, link the underlying notice, record renewals or closure, identify the publisher and retain corrections.

That would not make the draft binding or solve a crisis. It would simply distinguish a future safeguard from a live freeze. Without that distinction, readers can easily mistake a public description of process for a current constraint, or miss a constraint that has already begun. The rule is deliberately narrow. The public record that tells us when it applies should be narrow and clear too.

Sources