Skip to main content

Don't Miss These Reviews Sessions at ICANN60

There are a number of important ICANN review-related sessions scheduled during ICANN60. Read the session highlights below and be sure to mark your calendar for those that interest you. Click the links to learn more about each session, including how to join remotely.

  • Competition, Consumer Trust, and Consumer Choice (CCT) Review

    Interested in the future of the New Generic Top-Level Domains (gTLD) Program? The CCT Review Team is examining the effects of the program on competition, consumer trust and consumer choice. Join the team's community engagement session on 29 October to share your input and ask questions directly to the review team. You can also choose to observe its face-to-face meeting on 27 October, when the team will advance its work and refine its recommendations.

  • Second Security, Stability, and Resiliency of the Domain Name System (SSR2) Review

    Do you want to find out more about security, stability, and resiliency matters relating to ICANN's coordination of the Internet's system of unique identifiers? Join the SSR2 Review Team community engagement session on 29 October to learn about progress and provide input to the team. You may also observe the SSR2 Review Team two-day face-to-face meeting, on 27 October and 3 November, when the team will progress its work in the five key areas of the review.

  • Second Nominating Committee (NomCom2) Review

    The NomCom plays an important role in appointing key positions within ICANN's structure. Join the NomCom Review Update by the Independent Examiner Session on 1 November to learn about the current NomCom Review. To participate in the NomCom2 Review survey, click here.

  • Contribute to Development of the Operating Standards

    Operating Standards will guide how ICANN specific reviews are conducted. On 30 October, join the Cross-Community Session: Operating Standards for Specific Reviews to learn how you can contribute to their development. The session will bring together community leaders, ICANN Board members, and the wider ICANN community to discuss the draft Operating Standards, currently open for public comment.

Check out the ICANN60 schedule to view the complete list of sessions and create your custom schedule. See you in Abu Dhabi!


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