Skip to main content

Chair's Blog: Approving the Temporary Specification for gTLD Registration Data and Next Steps

Approving gtld registration data specs 750x425 17may18 en

The ICANN Board's approval today of the proposed "Temporary Specification for gTLD Registration Data" is an important step towards bringing ICANN and its contracted parties into compliance with the European Union's General Data Protection Regulation (GDPR). The Board took this action so that ICANN and its contracted parties may remain in compliance with both existing contractual requirements and community-developed policies as they relate to WHOIS.

The adoption of this Temporary Specification is a major and historic milestone as we work toward identifying a permanent solution. The ICANN org and community have been closely working together to develop this interim model ahead of the GDPR's 25 May 2018 enforcement deadline, and the Board believes that this is the right path to take.

WHOIS is an important system, and preserving it allows it to continue to act as a key tool in the ongoing fight against cybercrime, malicious actors, intellectual property infringement, and more. This Temporary Specification, which is based on the Proposed Interim Compliance Model [PDF, 922 KB], aims to prevent fragmentation of WHOIS and ensure that WHOIS continues to be available, to the greatest extent possible. ICANN's role in providing the technical coordination of the globally distributed WHOIS system is a unique matter, including the public interest nature of WHOIS.

In my previous post, I provided the background into how the Board reorganized its Vancouver Workshop to dedicate a significant amount of time, and effort to review and discuss the proposed Temporary Specification, This extra time was also an important opportunity for us to have ICANN org answer our questions and discuss the potential risks that could accompany either no action or adoption of a proposed Temporary Specification.

Above all, ICANN's mission, as laid out in the bylaws, is to preserve the Internet's system of unique identifiers. We believe that this Temporary Specification strikes the right balance between upholding that mission and bringing the org and its contracted parties into compliance with this law.

As with the requirements of a temporary policy, if still needed, the Board will reconvene in 90 days to reaffirm its adoption. Until that time, I encourage you to submit your thoughts to gdpr@icann.org. And I invite you to visit the dedicated Data Protection/Privacy page to follow the latest updates.

Finally, I want to thank the community, ICANN org and the Board for their hard work over the past year in getting us to this place. While I recognize there are important elements remaining to be finalized, the adoption of this Temporary Specification today is a first step, and it sets us on the right path to maintaining WHOIS in the public interest, while complying with GDPR.

Comments

    Teamanddata  15:11 UTC on 24 May 2018

    I will apply here after seeing the results of the current implementation.

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