Summary

  • ICANN87 will run in Bali from 17 to 22 October 2026. ICANN says the Annual General Meeting will be an important opportunity to discuss the 2026 New gTLD Program round and its next stages.
  • The Guidebook says Reveal Day occurs no later than nine weeks after the 12 August application close absent extraordinary circumstances. That ordinary outer limit is 14 October, but ICANN has not announced that as the actual Reveal Day.
  • Reveal Day is followed by a 14-day Replacement Period. Final strings and contention sets appear on String Confirmation Day, currently projected for November rather than guaranteed on a fixed date.
  • Most application-specific routes—including the Application Comment Forum, GAC member Early Warnings, singular/plural notifications and objections by parties with standing—are tied to String Confirmation Day. GAC Consensus Advice is different and may be issued at any time.
  • ICANN87 speech should remain fully discussable but explicitly labelled. A meeting-to-procedure receipt can record the speaker, exact string version, lifecycle state, later formal route and non-conclusion that the intervention alone is not a filing, evaluation result or decision.

Three days can contain several legal states

ICANN's 1 September release does more than announce a destination. ICANN87 will be the first ICANN meeting in Indonesia, hosted locally by PANDI, and the organisation specifically presents it as a place to discuss the 2026 round after the application window produced more than 1,600 primary applications.

The calendar makes that discussion unusually delicate. Applications closed at 23:59 UTC on 12 August. The Guidebook gives ICANN nine weeks to reach Reveal Day unless extraordinary circumstances intervene. Counting that ordinary period reaches 14 October. ICANN87 opens on 17 October.

That is not a prediction that Reveal Day will be 14 October. ICANN said the exact date and timeline would be announced in mid-September, and the Guidebook preserves an exception. The correct conclusion is narrower: the meeting may sit just after first disclosure, and possibly inside the following 14-day Replacement Period.

Within that short interval, the object under discussion is not stable. Reveal Day publishes the applicable public portions of applications that passed the Administrative Check. An eligible applicant may then attest once to use its designated replacement string, and the submitted choice cannot be reversed. String Confirmation Day later publishes the strings actually proceeding and the resulting contention sets.

A person speaking on 18 October may therefore be referring to a revealed string that is still subject to an applicant's permitted choice. The same words, repeated after String Confirmation Day, refer to a different procedural object. A transcript preserves the sentence; it does not automatically preserve that change in status.

The meeting is a forum, not a filing type

Public meetings are part of ICANN's accountability architecture. The Bylaws commit the organisation to transparent, bottom-up work, documented policies applied consistently and public information about meetings and decisions. Prep Week on 5–7 October will already include a 2026-round update, with materials, recordings and transcripts available where supplied.

Those features make speech easier to inspect. They do not convert every session intervention into an application record.

The Guidebook gives formal channels their own conditions. The Application Comment Forum has a 104-day window; evaluators are required to consider comments submitted during the relevant period. GAC members can issue Early Warnings during their 104-day window. Singular/plural notifications have 30 days. Formal objections have a 104-day filing period and standing requirements. GAC Consensus Advice follows its own path and, according to ICANN's objections material, may arrive at any time.

A question from a microphone can be valuable without satisfying any of those definitions. A constituency statement can expose a public-interest issue without becoming GAC Advice. An applicant's answer can clarify an intention without constituting its irrevocable replacement attestation. A well-attended panel can shape later reasoning without becoming an evaluation finding or Board resolution.

The danger runs in both directions. Treating visible speech as if it had already entered the case can bypass notice, standing, deadlines and response rights. Treating it as mere conference chatter can cause a legitimate concern to vanish before the correct channel opens.

Give each intervention a destination

The useful control is not a ban on discussing applications. It is a small meeting-to-procedure receipt attached to any materially application-specific exchange.

The receipt should identify the session, time and stable recording or transcript; the speaker and the capacity in which that person spoke; the exact application identifier or string spelling; and the lifecycle state on that date. It should then answer the status question directly: informational statement, question, community discussion, applicant response or submission through a named formal channel.

Where follow-up is expected, the record should name the next valid route, its owner and deadline. A later link should point to the authoritative comment, objection, Early Warning, advice, evaluation response or decision that incorporated, answered or declined the point. Until that join exists, the receipt should carry a plain non-conclusion: this intervention alone is not a formal filing, evaluation outcome or decision.

Receipt field Governance function
Exact string and application version Prevents a revealed string from being confused with the confirmed one
Speaker and speaking capacity Separates personal, constituency, applicant and governmental statements
Lifecycle state Shows which procedural routes were actually open
Intervention status Prevents discussion from impersonating a filing
Next route and deadline Keeps a valid concern from disappearing
Later authoritative record Shows whether the institution answered the point
Explicit non-conclusion Preserves the difference between visibility and authority

This is not a shadow objections docket. Corridor remarks should not be harvested into evidence without notice, and private applicant data should not be exposed. The receipt is for public, material exchanges whose institutional afterlife would otherwise be ambiguous.

What the announced record does not establish

No source reviewed here establishes the actual Reveal Day, that ICANN87 will occur during the Replacement Period, or that any applicant will change a string. The November date shown on the pre-evaluation journey is a projection dependent on volume and other factors, not a promise.

Nor does the meeting announcement give ICANN87 authority to decide an application. It advertises discussion. Formal powers remain with the processes and bodies identified in the Guidebook and Bylaws.

The strongest case for early discussion is practical. Participants should be able to compare interpretations, identify common uncertainty and prepare a properly grounded submission. Smaller or less-resourced actors may particularly benefit from hearing how the process works before a short window starts. Routing protects that value; it does not diminish it.

Heng Lu's warning about mandate laundering applies here without importing his RIR dispute into ICANN. A title, room or official agenda supplies visibility and context. It does not supply the missing chain from an utterance to an authorised act. The institutional record is strongest when it preserves both.

Sources

  1. ICANN87 Annual General Meeting to Convene in Bali, Indonesia
  2. ICANN87 Prep Week Schedule Now Available
  3. ICANN 2026 Round Closes With More Than 1,600 New gTLD Applications
  4. New gTLD Program: 2026 Round Applicant Guidebook
  5. 2026 Round Resources
  6. 2026 Round Objections and Appeals
  7. ICANN Bylaws
  8. ICANN Meetings Calendar
  9. What Happens During the Replacement Period?
  10. Pre-Evaluation Applicant Journey
  11. Heng Lu — Mandate Laundering: From RIR Fantasy to Transition Architecture