Skip to main content

Second Security, Stability, and Resiliency (SSR2) Review Team Update

The second Security, Stability, and Resiliency (SSR2) Review Team recently met for three days in Los Angeles.

During the meeting, we completed our assessment of ICANN's implementation of SSR1 recommendations from 2012, and we detailed the scope items for our remaining areas of focus, as guided by ICANN's Bylaws (see Article 4, Section 4.6):

  • ICANN's key security, stability, and resiliency activities.
  • Activities that impact the SSR of the Domain Name System (that ICANN contributes to/facilitates).
  • Challenges to the secure and resilient operation of the unique identifiers system.

As part of the scoping exercise, we also identified additional information needed to advance our work and documented questions for the ICANN organization on each topic. The answers to the questions will help us to develop findings and eventually recommendations.

On the third and final day of the meeting, we revisited our workplan and spent some time looking ahead to our next face-to-face meeting, which will be at ICANN64 in Kobe. While we hoped to have draft recommendations to present to the community in Kobe, we will instead use the face-to-face meeting time to reach consensus on the findings for the remaining three workstreams of our review, and advance the drafting of our report. At ICANN64 we also will hold an engagement session with the community where we will discuss our work to date. We expect to share our draft findings and recommendations with the community at ICANN65 in Marrakech, with a view to publishing our draft final report in August 2019, and then presenting our final report in November 2019 at ICANN66 in Montreal.

Meet with us at ICANN64

Let us know via our mailing list at input-to-ssr2rt@icann.org (publicly archived) if you would like to set up a consultation with us in Kobe, separate from our general engagement session. The SSR2 Review Team encourages everyone to share their views throughout our work, either in person or via our mailing list.

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