Summary

  • ICANN says its ICANN90 Annual General Meeting will run from 30 October to 4 November 2027 at the Adelaide Convention Centre, with .au Domain Administration (auDA) as local host.
  • The Board authorized venue contracting in March 2026; the public resolution still redacts its financial ceiling. Neither that authorization nor September's announcement reports a signed-contract date or actual cost.
  • ICANN's host criteria place substantial meeting-support duties beside promotional benefits but reserve site-selection discretion to ICANN. Hosting does not itself grant a policy mandate.

An organization can arrange invitations, network access and a welcome desk without acquiring the authority to speak for everyone who enters the room. That distinction is the interesting part of ICANN's 24 September announcement of Adelaide as the venue for ICANN90. The meeting is scheduled for 30 October–4 November 2027 at the Adelaide Convention Centre. ICANN names auDA as the host and says participation will be free, open and available in person or remotely. These are concrete commitments about a future event, not observations of how that event has worked.

There are two public clocks. On 12 March 2026 the ICANN Board authorized its President and CEO, or designees, to contract for the Adelaide host venue and make related disbursements. The Board said the choice followed geographic rotation, venue assessment and a review of financial and participant safety risks. The amount not to be exceeded is still redacted as confidential negotiation information on the published resolution. The authority to sign is therefore visible, while the date of any signed agreement and the final expenditure are not established by these documents.

September's announcement adds the public venue, dates and named local host; it does not fill those missing figures.

ICANN's published meeting-location criteria make the host role more specific than a logo. A local host is expected to assist with the venue and supporting hotels, provide invitation letters and help on visa and immigration issues, identify and fund installation of external Internet bandwidth, coordinate required IP address space, and help with government, security, vendors and customs. Those are operational obligations at points where an international meeting can succeed or falter for a participant. The page is a general selection document, however, not a report that auDA has already delivered any of these items for 2027.

The same criteria list benefits: prominent acknowledgement, signage, an exhibit space, social promotion and a high-level speaking opportunity at the welcome. A welcome platform can give a host visibility. It is not a vote, a power to set policy, or authorization by absent Internet users. ICANN says selection of the location remains solely within its discretion. The March Board action concerns the venue contract, not a reassignment of ICANN's policy processes. Treating the host's ceremonial presence as a governance mandate would muddle the very accountability that an open meeting is supposed to make inspectable.

Free remote participation also deserves precise language. ICANN has announced a channel. It has not yet published ICANN90 attendance, network performance, visa outcomes or an assessment of whether different participants could engage equally. The host criteria specify assistance with invitation letters and connectivity; they do not promise every applicant admission or every remote speaker an uninterrupted session. Neither a future attendance count nor a welcome speech will establish consent to whatever policy discussions occur. Participation can bring evidence and objections; it cannot silently stand in for authority.

The useful pre-meeting record would name an owner and status for each practical dependency: venue procurement under ICANN, invitation and visa assistance, external connectivity and IP coordination, and the remote-participation channel. It should distinguish a promised support path from a tested one and identify where a participant can escalate a failure. This proposed “host-role receipt” is Daniel Kade's editorial accountability device, not a new ICANN requirement. It would let readers judge whether the meeting's access conditions were prepared without inventing a policy power for its local host.

Sources