Summary

  • The Board, not the CEO acting alone, approved the need to move ICANN87 from Muscat to Bali; its 3 May resolution then authorized the CEO or designees to implement the move and contract for the venue.
  • The public record explains the travel and security uncertainty, the Finance Committee’s review and the regional-rotation rationale, but redacts the authorized contract ceiling as confidential negotiation information.
  • The US$750,000 approval threshold in ICANN’s contracting policy is a separate rule. It does not reveal the redacted cap, the final contract value or what ICANN ultimately spent.

The record of ICANN87’s move is more complete about authority than about money. In minutes published on 24 June, the ICANN Board says it approved the move from Muscat, Oman, to Bali, Indonesia, at its 3 May meeting. It then authorized the President and CEO, or designees, to take the steps necessary to change the location and to enter venue and hotel contracts. The resolution’s final amount is replaced with “[Redacted – Confidential Negotiation Information].”

That wording matters. ICANN’s Delegation of Authority Guidelines assign the Board approval of the need to move a Public Meeting from a previously identified location. After that approval, the President and CEO identifies sites within the approved budget and meeting-strategy variance. The Board’s resolution follows that division: it records the Board’s decision and delegates implementation. Calling this simply “the CEO moved the meeting” would collapse two distinct acts and obscure where the formal authorization sat.

The rationale is also unusually traceable. The Board record says Muscat had been the original location, and that events in the Middle East and a recent escalation created travel and security uncertainty that could impair a successful meeting there at that time. It says staff conducted a worldwide search and analysis, identified Bali as suitable, and considered its fit with geographic rotation. The Board Finance Committee reviewed financial risks and mitigation measures and found them reasonable and acceptable. The Board says it reviewed the information and costs and accepted the proposal against significant selection criteria.

Those criteria are not a single price comparison. ICANN’s published host guidance covers cost to ICANN and the community, international-airport access, local transport, hotel supply, meeting facilities, network infrastructure, participant safety and host responsibilities. ICANN’s meeting strategy calls for three meetings each year in different geographic regions and balances coverage over time. The minutes say the staff’s worldwide search found Bali consistent with the rotation framework. They do not publish every candidate, scoring weight or comparative worksheet.

The public record supports what ICANN says it considered; it does not let an outside reader independently reproduce the selection.

The move also involved a second institutional relationship. The Board thanked Oman’s Telecommunications Regulatory Authority and the local host partners for work already done in support of Muscat. It asked the CEO to work with the TRA to identify a mutually acceptable date for a future ICANN Public Meeting in Oman. ICANN’s 2 June announcement said the October meeting would proceed in Bali on 17–22 October. That confirms implementation, not the quality of every alternative considered.

The missing number is easy to misread because the same minutes cite a US$750,000 Board-approval threshold in the Contracting and Disbursement Policy. That policy sets officer approval levels up to US$750,000 and Board approval above it, while also describing an exception for obligations included in a specific Board-approved project budget. The ICANN87 resolution separately authorizes venue and hotel contracts up to a redacted not-to-exceed amount. A threshold that determines when Board approval is required is not the same thing as a particular contract’s authorized ceiling. Nor is either figure automatically the final amount paid.

The resolution discloses none of those values.

The record says the Board Finance Committee carried out due diligence on the proposed expenditure and reviewed the financial risks and the mitigations described by staff. The minutes state that the costs were accounted for in the Board-approved FY27 operating plan and budget. They also classify the action as an Organizational Administrative Function that does not require public comment, and state that it has no impact on DNS security or stability. Those classifications describe the action’s stated process and assessed effect.

They do not erase the unanimous Board vote or the Finance Committee review, and they do not turn a venue decision into a policy-development proceeding.

Negotiation confidentiality can protect a live commercial process. The published resolution itself says the specified information remains confidential for negotiation purposes until the President and CEO determines that release is appropriate. The record therefore offers a bounded answer, not a blank one: who approved the move, who was empowered to execute it, what reasons the Board recorded, and why a particular amount is temporarily withheld. Whether the later release decision has occurred, what the ceiling was, what the final contract covered and what was ultimately spent are not established by the reviewed public material.

The distinction is between a decision that can be followed and a cost exposure that cannot yet be compared. Readers can inspect the authority chain and the stated criteria. They cannot test the maximum contractual exposure against other sites or later reconcile it with invoices. The minutes are not evidence of misconduct, and the redaction alone does not establish that disclosure rules were breached. It is, however, a specific limit on public evaluation that should remain visible as a limit rather than be filled with a guess.

After negotiation confidentiality ends, ICANN should publish the released ceiling—or identify what remains withheld—along with the final contract scope and spend, the selection-criteria record and any material variance from the approved amount. This is a recommendation about making the decision auditable over time, not a claim that the Bylaws require immediate publication of a live negotiating figure.

Sources