Skip to main content

How to Get Involved: Launch of the EPDP on the Temporary Specification for gTLD Registration Data

Launched: Expedited Policy Development Process on Temporary Specification for gTLD Registration Data | Get involved! | Mailing List, Transcripts, Audio Streams

LOS ANGELES – 19 July 2018 – Today, the Generic Names Supporting Organization (GNSO) Council initiated the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Read the GNSO Chair Heather Forrest's blog for more details.

Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council has decided to limit the membership composition of this EPDP. This decision is primarily based on the need to complete the work in a relatively short timeframe and to resource the effort responsibly. As such, GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Security and Stability Advisory Committee (SSAC), and the Root Server System Advisory Committee (RSSAC) have each been invited to appoint up to a set number of members and alternates, as outlined in the EPDP Team Charter [PDF, 523 KB]. In addition, the ICANN Board and ICANN Org have been invited to assign a limited number of liaisons to this effort.

However, that does not mean that members of the ICANN community cannot be involved if they are not appointed members, alternates or liaisons. One can follow the deliberations of the EPDP Team by signing up as a mailing list observer, follow the meetings via real-time audio cast, and check the recordings and transcripts accessible to the public. Furthermore, the Charter dictates that the EPDP Team should make provisions as part of its work plan to provide regular updates to the ICANN community and others interested, for example, through newsletters and webinars. Moreover, the EPDP Team is required to reach out at an early stage to GNSO Stakeholder Groups and Constituencies as well as other ICANN Supporting Organizations and Advisory Committees to request input. Last but not least, everyone will be invited to comment on the EPDP Team Initial Report once it is published for public comment. Per the EPDP procedures, the EPDP Team is expected to carefully consider and analyze all input received through the public comment forum. Further details on how to get involved are included hereunder. The GNSO Council hope that the ICANN community will make use of these opportunities to closely follow the EPDP Team deliberations!

Mailing List Observers

One can become an observer of the EPDP Team mailing list on a read-only basis. Sign up here: https://goo.gl/forms/iZg5JWHOnERsoEMI2. The names of mailing list observers will also be published on the EPDP wiki space.

Conference Call Audio Cast

While participation on EPDP Team conference calls is restricted to appointed members and liaisons only, non-members are able to listen in real-time via an audio cast. The audio cast will begin streaming a few minutes before the start of each conference call:

Check the EPDP Team conference calls on the GNSO Master Calendar.

Recordings, Transcripts & Materials

All EPDP Team conference calls will be recorded and transcribed. Recordings, transcripts as well as any notes and action items will be made available on the GNSO Master Calendar. In addition, all EPDP related materials, including recordings, transcripts, background documents, and team output, can be found on the EPDP wiki space.

Frequently Asked Questions

ICANN Org has gathered questions received on the EPDP and will continue adding questions to the live Frequently Asked Questions document as they are received.

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

For further information, please email gnso-secs@icann.org.

About ICANN

ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.


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