Skip to main content

The Draft FY19 Operating Plan and Budget

Each year, preparing our proposed budget for the next financial year is one of the most important responsibilities ICANN organization has as a not-for-profit operating in the public interest.

Long-term financial planning and fiscal responsibility is important, and the ICANN org, the Board, and the community must work together on both. A critical part of this process is that the budget goes through public comment and that you, the community, have the opportunity to provide feedback and inform the budget before it is finalized.

ICANN's mission and the various commitments it has accumulated over the years, from the IANA Functions, technical work, and policy development support to ICANN meetings, reviews, and community needs, have meant an increased workload for the ICANN org and an increased amount of personnel and other resources to meet that workload.

Historically, the budget has been able to accommodate an increased workload, thanks to continued growth in funding.

Now, however, we cannot afford to continue this steady increase. The actual funding for FY18 is below the FY18 budget, and we expect this trend to continue. Funding for FY19 is $138 million, which is below the FY18 budget of $143 million by $5 million. This means ICANN needs to carefully plan and prioritize the work to support our mission and keep expenses within its available budget. I know this may not be an easy thing to do, but it's the right thing to do.

I know that we've all felt this increase in the volume of work. I recognize ICANN org could have done better in its financial long-term planning, and I know many of you agree based on previous public comments, such as the recent one on the reserve fund, as well as previous budget public comments, and I thank you for that. Now is the time, and we need your help, feedback, and input to finalize the budget.

It is for the multistakeholder community to decide not just what work gets done and when, but also to help keep expenses within ICANN's means and focused on our mission. The ICANN org exists to support the community's work and ICANN's mission.

To better allocate resources, the ICANN org looks to the community to provide feedback on what should be prioritized, so that the org can provide the resources and support accordingly. The draft budget includes some proposed reduction of activities, including decreased or delayed potential implementation of projects or activities, engagement, and community support. It also includes $8.5 million in savings within the ICANN org, which are achieved through optimized internal processes and procedures.

In addition, this year we've added new material to help you participate, based on your previous feedback. This includes a high-level plan for FY20, so that you see what's beyond FY19, and six modules that provide a specific focus by topic: Contractual Compliance and Consumer Safeguards, Direct Policy Support, DNS Marketplace and Identifier Ecosystem, Technology and DNS security, Engagement, and Reviews.

The planned projects in FY19 continue to focus on ICANN's technical mission and accountability and transparency. In addition to supporting the ongoing community work, this includes projects such as the Information Transparency Initiative, which seeks to improve ICANN's document governance and content management, ultimately making it easier for the community to find information on our website.

Also in FY19, the community will come together to create the next strategic plan for 2021 and beyond. This will be an important moment for us all to work together on a long-term plan that supports ICANN's mission within our available resources.

I know that prioritizing ICANN's work and being fiscally responsible is something the Board, community, and ICANN org all care deeply about. This is the right time to plan for the long-term and to prioritize ICANN's work to support its mission. It is for the multistakeholder community to decide. You, as the Empowered Community, are also entitled to reject the budget outright.

We want and need your feedback and input.

I look forward to productive discussions about this proposed budget between now and March. Please take action and share your comments during the public comment process.


    Dmitry Belyavskiy  05:22 UTC on 22 February 2018

    As for now, there is only one ICANN representative in such a big region as Central-Eastern Europe. I think this huge region needs more people to perform all the necessary ICANN-related activities. Till previous year there were 2 ICANN people who were active enough and were able to involve people from region into ICANN activities as part of multistakeholder community. I am sure that decreasing number of ICANN staff in the region will significantly decrease involvement of stakeholders into ICANN processes. I also want strongly disagree about proposed reducing number of the fellowship program as it provides possibility to people from relatively poor regions to become involved in ICANN processed and practices.

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"""" is not an IDN."