Skip to main content

Thoughts Heading into Los Angeles

The CCWG-Accountability chairs recently observed in a blog post how critical it is that we all keep up our energy and momentum going into the next CCWG-Accountability face-to-face meeting in Los Angeles on 25 and 26 September. I could not agree more. The CCWG-Accountability deserves much applause for its tremendous and impressive work leading to the 2nd Draft Proposal, this most recent public comment period and for its commitment to bring this process to a successful conclusion. It hasn't always been easy. The Board has tried to act in good faith throughout this process, weighing the most appropriate and helpful times to contribute, and in what manner in this unprecedented community effort.

The CCWG meeting in Los Angeles comes at a critical time. While it's easy to analyze the areas where consensus still needs to be reached, it is important to also recognize the many elements of the accountability proposal that have reached broad support. In studying the public comments, we agree with the CCWG that there are many areas of agreement and we look forward to contributing as a part of the community to refine and build upon the 2nd Draft Proposal to create the necessary enhancements to ICANN's accountability.

It is more important to get this work done right than it is to get it done quickly. However, should the group not focus on the core accountability requirements to fill the backstop role of the U.S. Government, I fear that it will drive the transition towards delay or even possible failure after being so close to completion. A lot of work has been done by our community, in the CCWG and at the ICG, and the crafting of these two dynamic proposals has been a testament to the capability of the multistakeholder community – we must not let this moment pass.

I am personally looking forward to using this time in Los Angeles to contribute constructively to the work of the CCWG and remain confident we will continue to enhance what we have built together.


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