Skip to main content

Data Protection/Privacy Update: Revised Proposed Temporary Specification Published; Webinar Scheduled

Gdpr updated proposed temp spec 750x424 14may18 en

I want to share some important updates related to our plans for compliance with the European Union's General Data Protection Regulation (GDPR) following very productive discussions that occurred at the Vancouver Board Workshop. Based on extensive Board input and robust discussions, we published revisions to improve the clarity of the proposed Temporary Specification for gTLD Registration Data. You can view the revised document here [PDF, 153 KB], as well as a redlined version here [PDF, 199 KB]. In addition, we scheduled a community webinar that will be held from 09:15 to10:30 Pacific Daylight Time (16:15-17:30 UTC) on 15 May 2018 to discuss this topic.

As a reminder, the intent of this specification is to establish temporary requirements to enable ICANN org and its gTLD registries and registrars to continue to comply with ICANN contractual requirements and community-developed policies, as well as the European Union's General Data Protection Regulation (GDPR), while maintaining the existing WHOIS system to the greatest extent possible.

I also want to point out that the Board passed a resolution noting their intent to take a decision on the adoption of the Temporary Specification on or about 17 May 2018. As noted in the resolution, the Board intends to use this additional time to confirm that appropriate modifications are incorporated into the Temporary Specification prior to adoption. Cherine Chalaby will be publishing a blog soon with more information on the Board's activities during their Vancouver Workshop.

In parallel, we still hope to receive a response to our letter [PDF, 400 KB] to the Article 29 Working Party that provides us with more clarity and guidance to inform the specification.

I know that this is a busy time for all of us, and I am well-aware of the pressures we are facing given the fast-approaching 25 May deadline for enforcement of the GDPR. That said, I want to take a moment to acknowledge your hard work and contributions on this issue, so thank you. Together we have achieved a lot and it has been truly remarkable to watch the multistakeholder community – a mix of individuals, non-commercial stakeholder groups, industry, governments and technical experts committed to a community-based, consensus-driven, policy-making approach – in action.

We still have more to do, but we're closing in on the finish line. Stay the course and, once again, thank you for your efforts.

As always, I encourage you to visit our Data Protection/Privacy page for the latest updates.


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