Summary

  • ICANN’s 1 October 2026 GAC register says the permanent, no-cost, post-registration notification system is complete. It separately says the implementation review team is still finalizing the curative-rights work whose completion is a dependency for releasing currently reserved IGO acronyms.
  • The Board’s October 2025 resolution directs ICANN org to finish both lines of work “to enable” the Board to lift the interim second-level moratorium. The notification milestone, the implementation milestone and the eventual Board act are distinct states.
  • A June 2026 estimate placed the policy effective date in Q2 2027 and said acronyms would not be released before then. That was a dated projection, not a Board-set release date. The latest public record reviewed here does not show a moratorium-lifting resolution.

A status page with two clocks

The phrase “IGO acronym protections” covers a policy history long enough to make the status column look deceptively simple. The current record is more useful when read as a set of separate clocks.

On 1 October 2026, ICANN’s Governmental Advisory Committee (GAC) Advice Status page showed three open consensus-advice items in Phase 4, “Implement.” Two concern IGO protections: the 2021 ICANN71 item and the 2023 ICANN76 item. For both, the action field says the IGO-INGO Curative Rights Implementation Review Team (IRT) is finalizing its work, and that completion is a dependency for releasing currently reserved IGO acronyms.

The same register records a different milestone. Several earlier advice items were closed on 23 July 2026. In some rows, closure follows adoption of the curative-rights recommendations; in others, it follows completion of a permanent notification system that will tell an affected IGO when a third party registers a matching acronym. The system is described as post-registration and without cost to IGOs.

Those entries do not contradict one another. They describe different work products and different advice items. But read quickly, a page full of closures can create the impression that the reservation itself has ended. It has not. The same page’s open IGO rows say that implementation is unfinished and tie its completion to release.

What the Board actually authorized

The interim reservation began in 2014, when the Board deferred action on the remaining 2013 GNSO recommendations concerning second-level IGO acronyms and required registry operators to withhold those acronyms from registration while further work proceeded. This story concerns that second-level interim reservation—not full-name protections, top-level names, the .GCC dispute, or the separate process for updating the IGO list for the next new-gTLD round.

In April 2023, the Board adopted four recommendations from the 2018 IGO-INGO access-to-curative-rights process and all five recommendations from the 2022 expedited IGO curative-rights process. It directed implementation and asked for an implementation plan covering staffing, resources and timelines. Adoption resolved a policy question; it did not mean the implementing rules had taken effect.

On 30 October 2025, the Board declined to adopt the remaining 2013 recommendations 3.3.5 and 3.3.7, reasoning that subsequent policy work had superseded them. The accompanying resolution is the key operational instruction: ICANN org was directed to complete ongoing work “to enable the Board to lift” the second-level moratorium. The text names the curative-rights recommendations and the permanent notification system. The rationale says lifting was expected after notification launch and once implementation of the Board-adopted curative-rights recommendations was complete.

“Enable the Board to lift” is not the same as “lift.” The Board established a path toward a later act; it did not make the reservation expire automatically when one component was delivered. The 2026 status record now says that the notification work is complete, while the IRT work remains open. That is progress, not the final state.

The implementation record is still being written

The public-comment proceeding that ran from 30 June to 10 August 2026 concerned three implementation deliverables: updates to the Uniform Domain-Name Dispute-Resolution Policy and Rules; updates to the Uniform Rapid Suspension Procedure and Rules; and policy guidance on IGO use of those mechanisms. The 1 September summary report counted 17 comments. It records support as well as requests for revisions and clarification, including questions about whether draft language matches the adopted recommendations, how arbitration would operate, how it interacts with court proceedings, and what registrants and providers would need to know.

The report does not announce a final policy text. It says ICANN org will review the submissions with the IRT and decide whether changes are necessary; the IRT’s record of how comments were considered would follow completion of that work. This is a normal part of implementation, not evidence that any commenter has prevailed or that the policy has been reopened. The distinction is simply that a public-comment summary is an input record, not proof of finalization or effectiveness.

A 2 June 2026 message from GNSO support provides a dated schedule. It said the draft documents were then expected to enter public comment in Q3 2026 and projected a Q2 2027 policy effective date. On that basis, it said acronyms would not be released until at least Q2 2027. The public-comment window did in fact open in June and close in August, with the summary report issued in September. But the Q2 2027 date remains an estimate from June, not a new Board resolution and not a guarantee that release will occur on that date.

The current evidence therefore supports a narrow conclusion: one protective component has reached completion; the implementation package remains under review; and the Board’s release decision remains a separate step. The available record does not establish whether every technical or operational element of the notification service is already live, how many acronyms are currently reserved, or the precise date on which the Board will act. Those questions should not be answered by inference from an advice item’s closure.

Why the distinction is operational

The reservation and the replacement protections distribute risk differently. A blanket interim hold prevents registration of listed acronyms before a dispute arises. A post-registration notification system tells an IGO that a match has been registered; it does not itself decide whether the registration is abusive or resolve a dispute. Curative procedures address the latter problem through specified processes and remedies. The Board’s stated design joins those elements rather than treating notification as a substitute for the ability to pursue a remedy.

That design also preserves a boundary between institutional aims and registrant rights. The Board said the combined policy work should protect IGOs’ public-interest missions within the scope of international law while safeguarding registrants. Implementation details matter because procedural notice, standing, arbitration, court review and provider operations shape how those interests meet in practice. The public-comment report makes clear that several such details were still being assessed in September.

For registries and registrars, the relevant trigger is not that a GAC table has a row marked “closed.” It is the effective policy and the Board’s formal action changing the reservation. For IGOs, the completed notification work is a real safeguard, but it should not be mistaken for the curative-rights framework becoming effective. For registrants, the reverse error would be to read the old interim reservation as permanent after the implementation path has advanced. The accurate view is conditional and time-bound: implementation continues; a June estimate points no earlier than Q2 2027; and release requires the Board’s next decision.

This is how a long-running policy file should be read: not as a single red or green light, but as a chain of authority, implementation and effect. Adoption can close one question. A deployed operational service can close another. The implementation review team can still be working. And a Board may still need to act before the legal and operational state changes. In October 2026, ICANN’s own public records show all four propositions at once.

Sources