Summary

  • The ICANN Board approved moving ICANN87 from Muscat to Bali under its authority to relocate a public meeting; it classified the action as an Organizational Administrative function that did not require public comment.
  • Staff and the Board Finance Committee reviewed the alternative, costs and financial risks, but the current public resolution still redacts the authorized venue and hotel spending cap and does not show a comparative venue table.

A redaction sits in the middle of ICANN’s decision to move its October 2026 public meeting. The Board’s 3 May resolution authorized contracts for the Bali venue and hotel, but the ceiling is still shown as “[Redacted – Confidential Negotiation Information]” in the currently accessible text. Around that blank, the Board published a fairly specific account of who could decide, what staff reviewed and why the change did not go to public comment.

The sequence began with a Board decision on 30 October 2025 to host ICANN87 in Muscat, Oman. On 3 May 2026, the Board approved moving the meeting to Bali, Indonesia. ICANN announced the new venue on 2 June; the official meeting page keeps the original 17–22 October dates. The Board also asked the CEO to work with Oman’s Telecommunications Regulatory Authority toward a mutually acceptable date for a future ICANN public meeting in Oman. It thanked the local host and venues for the work already done.

The record attributes the change to regional events and uncertainty over travel and security, and explicitly says these circumstances were outside the Omani host’s control.

The Board’s rationale is unusually clear about the control chain. It cites ICANN’s Delegation of Authority Guidelines, which assign the Board approval of a move from a previously identified location or a variation from the meeting strategy. It also says the Contracting and Disbursement policy requires Board approval for expenditures above US$750,000. Staff said it had searched worldwide for alternatives that met ICANN’s Meeting Location Selection Criteria. It selected Bali as suitable and consistent with the geographic rotation guidelines.

The Board Finance Committee reviewed financial risks and mitigation; it found them reasonable and acceptable. The Board says it reviewed the information and costs and agreed with the committee.

That is evidence of a formal review, not a public comparison an outside reader can reproduce. The published rationale does not identify all alternatives considered, provide a scored shortlist or disclose the full cost assumptions. It authorizes venue and hotel spending but leaves the ceiling redacted. A footnote says the resolution was republished on 1 June to release certain negotiation information; the amount remains redacted in the version currently available. The evidence supports neither a claim that the Board skipped financial review nor a claim that the public can independently test the price.

The other consequential line is procedural: the Board calls the relocation an Organizational Administrative function that does not require public comment. The Board had a stated authority to approve a venue move, and the record describes staff and finance review. That does not prove public comment was legally required. It does show how the institution drew the boundary between operational administration and a policy decision. The location of a meeting can shape cost and access, but the published process treated this choice as an organizational matter rather than a policy change.

The Board acknowledged financial effects on ICANN and travel costs for the community. It said those costs would arise whatever location was chosen and were included in the approved FY27 budget. That statement addresses the existence and budget treatment of costs, not their distribution. The public record does not compare likely travel costs across candidate cities or measure which groups would bear them. Nothing in the available evidence establishes that the move excluded a group or changed participation; neither can a budget line answer who paid more.

Three separate questions therefore remain. The Board’s authority to move the meeting is documented. The internal review is described, including a high-value spending threshold and Finance Committee assessment. The external record does not show a reproducible cost comparison or the authorized cap. Keeping those questions separate avoids two unsupported conclusions: that confidentiality proves misconduct, or that a completed internal approval makes public accountability unnecessary.

Primary records are the Board’s 3 May resolutions and rationale, the 30 October 2025 venue resolution, ICANN’s 2 June venue announcement, its meeting-location criteria, and the ICANN87 meeting page. The records do not establish actual spending, the final comparison set, realized travel-cost incidence or attendee outcomes. The published minutes of the 3 May meeting also record the Board’s decision.