Skip to main content
Resources

Approved Board Resolutions | Special Meeting of the ICANN Board

  1. Consent Agenda:
    1. September 2022 ICANN75 Meeting Contracting
    2. March 2023 ICANN76 Meeting Venue Contracting
  2. Main Agenda:
    1. FY21-25 Operating and Financial Plan and FY21 Operating Plan and Budget Approval

 

  1. Consent Agenda:

    1. September 2022 ICANN75 Meeting Contracting1

      Whereas, ICANN intends to hold its third Public Meeting of 2022 in the Asia Pacific region.

      Whereas, ICANN organization has completed a thorough review of the available venues in the Asia Pacific region and finds the one in Kuala Lumpur, Malaysia to be the most suitable.

      Resolved (2020.05.07.01a), 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 and hotels for the September 2022 ICANN Public Meeting in Kuala Lumpur, Malaysia, in an amount not to exceed [REDACTED FOR NEGOTIATION PURPOSES].

      Resolved (2020.05.07.01b), specific items within 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 that the confidential information may be released.

      Rationale for Resolution 2020.05.07.01a – 2020.05.07.01b

      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 17-22 September 2022. Following a search and evaluation of available venues, the organization identified Kuala Lumpur, Malaysia as a suitable location for the ICANN Public Meeting.

      The organization performed a thorough analysis of the available locations and prepared a paper to identify those that met the Meeting Location Selection Criteria (see http://meetings.icann.org/location-selection-criteria). Based on the proposals and analysis, ICANN has identified Malaysia, Kuala Lumpur as the location for ICANN75. Selection of this Asia Pacific location adheres to the geographic rotation guidelines established by the Meeting Strategy Working Group.

      The Board reviewed the organization's briefing for hosting the meeting in Kuala Lumpur, Malaysia 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 September 2022 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 DNS.

      This is an Organizational Administrative function that does not require public comment.

    2. March 2023 ICANN76 Meeting Venue Contracting

      Whereas, ICANN intends to hold its first Public Meeting of 2023 in the Latin America/Caribbean region.

      Whereas, ICANN organization has completed a thorough review of the available venues in the Latin America/Caribbean region and finds the one in Cancún, Mexico to be the most suitable.

      Resolved (2020.05.07.02), 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 2023 ICANN Public Meeting in Cancún, Mexico, in an amount not to exceed [REDACTED FOR NEGOTIATION PURPOSES].

      Resolved (2020.05.07.03), specific items within 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 that the confidential information may be released.

      Rationale for Resolutions 2020.05.07.02 – 2020.05.07.03

      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. ICANN76 is scheduled for 11-16 March 2023. Following a search and evaluation of available venues, the organization identified Cancún, Mexico as a suitable location for the ICANN Public Meeting.

      The organization performed a thorough analysis of the available locations and prepared a paper to identify those that met the Meeting Location Selection Criteria (see http://meetings.icann.org/location-selection-criteria). Based on the proposals and analysis, ICANN has identified Cancún, Mexico as the location for ICANN76. Selection of this Latin America/Caribbean location adheres to the geographic rotation guidelines established by the Meeting Strategy Working Group.

      The Board reviewed the organization's briefing for hosting the meeting in Cancún, Mexico 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 2023 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 DNS.

      This is an Organizational Administrative function that does not require public comment.

  2. Main Agenda:

    1. FY21-25 Operating and Financial Plan and FY21 Operating Plan and Budget Approval

      Whereas, the draft FY21 Operating Plan and Budget and draft FY21-25 Operating and Financial Plan were posted for public comment in accordance with the Bylaws on 20 December 2019.

      Whereas, comments received through the public comment process were discussed by a few Board members and ICANN organization during a remote public session during ICANN 67 and during conference calls with representatives of the bodies that submitted public comments to help ensure the comments were adequately understood and appropriate consideration was given to them.

      Whereas, the public comments received were considered and revisions were applied as appropriate to the draft FY21 Operating Plan and Budget and the draft FY21-25 Operating and Financial Plan.

      Whereas, in addition to the public comment process, ICANN organization actively solicited community feedback and consultation with the ICANN Community by other means, including a remote public session during ICANN67.

      Whereas, the COVID-19 pandemic has created a situation of economic uncertainty, potentially affecting ICANN's current and planned work, leading to the development of new plans that are reflected in ICANN's Proposed FY21 Operating Plan and Budget and Proposed FY21-25 Operating and Financial Plan.

      Whereas, at each of its recent regularly scheduled meetings, the Board Finance Committee (BFC) has discussed, and guided ICANN organization on the development of the final FY21 ICANN Operating Plan and Budget and final FY21-25 Operating and Financial Plan.

      Whereas, the BFC reviewed and discussed suggested changes to the ICANN FY21 Operating Plan and Budget and FY21-25 Operating and Financial Plan resulting from public comment and consultations, and the changes resulting of the COVID-19 pandemic, and recommended that the Board approve the final FY21 Operating Plan and Budget and final FY21-25 Operating and Financial Plan.

      Whereas, the BFC and the Board have received from ICANN organization an overview of the topics discussed and the questions addressed during the two webinars that were held on the new plans updated after the public comment process concluded, which did not require that any change be made to the proposed new plans.

      Whereas, per section 3.9 of the 2001, 2009 and 2013 Registrar Accreditation Agreements, respectively, the Board is to establish the Registrar Variable Accreditation Fees, which must be established to develop the annual budget.

      Whereas, the description of the Registrar fees, including the recommended Registrar Variable Accreditation Fees, for FY21 has been included in the FY21 Operating Plan and Budget.

      Resolved (2020.05.07.04), the Board adopts the FY21 ICANN Operating Plan and Budget, including the FY21 ICANN Caretaker Budget that would be in effect in the event the FY21 ICANN Operating Plan and Budget is not in effect at the beginning of FY21.

      Resolved (2020.05.07.05), the Board adopts the FY21-25 Operating and Financial Plan which describes the activities ICANN org will undertake and the resources needed to achieve the ICANN Board adopted ICANN's Strategic Plan for Fiscal Years 2021-2025.

      Rationale for Resolutions 2020.05.07.04 – 2020.05.07.05

      In accordance with Article 22, Section 22.4 of the ICANN Bylaws, the Board is to adopt an annual budget and publish it on the ICANN website. On 20 December 2019, drafts of the ICANN FY21 Operating Plan and Budget and the FY21-25 Operating and Financial Plan were posted for public comment. The Public Technical Identifiers (PTI) Board approved the PTI Budget on 08 January 2020, and the PTI Budget was received as input into the FY21 IANA Budget.

      The published draft ICANN FY21 Operating Plan and Budget and the FY21 IANA Budget were based on numerous discussions with members of ICANN organization and the ICANN community, including extensive consultations with ICANN Supporting Organizations, Advisory Committees, and other stakeholder groups throughout the prior several months.

      The comments received from the public comment process resulted in no revisions to the 20 December 2020 draft ICANN FY21 Operating Plan and Budget, however, since concluding the Public Comment process, the economic impact of the COVID-19 pandemic has had a significant and ongoing impact on the world. ICANN org has recently developed new plans that are reflected in the Proposed FY21-25 Operating and Financial Plan and Proposed FY21 Operating Plan and Budget. As the changes reflected in the new plans were defined after the public comment process was concluded, the ICANN organization organized two webinars on 28 April 2020 to present to the attendees the new plans and highlight the changes that had been made to the draft documents published in December 2019. The webinars were well attended, by more than 100 different participants, as well by most BFC members. The topics addressed, questions asked and answered, and the input received during two webinars did not lead to any change to the new plans presented.

      The following consultation activities were carried out:

      • 12 September 2019 and 13 September 2019 – Community webinar on the FY21 Planning Schedule.

      • 08 March 2020, the comments received through the public comment process were discussed by Board members and ICANN organization members during a remote public session on public comments during ICANN 67 with representatives of the ICANN bodies that submitted them to help ensure the comments were adequately understood and appropriate consideration was given to them.

      • In addition to the public comment process, ICANN actively solicited community feedback and consultation with the ICANN community by other means, including remote public sessions during ICANN67.

      • 28 April 2020, Community webinars on the new projections that are contained in the Proposed for Adoption FY21-25 Operating and Financial Plan and Proposed for Adoption FY21 Operating Plan and Budget plans.

      All comments received in all manners were considered in developing the final ICANN FY21 Operating Plan and Budget and the FY21-25 Operating and Financial Plan. Where feasible and appropriate these inputs have been incorporated into the final FY21 Operating Plan and Budget and the FY21-25 Operating and Financial Plan proposed for adoption.

      In addition to the day-to-day operational requirements, the FY21 Operating Plan and Budget includes the FY21 new gTLD budget items and amounts allocated to various FY21 budget requests received from community leadership. The FY21 Operating Plan and Budget also discloses financial information on the New gTLD Program, relative to expenses, funding and net remaining funds. Further, because the Registrar Variable Accreditation Fee is key to the development of the budget, the FY21 Operating Plan and Budget sets out and establishes those fees, which are consistent with recent years, and will be reviewed for approval by the Registrars.

      The FY21 Operating Plan and Budget and the FY21-25 Operating and Financial Plan, all will have a positive impact on ICANN in that together they provide a proper framework by which ICANN will be managed and operated, 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 org 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.

Published on 11 May 2020
Consent Agenda Item 1.a. republished on 3 August 2020. See footnote 1.


1 This resolution was republished on 3 August 2020 to release certain confidential negotiation information previously redacted from the Board resolution and rationale.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."