Skip to main content

GNSO Council Adopts EPDP Final Report on the Temporary Specification for gTLD Registration Data

GNSO Council

LOS ANGELES – 4 March 2019 – Today, the Generic Names Supporting Organization (GNSO) Council voted to approve all of the policy recommendations in the Expedited Policy Development Process (EPDP) Team's Final Report on the Temporary Specification for gTLD Registration Data. The Final Report will now be submitted to the ICANN Board for consideration. The EPDP Team has been chartered to determine if the Temporary Specification for gTLD Registration Data should become an ICANN Consensus Policy as is, or with modifications.

The EPDP Team's Final Report includes 29 policy recommendations that broadly address the following areas:

  • Purposes for processing data.
  • Data elements for collection, transfer, and retention.
  • Data elements for public display.
  • Data elements to be redacted.
  • Changes and/or review of current ICANN Consensus Policies.
  • Update to reasonable requests for the lawful disclosure of data.
  • Continued course for an implementation bridge, or how contracted parties may handle the policy recommendations and Temporary Specification requirements following its expiration and before EPDP policy recommendations are officially implemented.

In developing its Final Report, the EPDP Team reviewed all public comments received on its Initial Report and incorporated changes where the Team believed warranted.

Public Comment

The GNSO Council has submitted the EPDP Team's Final Report for the ICANN Board's consideration. Prior to any action by the Board, the ICANN organization must provide a reasonable opportunity for parties to comment on the adoption of the proposed policies.

Accordingly, ICANN org has commenced a Public Comment period today on the EPDP Team's Final Report, which will close on 17 April 2019. Members of the ICANN community and the general public are welcome to participate and contribute.

EPDP Phase 2

Today, the GNSO Council also provided its non-objection to the EPDP Team starting its work on Phase 2 of the charter, which will include a system for standardized access to non-public registration data and issues in the Annex to the Temporary Specification ("Important Issues for Further Community Action"). In addition, Phase 2 will also include a number of items that were deferred from the EPDP Team's Phase 1 deliberations. The EPDP Team will begin planning for its Phase 2 work during ICANN64 in Kobe, Japan. The GNSO Council is now seeking expression of interest to chair Phase 2 of the EPDP. Learn More.

About EPDP

On 17 May 2018, the ICANN Board approved the Temporary Specification for gTLD Registration Data. The Board took this action to establish temporary requirements for how ICANN and its contracted parties would continue to comply with existing ICANN contractual requirements and community-developed policies related to WHOIS, while also complying with the European Union's General Data Protection Regulation (GDPR). The Temporary Specification has been adopted under the procedure for Temporary Policies outlined in the Registry Agreement (RA) and Registrar Accreditation Agreement (RAA). Following adoption of the Temporary Specification, the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." This Consensus Policy development process on the Temporary Specification would need to be carried out within a one-year period. Additionally, the scope includes discussion of a system for standardized access to non-public registration data. However, the discussion of a standardized access system will occur only after the EPDP Team has comprehensively answered a series of "gating questions" and non-objection by the GNSO Council.

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