Skip to main content

ATRT3 Brussels Meeting Recap and Looking Ahead to Cancún

Atrt3 brussels 1593x885 19feb20 en

From 7 to 9 February 2020, the third Accountability and Transparency Review Team (ATRT3) held a face-to-face meeting at the ICANN office in Brussels, Belgium. We had a nearly full-house turnout of review team members who actively participated in the meeting either in-person or remotely. We also had a number of dedicated observers who followed our work remotely throughout the weekend. We thank you all for your commitment and contributions.

Below are some highlights from our discussions. Records of the meeting are posted here. We encourage you to dig into those for more detail on the topics that are of particular interest to you.

Day One

We spent the first day analyzing each of the sixteen public comments we received on our draft report. Thank you to all for your input. Our final report will include a detailed analysis of the comments, including an explanation of why and how we have incorporated each comment into the final report, or why and how we chose not to. The ATRT3's working draft of this analysis is posted to our wiki here.

Day Two

On day two, we focused much of our discussion around the issues of prioritization and reviews. These are two areas of our draft report that we had highlighted as critical for receiving input on. Based on our analysis of public comments, we significantly modified these areas of our report. Although the revisions are in draft form, we made considerable progress and look forward to coming to consensus on our approach to these items in the coming weeks.

We also carried out a preliminary impact analysis on a number of our draft recommendations. We will undertake this exercise on all our draft suggestions or recommendations, to ensure that our recommendations meet the requirements as called for by Section 4.2 of the Operating Standards for Specific Reviews (Operating Standards).

Day Three

On our final day, we completed a prioritization exercise on our draft suggestions and recommendations. We agreed by consensus how each of these will be prioritized in our final report based on the requirements in the Operating Standards. We also spent a bit of time planning our approach to work towards the Cancún meeting where we will be making final adjustments to our report.

Looking Ahead to Cancún

We will be holding a face-to-face meeting on 5 and 6 March in Cancún, Mexico, ahead of ICANN67. Our goal for this meeting is to reach consensus on our final recommendations. We will be communicating our progress during a community engagement session, details of which will be posted to the ICANN67 meeting schedule once available.

Between now and the meeting in Cancún, we will continue our regular weekly plenary meetings, all of which are open for observers to join. We look forward to completing our work and submitting our final report to the ICANN Board on schedule in April 2020.

Comments

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