Approved Resolutions | Regular Meeting of the ICANN Board | 22 October 2026

Деятельность и заседания Правления
Контент доступен только на следующих языках
Whereas, ICANN has an established need to continue contracting with an Enterprise Resource Planning (ERP) provider.
Whereas, the Board Finance Committee (BFC) has reviewed the financial implications of a new contract for an ERP provider.
Whereas, ICANN staff and the BFC have recommended that the Board approve the below resolutions.
Resolved (2026.10.22.01), the Board authorizes the President and CEO, or his designee(s), to enter into, and make disbursements in furtherance of, a [Redacted – Confidential Negotiation Information] contract with [Redacted – Confidential Negotiation Information] for a value not to exceed [Redacted – Confidential Negotiation Information].
Resolved (2026.10.22.02), specific portions of this resolution shall remain confidential for negotiation purposes pursuant to Article 3, Section 3.5(b) of the ICANN Bylaws until the President and CEO determines the information may be publicly released.
ICANN's ERP provides an integrated solution under a single system of record improving systems capacity, global reporting and analysis capability, leading to improved productivity and cross-functional efficiencies, and enhanced internal controls. [Redacted – Confidential Negotiation Information].
[Redacted – Confidential Negotiation Information].
The Board agrees with staff and the Board Finance Committee's recommendations for entering into this new [Redacted – Confidential Negotiation Information].
Taking this action fits squarely within ICANN's mission and the public interest in that it ensures that payments of large amounts for one invoice to one entity are reviewed and evaluated by the Board if they exceed a certain amount of delegated authority through ICANN's Contracting and Disbursement Policy. This ensures that the Board is overseeing large disbursements and acting as proper stewards of the funding ICANN receives from the public.
There will be a financial impact on ICANN to enter into this contract, and that impact was anticipated and included in the FY27 Operating Plan and Budget.
This action will not have a direct impact on the security, stability and resiliency of the domain name system.
This is an Organizational Administrative function that does not require public comment.
Whereas, the Operating Fund includes the funds used for ICANN's day-to-day operations and must contain enough funds to cover a minimum of three months of ICANN's operating expenses.
Whereas, the Project Fund is meant to be used for projects that are large, multi-year, and do not fit within the annual budget.
Whereas, periodically, if surplus funds exist in the Operating Fund after an allocation to the Reserve Fund has been considered or decided, an allocation to the Project Fund will be considered based on the project needs identified.
Whereas, the Operating Fund as of 30 June 2026, contained surplus funds.
Whereas, both ICANN organization and the Board Finance Committee have recommended that the Board approve a US$20,000,000 transfer to the Project Fund from the Operating Fund.
Resolved (2026.10.22.03), the Board approves the transfer of US$20,000,000 from the Operating Fund to the Project Fund.
As part of ICANN's Investment Policy, the Operating Fund should be at a level of funds to cover a minimum of three months of ICANN's operating expenses.
The Project Fund is used to address activities and projects that are large, multi-year, and do not fit within the annual budget. If the Operating Fund contains surplus after an allocation to the Reserve Fund has been considered or decided, an allocation to the Project Fund will be determined based on the project needs identified.
As of 30 June 2026, there was surplus in the Operating Fund of at least US$20,000,000, and both ICANN organization and the Board Finance Committee recommended that the Board approve US$20,000,000 be transferred to the Project Fund.
This action is consistent with ICANN's mission and is in the public interest that ICANN uses the Project Fund to fund projects, as approved by the Board, when the size, complexity, and length of the projects create a challenge to be solely funded by the annual Operating Fund.
This action will not have a direct financial impact on ICANN, and will not have an impact on the security, stability, or resiliency of the domain name system.
This is an Organizational Administrative function that does not require public comment.
Whereas, the ccPDP4 Working Group (ccPDP4 WG) submitted its Final Report with its proposed policy on the de-selection of IDN ccTLDs to the ccNSO Council in February 2024, and the ccNSO subsequently delivered its report to the Board on 25 June 2024 (the "ccPDP4 Board Report").
Whereas, the ICANN Board convened a Board Caucus on IDN ccTLDs (ccPDP4 Caucus) to support the Board's consideration of the ccPDP4 Board Report. As part of the ccPDP4 Caucus' work, it reviewed implementation analysis presented by ICANN org and engaged in dialogue with the ccNSO Council in June 2026, which resulted in a set of clarifications by the ccNSO Council.
Resolved (2026.10.22.04), the Board adopts the ccNSO Recommended Policy, as set out in Part A of the Board Report, with the exception of the Section 7.8 regarding the Risk Treatment Appraisal and references to the Risk Treatment Appraisal in Sections 2.1.2, 7.3.1, 7.5, and 7.6.4.3 of the Board Report (collectively, the Risk Treatment Appraisal Recommendations).
Resolved (2026.10.22.05), the Board determines that Risk Treatment Appraisal Recommendations are not in the best interest of the ICANN community or of ICANN and therefore does not adopt them. Pursuant to the ICANN Bylaws, Annex B, Section, 15.b, the Board has developed a Board Statement stating its reasons for this determination. The Board directs the ICANN President and CEO, or his designee(s), to submit the Board Statement to the ccNSO Council.
Resolved (2026.10.22.06) the Board directs the ICANN President and CEO, or his des