Skip to main content
Resources

Registration Data Policy for gTLDs (EPDP Phase 1 Implementation)

Implementation Project Status

Updated 6 January 2020

Translation and Transliteration of Contact Information Implementation Project Status: Plan

  • Interim Registration Data Policy for gTLDs Policy published on 17 May 2019

  • Interim Policy Effective Date: 20 May 2019

Timeframe

Summary

On 4 March 2019, the GNSO Council adopted the Expedited Policy Development Process (EPDP) on gTLD Registration Data Team's Phase 1 Final Report. Following a Public Comment period, the ICANN Board passed a resolution on 15 May 2019 to authorize the implementation of 27 of the 29 recommendations contained within the Report. Of the two recommendations not adopted in full, the Board identified portions of the recommendations that require further consultation with the GNSO (see the ICANN Board's scorecard for the EPDP's Phase 1 recommendations here).

ICANN org implemented the Interim Registration Data Policy for gTLDs pursuant to the Board's 15 May 2019 resolution. The interim policy maintains requirements from the Temporary Specification for gTLD Registration Data, which detailed how registries and registrars must handle gTLD registration data as a result of privacy legislation, and which expired on 20 May 2019. The EPDP Team recommended that the final effective date for the Registration Data Policy for gTLDs be 29 February 2020 (see Recommendation 28 from the Final Report).

Resources

A note about our privacy policies and terms of service:

We have updated our privacy policies and certain website terms of service to provide greater transparency, promote simplification, and align with recent changes in privacy laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

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