Skip to main content

Data Protection/Privacy Update: Seeking Additional Clarity from Article 29

Gdpr update 10may18 en

In a previous blog post, I detailed our 23 April meeting with the Article 29 Working Party (WP29) Technology Subgroup in Brussels. This meeting was an important follow-up to the letter [PDF, 400 KB] that WP29 sent us on 11 April, and we remain appreciative of the opportunity to receive their feedback on the progress made in developing an interim compliance model.

It was clear after our meeting that a number of important questions still remained, and we agreed to provide a letter requesting additional input on how to bring the ICANN org and contracted parties into compliance with the law. That letter was sent to the WP29, and is available here [PDF, 564 KB].

We hope that the WP29's reply will provide us with greater clarity and guidance as we move forward.

Our ongoing dialogue with the WP29 has been a key part of our overall work to identify a model that will both maintain the current WHOIS to the greatest extent possible, while also complying with the European Union's General Data Protection Regulation (GDPR). It is important that we strike the right balance that allows us to both maintain a stable and secure Internet and comply with our bylaw obligations relating to WHOIS, while also ensuring compliance with the law.

As always, you can follow the latest updates on our dedicated Data Protection/Privacy page. We welcome the community's input and invite you to email your thoughts to


    Daniel K. Nanghaka  21:09 UTC on 12 May 2018

    Thanks for the great progress and work, I would like to inquire about the previous works that have been going on with the GNSO RDS WG, All activities were put on hold until further notice which affects the original purpose of the WG, What will be the relevance of the WG after the successful implementation of the new model that will be compliant with the GDPR?

    Volker Greimann  02:39 UTC on 14 June 2018

    Maybe cheaper than losing in court over and over: Just search get this on Amazon: Meguiars Perfect-Clarity-Cleaner

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