Skip to main content
Resources

Approved Board Resolutions | Special Meeting of the ICANN Board

  1. Main Agenda:
    1. ICANN Allocates Emergency Financial Support for Continued Access to the Internet

 

  1. Main Agenda:

    1. ICANN Allocates Emergency Financial Support for Continued Access to the Internet

      Whereas, the ICANN Board has watched events unfold in Ukraine and the surrounding region that are tragic and profoundly troubling. Our hearts go out to the millions of people who are suffering from the violence as well as the related consequences that are impacting their lives.

      Whereas, the ICANN Board confirms that ICANN stands for a single, global, and interoperable Internet that serves all people around the world in exercising their fundamental human rights, including the human right to seek, receive, and impart information and ideas. It is through unimpeded access to the Internet and the free flow of information that people can gain knowledge and exposure to a diversity of viewpoints and information. This is especially critical when timely access to information and communication may be life-saving.

      Whereas, the ICANN Board affirms that ICANN's mission and the global public interest support that ICANN continues to uphold the multistakeholder stewardship role it has been entrusted. ICANN shall continue to act in a manner that supports the world's access to the Internet DNS and the unique identifiers.

      Whereas, the ICANN Board recognizes that during times of local crisis or emergency, ICANN has a longstanding practice of providing technical guidance and support to entities such as ccTLD operators and others working to maintain secure and stable operations of portions of the Internet's DNS. The ICANN Board also recognizes that access to funding to support such technical solutions is also essential.

      Resolved (2022.03.06.01), the ICANN Board directs the ICANN President and CEO to develop a process for how ICANN can provide financial assistance to support the security, stability and resiliency of the Internet's unique identifier systems, specifically for use in supporting mitigation measures where access to the Internet infrastructure is jeopardized by sudden, unexpected events beyond the control of the affected users.

      Resolved (2022.03.06.02), the ICANN Board allocates an initial sum of US$1,000,000 from ICANN's FY22 Budget to be used within the remainder of FY22 in order to provide financial assistance to support access to Internet infrastructure in emergency situations. The Board directs the ICANN President and CEO, or his designees, to promptly develop a proposal for distribution of these funds in support of ICANN's mission and distribute accordingly, taking into account fiduciary and legal obligations, and to report back to the Board on how these funds were utilized. The ICANN Board expects that the distribution directed today will focus on support for maintaining Internet access for users within Ukraine.

      Resolved (2022.03.06.03), the ICANN Board directs the ICANN President and CEO, or his designees, to advise the Board on whether and how ICANN can continue this effort beyond FY22 and be instilled in future budget years.

      Rationale for Resolutions 2022.03.06.01 – 2022.03.06.03

      The ICANN Board takes this action today in response to the events unfolding in Ukraine and the surrounding region that are tragic and profoundly troubling. Our hearts go out to the millions of people who are suffering from the violence as well as the related consequences that are impacting their lives.

      ICANN, as the entity entrusted with the global stewardship role of some key technical Internet functions, is in a unique position to uphold its mission and meet the expectation of all across the world that rely upon maintaining unimpeded access to the Internet and the free flow of information. This access allows people to gain knowledge and exposure to a diversity of viewpoints and information. The ICANN Board notes that groups across the ICANN community have recently issued statements regarding the value of a global and interoperable Internet and we thank the multistakeholder community for all of their efforts in supporting ICANN's mission.

      As ICANN's President and CEO recently stated: "ICANN is a facilitator of the security, stability, and resiliency of these identifiers with the objective of a single, global, interoperable Internet. . . . Essentially, ICANN has been built to ensure that the Internet works, not for its coordination role to be used to stop it from working."

      The ICANN Board recognizes that there have been and will unfortunately continue to be sudden and unexpected events that threaten access to the Internet's infrastructure. The impact of loss of access and widespread disconnection from the Internet is contrary to ICANN's mission, no matter the cause.

      The ICANN organization has a longstanding practice of coming to the technical support and aid of technical providers, such as ccTLD managers, to enable them to stay connected to the Internet's DNS and continue servicing their customers and region during times of crisis. The Board's action today goes a step further and directs ICANN org to also provide funding, as legally appropriate and within ICANN's mission, to support maintaining access to Internet infrastructure through these challenges.

      The Board is directing that for the remainder FY22, an initial sum of US$1,000,000, funded from ICANN's FY22 Budget, shall be made available to support mitigation measures where the access to the Internet is jeopardized by sudden, unexpected events beyond the control of the affected users. The ICANN President and CEO is directed to swiftly work with his team to identify how and to actually distribute these funds in alignment with ICANN's mission and in compliance with applicable laws and regulations. The ICANN President and CEO is to report back to the Board on how these funds were utilized. The Board expects that the FY22 distribution will focus on maintaining Internet infrastructure access for users within Ukraine. Further, the Board recognizes the value of providing this support on a longer-term basis, and directs the ICANN President and CEO to evaluate whether and how to instill this effort for future budget years.

      For clarity, the Board notes that though this type of financial support might be the sort of project that could be funded through the eventual grant-making mechanism anticipated by the recommendation of the Cross-Community Working Group on New gTLD Auction Proceeds, today's action does not access the Auction Proceeds fund in any way.

      This action is within ICANN's mission as it directly supports ICANN's core role, and is also within the global public interest. This action is anticipated to have a positive impact on the security, stability, and resiliency of the DNS as it will make funding available to maintain accessibility when operators or others might otherwise not have the resources to do so.

Published on 6 March 2022

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."