ICANN Resolutions » ICANN82 Venue Contracting
Important note: The Board Resolutions are as reported in the Board Meeting Transcripts, Minutes & Resolutions portion of ICANN's website. Only the words contained in the Resolutions themselves represent the official acts of the Board. The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.
Whereas, ICANN intends to hold its first Public Meeting of 2025, currently scheduled for 8-13 March 2025 (ICANN82), in the North America region.
Whereas, following the change of the ICANN72 meeting in Seattle, Washington to a virtual meeting, ICANN rescheduled with the venue and arranged to hold the ICANN82 meeting in Seattle.
Whereas, ICANN's rotation among geographic regions for public meetings is measured over a 5-year period.
Whereas, selection of Seattle as the location for ICANN82 adheres to the geographic rotation guidelines established in the Meeting Strategy Working Group.
Whereas, ICANN organization has completed a thorough review of the venue and finds the one in Seattle, Washington to be suitable.
Resolved (2022.05.01.03), the Board authorizes the President and CEO, or his designee(s), to engage in and facilitate all necessary contracting and disbursements for the host venue for the March 2025 ICANN Public Meeting in Seattle, Washington, in an amount not to exceed [REDACTED – CONFIDENTIAL NEGOTIATION INFORMATION].
Resolved (2022.05.01.04), specific items within this resolution shall remain confidential for negotiation purposes pursuant to Article 3, section 3.5(d) of the ICANN Bylaws until the President and CEO, or his designee(s), determines that the confidential information may be released.
As part of ICANN's Public Meeting strategy, ICANN seeks to host a meeting in a different geographic region (as defined in the ICANN Bylaws) three times a year. ICANN75 is scheduled for 8-13 March 2025. Following the change of the ICANN72 meeting in Seattle, Washington to a virtual meeting, ICANN rescheduled with the venue and arranged to hold the ICANN82 meeting in Seattle.
ICANN org previously confirmed that the Seattle, Washington meeting location meets the Meeting Location Selection Criteria. ICANN's rotation among geographic regions for public meetings is measured over a 5-year period. Selection of this North America location adheres to the geographic rotation guidelines established in the Meeting Strategy Working Group. ICANN org did not conduct a broader search for other available locations for this meeting due to the already confirmed suitability of the venue.
The Board Finance Committee (BFC) has carried out its standard due diligence in reviewing the proposed board decision to recommend approval to the Board. As part of this diligence, the BFC has reviewed the financial risks associated with the proposed decision and the information provided by the org on the measures in place to mitigate those risks. The BFC has found these financial risks and the mitigation measures in place to be reasonable and acceptable.
The Board reviewed the organization's briefing for hosting the meeting in Seattle, Washington and the determination that the proposal met the significant factors of the Meeting Location Selection Criteria, as well as the related costs for the facilities selected, for the March 2025 ICANN Public Meeting. ICANN conducts Public Meetings in support of its mission to ensure the stable and secure operation of the Internet's unique identifier systems, and acts in the public interest by providing free and open access to anyone wishing to participate, either in person or remotely, in open, transparent and bottom-up, multistakeholder policy development processes.
There will be a financial impact on ICANN in hosting the meeting and providing travel support as necessary, as well as on the community in incurring costs to travel to the meeting. But such impact would be faced regardless of the location and venue of the meeting.
This action will have no impact on the security or the stability of the domain name system.
This is an Organizational Administrative function that does not require public comment.