Skip to main content

Keep Up with EPDP on the Temporary Specification for gTLD Registration Data

Epdp temp spec gtld registration data 1200x600 10sep18 en

The Expedited Policy Development Process (EPDP) Team on the Temporary Specification for gTLD Registration Data kicked off its first meeting on 1 August 2018. Due to the expedited timeline, the EPDP Team agreed to meet for two hours, twice a week.

We are aware that keeping up with this fast-moving EPDP may prove challenging, particularly for non-members. Therefore, we plan to utilize a variety of communication channels and platforms for the ICANN community to follow the EPDP's progress to respond to different needs. Below is a summary of the types of ongoing updates you can expect.

Announcements & Blogs

We will keep the ICANN community informed of important milestones and key activities of the EPDP Team via announcements and blogs published on These updates could include notifications of open or closed public comment periods and official statements from the EPDP Leadership Team.

GNSO Council Updates

Rafik Dammak, the GNSO Council Liaison to the EPDP Team, provides weekly updates on the team's progress to the GNSO Council, which acts in the role of the policy manager of GNSO PDPs. You may access these updates via the EPDP wiki workspace or the EPDP page on the GNSO website.

ICANN Global Newsletters

Subscribe to the monthly ICANN Global Newsletters. Each newsletter will feature EPDP content providing you with a summary of the EPDP Team's progress.

ICANN63 Communications

About a month before ICANN63 begins, a wide array of communications programs and materials will be launched to provide a detailed overview of the policy development activities. The EPDP efforts will be featured in the following ICANN63 communications:

  1. Pre-ICANN63 GNSO Policy Briefing (check previous editions here)
  2. Pre-ICANN63 Policy Report (check previous editions here)
  3. Pre-ICANN63 Policy Webinar

During ICANN63, the daily meeting newsletter and ICANN YouTube channel will also provide timely updates about the EPDP sessions.

Dedicated EPDP Webinars

The EPDP Leadership, in collaboration with ICANN's policy development support staff, plans to hold one or more dedicated webinars about the EPDP. These webinars aim to provide you with details and insights into the EPDP Team's work, as well as opportunities to ask questions. The timing and frequency will depend on the EPDP Team's progress. Watch for future webinar announcements on

Social Media

Follow @ICANN_GNSO on Twitter! In addition to tweets about the agenda and audiocast to follow our EPDP Team meetings 'live', you will also be alerted to EPDP communications promoted via the other channels noted above.

We sincerely hope the ICANN community will take advantage of these opportunities to closely follow the EPDP and get involved! To learn more about participation as an observer, read the July announcement on

About EPDP

On 17 May 2018, the ICANN Board adopted the proposed Temporary Specification for gTLD Registration Data. This is an interim measure to bring existing WHOIS obligations in line with requirements of the European Union's General Data Protection Regulation. This also triggered the GNSO Council to undertake a policy development process to confirm, or not, the Temporary Specification as a Consensus Policy within 12 months of its implementation effective date (25 May 2018). The GNSO Council agreed that an EPDP provides the best opportunity to meet this timing requirement. To determine the proposed path forward, a Drafting Team was formed, consisting of Council leadership and interested Council members. The Drafting Team developed an Initiation Request [PDF, 390 KB] for an EPDP and a proposed EPDP Team Charter. During its meeting on Thursday, 19 July 2018, the GNSO Council passed the motion to initiate the EPDP and to adopt the EPDP Team Charter [PDF, 523 KB].


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