Skip to main content

Working Together Through The Last Mile

I'd like to thank everyone who has participated in both the CCWG briefing to the ICANN Board, and the CCWG and ICANN board dialogue. All of our dialogues over the past months have been illuminating, challenging and in my opinion, an important and true testament to the multistakeholder model as we work toward the IANA Stewardship Transition.

We support the important improvements for ICANN's accountability contained in the CCWG-Accountability's 2nd Draft Proposal. We endorse the goal of enforceability of these accountability mechanisms, and we believe that it is possible to implement the key elements of the proposal. We want to work together to achieve the elements of the proposal within the community's timeline while meeting the NTIA requirements.

As we enter the final days of the Public Comment period, the Board wants to be completely clear on our position. We are in agreement on key concepts set forward in the CCWG's proposal, for example:

  • Fundamental bylaws.
  • Specific requirements for empowering the community into the bylaws adoption process.
  • IRP enhancements.
  • Board and director removal.
  • ICANN's mission and core values.
  • Strengthening requirements for empowering the community in the budget, operational and strategic planning process.
  • The incorporation of the Affirmation of Commitments Reviews into ICANN bylaws.
  • Community ability to enforce the accountability mechanisms in the bylaws.

We have suggestions on how these could be operationalized. With regards to the mechanisms for community enforceability, where the current proposal still warrants much detail that may not be achievable we have a suggestion on how to deliver on it in a stable way, as increased enforceability must not open up questions of, for example, capture or diminishing of checks and balances.

Let's work together on operationalizing the above principles on which we agree. Once again, we are committed to providing more detail on how these ideas can be operationalized in a way that they can be implemented within the community identified time frame for the transition, as well as have sufficient tested grounds to not result in unintended consequences.

During last night's discussion we shared this feedback. It was a lot of information to digest in a call (notes around opening remarks, notes around 10 points), and we appreciate everyone giving our advice consideration. We are committed to submitting our comments into the Public Comment process in the next few days, and we look forward to the working with the community on further details.

It is critical that we work together to build enhanced accountability for ICANN and continue to refine and flesh out details of the impressive work already done by the community and complete the IANA Stewardship Transition.


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