Skip to main content

Security, Stability and Resiliency of the Domain Name System (DNS) Review Team (SSR2): Follow Our Progress

Ssr2 review team icann58 691x461 26apr17 en

SSR2 Review Team members at ICANN58 (L-R): James Gannon, Ramkrishna Pariyar, Žarko Kecić, Denise Michel, Jabhera Matogoro, Geoff Huston, Kerry-Ann Barrett, Kaveh Ranjbar, Emily Taylor, Alain Aina, Boban Krsic, Cathy Handley, Eric Osterweil, Mohamad Amin Hasbini. Not pictured: Noorul Ameen, Don M. Blumenthal.

On behalf of the SSR2 Review Team we'd like to update you on our work so far and tell you how you can get involved. The SSR2 Review Team is reviewing security, operational stability and resiliency matters relating to ICANN's coordination of the Internet's system of unique identifiers. (Our detailed mandate can be found here.)

Here are some highlights from the Review Team's work so far:

  • At ICANN58 we met face-to-face for the first time and held a community engagement session. Many thanks to everyone who came to this session and contributed to the discussion.
  • In March, we announced our leadership selections, agreeing by consensus to leadership by three co-chairs.
  • We are currently drafting our work plan and terms of reference, which we expect to finalize and publish in the coming weeks – watch the SSR2 wiki.
  • As mandated by ICANN's Bylaws, we are reviewing the first SSR Review Team's recommendations. We are in the information-gathering phase, assessing the status and impact of these recommendations.
  • We are also doing a lot of "homework" – reviewing a substantial number of reports and background materials – to prepare for our in-depth work.

Our next face-to-face meeting will be in Madrid on 14 and 15 May, just after the ICANN DNS Symposium. Information on how to observe this meeting in person or remotely is included below.

We need you to help us carry out a successful review!

We encourage contributions and comments from the community throughout the review process. Please give us input on ICANN's role and the issues you see facing the security, stability and resiliency of the DNS.

Here's how you can get involved:

  • Share your input with us. Send an email to (Note: This is a publicly archived mailing list.)
  • Become an observer. Review Team meetings, whether in person or online, have a dedicated Adobe Connect room for observers to participate. Learn more.
  • Attend the face-to-face meeting in Madrid. The agenda and remote participation information will be posted here. Check back regularly for updates.
  • Follow our work! Bookmark the SSR2 wiki to make sure you stay informed of our progress and upcoming meetings.


    doni  18:50 UTC on 29 April 2017

    it's sound good progress

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