Technical Study Group Publishes Draft Model for Review and Input
On behalf of the Technical Study Group on Access to Non-Public Registration Data, I am pleased to share with you the Draft Technical Model for Access to Non-Public Registration Data. This document represents the collective input of our group. We are sharing this model now to give the community time to review it prior to an engagement session on 11 March 2019 at ICANN64 in Kobe, Japan.
As noted in my last blog, at the conclusion of our February face-to-face meeting, this model is built on the Registration Data Access Protocol (RDAP). The draft model includes details on the system requirements, actor models, and recommended authentication/authorization mechanisms. When we finish our work, we will send our report to ICANN President and CEO Göran Marby, who chartered our work.
We look forward to discussing this model with you in more detail in Kobe, from 04:30-06:00 UTC on 11 March 2019 in Portopia Hall. Remote participation will be available for this session. We are also looking forward to meeting with several community groups in Kobe. If you are interested in hearing more from our group or would like to send us your input on the model, please email firstname.lastname@example.org. For more information on our work, please visit our page on https://www.icann.org.
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."