Skip to main content

A Conversation About Evolving The Effectiveness of Our Multistakeholder Model

At ICANN63 in Barcelona, Spain, the ICANN Board asked the community for feedback on Strategic Objective #2 concerning ICANN's governance in the draft ICANN Strategic Plan for Fiscal Years 2021-2025. Specifically, the community was asked how to improve the effectiveness of ICANN's multistakeholder model (MSM) of governance. Based on the community's response at ICANN63, we held a session at ICANN64 to continue the conversation. I was asked to serve as an independent facilitator to build on the conversation that began at ICANN63.

On 14 March 2019 in Kobe, Japan, that conversation began in earnest about how we can evolve our multistakeholder model to make it more effective. The stated goals of the conversation are: 1) to develop a list of issues that challenge the effectiveness of ICANN's multistakeholder model; and 2) to create a work plan based on those issues that will become part of ICANN's Operational Plan in December 2019.

The energy in the session was palpable. Voices from long-time ICANN community members, as well as more recent members, contributed to our issue identification exercise. The comments offered were candid and clear. Statements ranged over a number of topics from how ICANN was originally set up, to how incentives don't exist to create conditions for compromise, to the importance of informed policy-making, and the need for greater participation of NextGen members in the work of the ICANN community.

Community members also shared their thinking on this topic in the sessions between the ICANN Board and the Supporting Organizations and Advisory Committees (SO/ACs), as well as some constituency groups, which were held earlier in the week at ICANN63. Listening to community members from across the stakeholder spectrum, there was clear and consistent recognition of the "pain points" in the system: decision-making and policy processes take too long, resources are stretched too thin, there are too many work streams, and volunteers are feeling exhausted and burned-out.

It is often said that the first step in solving a problem is recognizing that you have one. The first step has been taken.

For the ICANN64 session, we began the exercise of creating a list of issues that the community believes must be addressed to improve the effectiveness of our multistakeholder model. I want to thank all of you who offered your thoughts. I have captured those inputs, along with the community member inputs made during the community sessions with the ICANN Board. That information is included in the public comment period.

Next Steps

  1. A Public Comment period to continue developing the issues list is being launched today and will be open for forty days. The Public Comment proceeding can be found here. Comments will be reviewed and incorporated into the issues list and an updated issues list will be published prior to ICANN65 in Marrakech, Morocco.
  2. Webinars to review the final issues list and to develop the work plan will be held in mid-May and in June, during Prep Week for ICANN65 (details to come).

Continue to check this site for updates on activities and the Evolving MSM process. If you want to share your thoughts on any of these materials, you can post them to this publicly archived email list, which you can subscribe to here. I will also be sharing my updates to this list.


    fixoyexcv  02:54 UTC on 21 September 2019

    nice post

    fixoyexcv  02:55 UTC on 21 September 2019

    []preinsurance[/url] [preinsurance](

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