Update on the Registration Data Access Protocol (RDAP) Profile
I am pleased to report that the Registration Data Access Protocol (RDAP) pilot discussion group has submitted their proposed profile to the ICANN organization, which follows the requirements of the Temporary Specification for gTLD registration data. RDAP delivers registration data much like WHOIS, but its implementation will help standardize registration data access and query response formats. Moreover, RDAP provides native support for Internationalized Domain Names (IDNs), and more importantly, the ability to provide a uniform and robust platform for layered access to registration data for legitimate users.
In addition, the discussion group for RDAP service level agreements (SLA) and reporting requirements is finalizing their proposed specification, which we expect to receive in mid-August.
The ICANN org plans to review and publish the proposed profile, SLA, and reporting requirements for public comment in the second half of August. I’ll be issuing a new blog once that occurs. Concurrently, we’ll be updating our ICANN RDAP resources page with additional information and collateral for RDAP implementers and users.
As a reminder, all gTLD registries and registrars will be required to deploy an RDAP service within 135 days upon notice from ICANN. Additional information about this requirement is published in the Temporary Specification, which is now available in Arabic, Chinese, English, French, Spanish, and Russian.
My sincere thanks to the discussion groups and all volunteers who contributed to this important activity!
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."