Skip to main content

Empowered Community Powers Triggered: FY18 Operating Plan and Budget, and Updates to Five-Year Operating Plan

On 24 June 2017, the ICANN Board adopted ICANN's FY18 Operating Plan and Budget, the FY18 IANA Budget, and updates to the Five-Year Operating Plan. Under ICANN's post-IANA Stewardship Transition Bylaws, the Empowered Community has the power to consider and, if they choose, to reject these documents before they go into effect.

ICANN's FY18 Operating Plan and Budget, the FY18 IANA Budget, and updates to the Five-Year Operating Plan are the result of 11 months of collaborative work by the organization, community, PTI Board, and ICANN Board Finance Committee. They include:

  • Highlights of all ICANN Operations
  • Overview of ICANN's FY18 Budget
  • Detailed FY18 Operating Plan
  • Detailed descriptions of portfolios of activities to support the goals and objectives described in the ICANN Strategic Plan for Fiscal Years 2016 –2020, and the updated Five-Year Operating Plan
  • Detailed lists of projects for each portfolio, with project-level budgeted costs
  • Summary of changes from the Draft FY18 Operating Plan and Budget

The community's continuously increasing participation in the planning process is a cornerstone of ICANN's transparency and accountability to the global multistakeholder community. ICANN thanks all community members who contributed to the development of the budget. Budget documents for FY18 and previous years are published here.

In accordance with the ICANN Bylaws Annex D, Section 6.2, the Empowered Community now has the opportunity to trigger the following three actions:

  • Rejection of the ICANN FY18 Operating Plan and Budget
  • Rejection of the FY18 IANA Budget
  • Rejection of updates to the Five-Year Operating Plan

Each of these documents will come into effect only after giving the Empowered Community time to consider whether it will raise a petition rejecting the budgets and/or operating plans. Decisional Participants of the Empowered Community have 28 days to bring forth a petition to reject any of these documents. To address concerns raised by a representative of the Empowered Community Administration on the explanation of timing, for clarification, under Annex D, Section 2 of the Bylaws, there is a 21-day period for any Decisional Participant to raise a petition to reject the documents, followed by a 7-day period to obtain support for that petition. For more information on the Petition Process, refer to the ICANN Bylaws.

If the Empowered Community does not raise a petition, both budgets will go into effect on 22 July 2017. In accordance with the ICANN Bylaws Sections 22.4(a)(ix) and 22.4(b)(ix), until the budgets are adopted, including throughout an Empowered Community Petition Process, both IANA and ICANN will operate under separate Caretaker Budgets during the period of FY18.

With the FY18 Caretaker Budget in effect, the ICANN organization will manage with limited operational impact. As noted in the FY18 Operating Plan and Budget, the ICANN FY18 Caretaker Budget prohibits ICANN from posting new positions and reduces travel and professional fees by 10%. The IANA Caretaker Budget is equal to the FY18 IANA Budget to ensure the stability of the IANA functions.

What Is the Empowered Community?

The Empowered Community is the mechanism through which ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) can organize under California law to legally enforce community powers. The community powers and rules that govern the Empowered Community are defined in the ICANN Articles of Incorporation and Bylaws.

Who Can Participate in the Empowered Community?

All of ICANN's SOs, as well as the At-Large and Governmental ACs, are Decisional Participants, and can participate in the Empowered Community, including:

  • Address Supporting Organization (ASO)
  • Country Code Names Supporting Organization (ccNSO)
  • Generic Names Supporting Organization (GNSO)
  • At-Large Advisory Committee (ALAC)
  • Governmental Advisory Committee (GAC)

How Does the Empowered Community Use Its powers?

The Empowered Community has an escalation process to reject ICANN's FY18 Operating Plan and Budget, the FY18 IANA Budget, and updates to the Five-Year Operating Plan. This escalation process gives SOs and ACs opportunities to discuss solutions with the ICANN Board.

For more information on the Empowered Community, click here.
For more information on ongoing Empowered Community petitions, click here.
For more information on upcoming Empowered Community opportunities, click here.

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