Skip to main content

Next steps in Evolving ICANN’s Multistakeholder Model: Developing a Work Plan for 2021-2025

Evolving ICANN's Mutlistakeholder Model (MSM) process is about strengthening our open and inclusive bottom-up model of governance and policy-making. As one part of ICANN's Strategic Objective on Governance in the Strategic Plan for Fiscal Years 2021-2025, the aim of Evolving ICANN's MSM's is to identify the work that we need to do to ensure that ICANN's MSM is working effectively and efficiently, and serving the ICANN community, the Internet and the world well into the future. To move this work forward, a public comment proceeding was opened today for input on the issues to be addressed in an eventual Work Plan.

At ICANN65 in Marrakech, the Evolving ICANN's MSM process turned its focus to developing a Work Plan for 2021 -2025. In the first phase of Evolving ICANN's MSM, the community identified a list of issues that it believes are hampering the more effective and efficient functioning of ICANN's MSM. The Issues List was prioritized and consolidated through community input. The completed work plan will become part of the Five-Year Operating Plan.

The work plan will capture, through community input, four items:

  1. The issues to be addressed.
  2. The entity who will develop and propose a solution to the issue (e.g. Advisory Committee, Supporting Organization, community, ICANN Board, ICANN organization).
  3. The projected time frame when the "owner" of that task will deliver a proposed solution within the Strategic Plan's Fiscal Years 2021-2025 time frame; and
  4. The resources the task owner will need to develop and propose a solution to the issue.

A number of community members at ICANN65 asked how we can ensure that the Evolving ICANN's MSM Work Plan would not duplicate other, ongoing work in the community. This is an important question given the current amount of ongoing work in the community, and the clear signal from the community that resources are stretched thin and volunteer burnout is real.

The best way to avoid duplicating work is to take stock of any work already undertaken in the community that could potentially address issues identified by the community. There is no point in reinventing the wheel. Also, we need to take into account work streams that are in the process of developing potential solutions to the issues identified by community input, such as the Third Accountability and Transparency Review and the Generic Names Supporting Organization's PDP 3.0 plan.

With some thoughtful analysis and working together, the community, Board and organization can create a Work Plan that will address these issues and improve the functioning of ICANN's MSM for years to come.

To follow the discussion on this topic, please join the Evolving ICANN's MSM mailing list here and look for updates on the project on this page.

Comments

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