Skip to main content

Accountability and Transparency Review: Highlights from Marrakech and Share Your Views

The third Accountability and Transparency Review Team (ATRT3) had a productive five days at ICANN65 in Marrakech.

Shortly before ICANN65 we shared our terms of reference and work plan with the Board and community. Achieving this milestone allowed us to use the meeting time to progress our data collection and analysis, socialize our scope and seek input from the community.

To kick the week off, we had a face-to-face meeting to review our data collection and analysis to-date and map areas of interdependency within our work party objectives. Our team is also mindful of possible areas of overlap between our scope items and other efforts within ICANN. For example, the community conversation about how to evolve the multistakeholder model, and the Cross Community Working Group on Enhancing ICANN Accountability Work Stream 2 recommendations and implementation. We are following these works closely to gain useful insights and avoid unnecessary duplication where possible.

We had several engagement sessions and interactions with various ICANN groups throughout the week. On behalf of our team, we'd like to thank everyone who took the time to meet with us during what is a hectic time for all. Your insights are critical in helping us to produce a report and recommendations that are fact-based, meaningful, and thorough.

Upcoming Community Survey

We hope to continue to gather information from the community in the coming weeks as we complete our data collection and draft our initial findings. We will publish a community survey to gain feedback on specific areas of focus identified in Marrakech and through our research to-date. Thank you in advance for openly sharing your views in the survey. Additionally, we are open to hearing your thoughts on accountability and transparency matters at any time as we continue our review. Your input is welcome to, or please, feel free to talk with any of our team members directly.

Our Timeline

We are mandated by ICANN's Bylaws to complete our review within one year (i.e. by April 2020). We are on track to meet this target. Our next face-to-face meeting will be 20 – 22 October 2019 in Singapore. We plan to use the time to finalize our draft final report, which will be published for public comment ahead of ICANN66 in Montreal.

Become an Observer

All of our meetings are open and available for observers to join. Send a request to to receive calendar invites to our meetings and to subscribe to our mailing list (read only).


The Accountability and Transparency Review is mandated by ICANN's Bylaws (Article 4, Section 4.6) to review "ICANN's execution of its commitment to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making reflect the public interest and are accountable to the Internet community."

Learn more about the ATRT3 Review 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"""" is not an IDN."