ICANN Resolutions » FY23 IANA Operating Plan and Budget
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, the draft FY23 IANA Operating Plan and Budget was posted for public comment in accordance with the Bylaws on 15 September 2021.
Whereas, comments received through the public comment process were reviewed and responded to and provided to the Board Finance Committee (BFC) for review and consideration. In addition, all public comments have been taken into consideration, and where appropriate and feasible, have been incorporated into a final FY23 IANA Operating Plan and Budget.
Whereas, in accordance with ICANN Bylaws Article 22, Section 22.4(b), ICANN shall require PTI to submit the PTI Budget to ICANN as an input prior to and for the purpose of being included in the proposed Operation Plan and ICANN Budget. The Adopted FY23 PTI Budget is included as input to the IANA Operating Plan and Budget.
Whereas, per the ICANN Bylaws, the IANA Operating Plan and Budget is to be adopted by the ICANN Board and then posted on the ICANN website.
Resolved (2022.02.24.04), the Board adopts the FY23 IANA Operating Plan and Budget.
In accordance with Article 22, Section 22.4 of the ICANN Bylaws, the Board is to adopt an annual IANA budget and publish it on the ICANN website. On 15 September 2021, the drafts of the FY23 PTI Operating Plan and Budget and the FY23 IANA Operating Plan and Budget were posted for public comment. The PTI Board approved the FY23 PTI Operating Plan and Budget on 13 December 2021, and the PTI Budget was received as input into the FY23 IANA Operating Plan and Budget.
The FY23 PTI Operating Plan and Budget and the draft FY23 IANA Operating Plan and Budget are based on numerous discussions with members of ICANN org and the ICANN Community, including extensive consultations with ICANN Supporting Organizations, Advisory Committees, and other stakeholder groups throughout the prior several months. In July 2021, preliminary consultations were conducted with stakeholders on FY23 priorities for Public Technical Identifiers (PTI). These engagements were in the form of discussions with Supporting Organizations and Advisory Committees, as well as the gTLD Registries Stakeholder Group, Regional Internet Registries and IETF leadership. In addition, two Community Webinars were held on 27 July 2021.
All comments received through the Public Comment proceeding were considered in relation to the FY23 IANA Operating Plan and Budget. Where feasible and appropriate these inputs have been incorporated into the final FY23 IANA Operating Plan and Budget proposed for adoption.
Adopting the FY23 IANA Operating Plan and Budget will have a positive impact on ICANN in that it provides a proper framework by which the IANA services will be performed, which also provides the basis for the organization to be held accountable in a transparent manner.
This decision is in the public interest and within ICANN's mission, as it is fully consistent with ICANN's strategic and operational plans, and the results of which in fact allow ICANN to satisfy its mission.
This decision will have a fiscal impact on ICANN and the Community as is intended. This should have a positive impact on the security, stability and resiliency of the domain name system (DNS) with respect to any funding that is dedicated to those aspects of the DNS.
This is an Organizational Administrative Function that has already been subject to public comment as noted above.