Skip to main content

Deadline Extended – Call for Expressions of Interest: Chair of Phase 2A GNSO EPDP on the Temporary Specification for gTLD Registration Data

This is an update to the announcement published on 4 November 2020.

LOS ANGELES – 13 November 2020 – The Generic Names Supporting Organization (GNSO) Council of the Internet Corporation for Assigned Names and Numbers (ICANN) is seeking a neutral chair for the remaining Phase 2A work of the Expedited Policy Development Process (EPDP) on the Temporary Specification for Generic Top-Level Domain (gTLD) Registration Data.

Candidates interested in serving in this role should review the Expressions of Interest document before submitting their application. The document details the role description, required skills and experience, time commitment, and selection process. The deadline to submit an Expression of Interest has been extended to 23 November 2020 at 23:59 UTC.

There will be no compensation associated with the role of the EPDP Team chair; however, travel associated with any face-to-face meetings may be supported by the ICANN org. Please note that face-to-face meetings are currently paused due to pandemic travel restrictions.

Expressions of Interest should be submitted to EOI-EPDPTeam-chair@icann.org. By submitting your personal data, you agree that your personal data will be processed in accordance with the ICANN Privacy Policy, and you agree to abide by the electronic Terms of Service.

Background on EPDP Phase 2A

The two remaining topics that are part of Phase 2A will be:

  • Legal vs. natural persons
  • Feasibility of unique contacts to have a uniform anonymized email address

Instructions for the EPDP Team to address the issues of Phase 2A:

  1. Legal vs. natural persons: The EPDP Team is expected to review the study undertaken by ICANN org (as requested by the EPDP Team and approved by the GNSO Council during Phase 1), the legal guidance provided by Bird & Bird LLP, as well as the substantive input provided on this topic during the Public Comment forum on the addendum. The Team will then answer:
    1. Whether any updates are required to the EPDP Phase 1 recommendation on this topic ("Registrars and Registry Operators are permitted to differentiate between registrations of legal and natural persons, but are not obligated to do so.", Rec. #17, EPDP Phase 1 Final Report)
    2. What guidance, if any, can be provided to registrars and/or registries who differentiate between registrations of legal and natural persons.
  2. In relation to the feasibility of unique contacts obtaining a uniform anonymized email address, the EPDP Team is expected to review the legal guidance and consider specific proposals that provide sufficient safeguards to address issues flagged in the legal memo. Groups that requested additional time to consider this topic, which include the At-Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), and Security and Stability Advisory Committee (SSAC), will be responsible to come forward with concrete proposals to address this topic. This consideration is expected to address:
    1. Whether or not a uniform anonymized email address for unique contacts is feasible and, if feasible, whether it should be a requirement.
    2. If feasible but not a requirement, what guidance, if any, can be provided to contracted parties who may want to implement uniform anonymized email addresses.

For clarity, the GNSO Council is not directing any particular outcome on either topic. As manager of the policy development process (PDP), it is sharing its expectations for which questions should be addressed as part of the EPDP Team's deliberations.

Consistent with the Policy Development Process Manual, the GNSO Council does expect that all the required steps are followed in the consideration of these issues. These steps may include further Public Comment on an initial report as well as a final report that would be considered an addendum to the EPDP Phase 2 Final Report.

Additional information about the EPDP is located in the Annex-A1 of the ICANN Bylaws and EPDP Manual.

Additional Resources:

About the Generic Names Supporting Organization (GNSO)

As one of the three Supporting Organizations in the ICANN community, the GNSO develops policies relating to generic top-level domains (gTLDs). Its membership consists of representatives advocating for the gTLD registry, gTLD registrar, noncommercial, not-for-profit, business, intellectual property, and Internet service provider and connectivity interests. The GNSO Council manages the policy development process relating to gTLDs.

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