Skip to main content

Next Steps with the RDAP Service for gTLD Registries and Registrars

Rdap update 750x425 28feb19 en

Last August, a draft of the Registration Data Access Protocol (RDAP) profile underwent Public Comment in an effort to give the entire ICANN community a chance to provide feedback on this important document. The ICANN organization worked with a discussion group of gTLD registries and registrars to create this proposal. We've published the profile and invite you to review it at the RDAP webpage. The RDAP implementation process has now started, and we have updated our implementation timeline accordingly.

RDAP enables users to access current registration data and has several advantages over the current protocol (WHOIS) including: support for internationalization, more secure access to data, and the ability to provide differentiated access to registration data. The profile, which follows the requirements of the Temporary Specification for gTLD Registration Data, aims to provide technical instructions to gTLD registries and registrars on how to implement the RDAP service in a consistent way.

The input gathered via Public Comment was provided to the discussion group of gTLD registries and registrars. They submitted the finalized profile this week to the ICANN organization.

We look forward to the next steps of the RDAP deployment. As you may recall, the Temporary Specification for gTLD Registration Data requires all gTLD registries and registrars to deploy an RDAP service after notification from ICANN. Additional resources and information about the RDAP profile development can be found at the RDAP webpage. We thank the discussion group of gTLD registries and registrars for their contributions, and the community for their participation to achieve this critical milestone.


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