Skip to main content

Final Proposed FY19 Operating Plan and Budget

Today, we published the final proposed FY19 Operating Plan and Budget and submitted it to the ICANN Board for consideration at the meeting on 30 May 2018. This is an important step in the process to ensure transparency so that you – and the rest of the ICANN community – can see what exactly is sent to the Board before it is adopted.

I want to thank you for your comments and productive discussions on the budget. I was very pleased that we received over 185 comments through the public comment process, in addition to the many productive discussions we had, especially during ICANN61.

As a result of your feedback and comments, we've made a few suggested changes to the budget.

The Fellowship Program received an increase from 30 to 45 seats per meeting, based on your feedback. In addition, the ICANN organization will be seeking community feedback on the entire Fellowship Program in the next few months.

We heard your concerns about the reduced Community Regional Outreach Program (CROP) funding, and as a result, its funding for outreach is reinstated at $50,000.

We will also be progressively decreasing funding for the ICANN Wiki from $66,000 in FY19 to a commitment of $33,000 for FY20, based on your comments.

In addition, budget was reallocated for the General Data Protection Regulation (GDPR), and data protection and privacy in FY19, as it is prudent planning to anticipate increased expenses next year.

This year was the first time we merged the Additional Budget Request process with the Operating Plan and Budget process. In Document 2 [PDF, 621 KB] on page 26 you can see what additional budget items were approved.

We are also holding a webinar on 24 May at 14:00 UTC, where you can learn more about these changes and ask questions. Here is the link to join: https://participate.icann.org/finance/.

I encourage you to read the Executive Summary in Document 1 [PDF, 305 KB].

Thank you again for contributing your comments and feedback. It is a testament to the multistakeholder model in action.

Comments

    Shah Zahidur Rahman  04:03 UTC on 22 May 2018

    Appreciate this operating plan and budget.

    judith hellerstein  12:58 UTC on 22 May 2018

    Can you have a second time for this webinar as it is at the same time as the CCWG-Auction Proceeds? Thanks

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