Skip to main content

GNSO Council Launches EPDP on the Temporary Specification for gTLD Registration Data

Gnso council epdp temp spec launch 750x425 19jul18 en

It is an honor to announce that the Generic Names Supporting Organization (GNSO) Council has just officially launched an Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. During our July Council meeting held today at 12:00UTC, the GNSO Council passed the Initiation Request [PDF, 390 KB] of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data and adopted the EPDP Team Charter [PDF, 523 KB]. Both documents are the product of several months of preparatory work on the part of the Council, acting as the Charter and Initiation Request Drafting Team. This important milestone marks the official commencement of the GNSO's very first Expedited PDP. As the name suggests, an EPDP is a Policy Development Process in which the early steps of Preliminary Issue Report and Final Issue Report (and associated public comment periods) are eliminated to fast-track policy development in cases of urgency. The GNSO Council has agreed that the EPDP is the most appropriate response to the ICANN Board's adoption of the proposed Temporary Specification for gTLD Registration Data. It facilitates meeting the unique time constraints presented by the Temporary Specification, as described in detail in the Background Information section below.

Since the Board's adoption of the Temporary Specification on 17 May 2018, the GNSO Council, as Bylaws-mandated manager of the policy development process, has been working hard in preparation for the launch of this EPDP. During an extraordinary meeting on 12 June 2018, the GNSO Council agreed to form a Drafting Team, consisting of Council leadership and interested Council members. Over the next several weeks, including many face-to-face hours at ICANN62 in Panama and many hours of teleconferences in the weeks following ICANN62, the Drafting Team worked tirelessly to reach an agreement on challenging issues such as membership criteria, composition, leadership, and scope of the policy development effort. Incremental changes identified through the PDP 3.0 – a key 2018 initiative of the GNSO Council aimed at improving the effectiveness and efficiency of the PDP – have informed and guided the Charter drafting process. Ultimately, the EPDP Charter is a testament to the true commitment and diligence of the Drafting Team and GNSO Council.

It is also with great pleasure that we announce the appointment of Kurt Pritz as the Chair of the EPDP. Following rigorous evaluation of the applications received for the role of Chair of the EPDP, a selection panel unanimously recommended Kurt Pritz for this important position. The GNSO Council has agreed that he possesses the unique skill set needed to lead this EPDP. The GNSO Council has also put out a Call for Volunteers for the EPDP Team; it is expected that the Team will be formed and hold its first meeting during the week of 30 July 2018.

This is an achievement that all in the GNSO and the wider ICANN community can be immensely proud of. This milestone could not have been achieved without the dedication, principled compromise, and remarkable efforts of the Drafting Team and GNSO Council members, working in collaboration with their Stakeholder Groups and Constituencies. While the EPDP has put the GNSO in unfamiliar territory, the heartening amount of work accomplished in such a short period has laid the groundwork for the EPDP's success. Please join me in celebrating the GNSO Council's achievement, and the demonstration of Councilors' ability to work together in the true spirit of the multistakeholder model.

We welcome the ICANN community to follow the important work of the EPDP. To learn how to participate as a non-member, you may read our announcement today on

Background Information

On 17 May 2018, the ICANN Board adopted the proposed Temporary Specification for gTLD Registration Data. This was an interim measure to bring existing WHOIS obligations in line with requirements of the European Union's General Data Protection Regulation. This has, in turn, triggered the obligation of the GNSO Council to undertake a policy development process to confirm, or not, the Temporary Specification as a Consensus Policy. The EPDP must be completed within 12 months of the implementation effective date (25 May 2018) of the Temporary Specification.


    jonathan matkowsky  00:41 UTC on 20 July 2018

    I look forward to observing, or participating if invited. Congrats. Jonathan Matkowsky VP, Cybersecurity, Privacy & IP JD, CIPP/EU, CIPT PGP Fingerprint AE12 A604 D2EC RiskIQ, Inc.

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