Skip to main content

ATRT3 Review Team Makes Progress at First Face-to-Face Meeting

The third Accountability and Transparency Review Team (ATRT3) had its first face-to-face meeting in Los Angeles on 3 – 5 April 2019.

The main objectives of the meeting were to:

  1. Develop and prioritize scope items for our review, as guided by ICANN's Bylaws (see Article 4, Section 4.6);
  2. Agree on our approach to work; and
  3. Make substantive progress towards developing our Terms of Reference and Work Plan.

We successfully met all of these objectives, and we'd like to thank our review team colleagues for their hard work and important contributions. The meeting archive and associated materials are available here.

Our Scope and Approach to Work

After identifying and prioritizing our scope items through a series of brainstorming exercises, the team agreed to conduct our work in four work parties: Board, Governmental Advisory Committee (GAC), Reviews, and Community. Each work party will finalize the detailed objectives of their work in the coming weeks. Work party objectives will be guided by ICANN's Bylaws to include, at a high level:

  • Board: Assessing and improving Board governance.
  • GAC: Assessing the role and effectiveness of the GAC's interaction with the Board and with the broader ICANN community.
  • Reviews: Assessing and improving the processes by which ICANN receives public input, and assessment of ICANN's implementation of ATRT2 recommendations.
  • Community: Assessing the extent to which ICANN's decisions are supported and accepted by the Internet community, and assessing the policy development process to facilitate enhanced cross community.

As they are finalized, work party resource requests will be tracked here, where you can also see membership details of each work party.

Next Steps

We are on track to adopt our Terms of Reference and Work Plan by the Board-directed timeline of within 60 days of the face-to-face meeting, i.e. by 5 June 2019. Once adopted, these items will be publicly posted on our wiki, as well as sent to the ICANN Board and Supporting Organizations and Advisory Committees.

We plan to socialize our Terms of Reference and scope during ICANN65 in Marrakech, where we will also seek input from the community to help us shape our findings and draft recommendations. Community input is key to the success of this review. Please, do let us know via our mailing list at (publicly archived) if you would like to set up a consultation with us in Marrakech. We welcome your feedback to this mailing list any time throughout our work.

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 ATRT review team 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 ATRT3 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."