Evolving ICANN’s Multistakeholder Model: Continuing the Conversation and Preparing for ICANN65
Since ICANN64, the ICANN community has been engaged in conversations and contributing to the work on evolving ICANN's multistakeholder model. Most recently, more than 60 community members attended two webinars (14 May 2019, 15 May 2019), offering input on the issues that are hampering the effective and efficient functioning of ICANN's multistakeholder model.
The Evolving ICANN's Multistakeholder Model Public Comment period be summarized. A proposed final Issues List will be presented at a 12 June 2019 webinar during ICANN Prep Week. If you have not submitted comments, I encourage you to do so before the 4 June 2019 deadline.
The Issues List will be vetted against ongoing, community-led work streams to ensure there is no duplication of work that is already underway. The final Issues List will reflect the opportunities that we have to make our governance model more effective and efficient and to create more proactive, flexible, and nimble decision-making processes.
During the Prep Week webinar, I will also present the outline of a work plan to identify the "owners" of the respective issues. That is to say, which group (community, org, or Board) will be responsible for developing a solution or new approach to an issue. This will include a deadline for proposing a solution, which must fall within the ICANN Strategic Plan's fiscal years 2021-2025. The responsible group will also be asked to identify the resources it will need to deliver the solution or new approach.
How to prepare for ICANN65
At ICANN65, we will hold a session focused on mapping the final Issues List to the work plan. The ICANN community, org, and Board should be thinking about their respective planning processes and what they will need to contribute to the work plan should they be assigned one or more issues. The work plan will be completed by ICANN66 and will become part of ICANN's Operating and Financial Plan.
Continue to check this site for updates on activities and the Evolving ICANN's Multistakeholder Model process. You can subscribe to the publicly archived email list here.
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."