Skip to main content

EPDP Team Makes Substantial Progress Toward Final Report

Epdp team progress final report 1549x848 24jan19 en

The Expedited Policy Development Process (EPDP) Team on the Temporary Specification for generic top-level domain (gTLD) Registration Data is making substantial progress as we prepare to deliver our Final Report in early February.

Starting at the beginning of the year, the EPDP Team has resumed meeting twice a week. We would like to thank everyone that provided public comments in response to the Initial Report. The Leadership and Staff Support Team compiled the submissions into an organized format to ensure a comprehensive and efficient review of all comments received. The Team's Public Comment Review page provides a separate page for each purpose statement and recommendation, as well as all comments received on a specific recommendation, from the Team's Initial Report.

We received a total of 42 unique submissions. Nine ICANN community groups commented on the Initial Report, including Supporting Organizations, Advisory Committees, and Stakeholder Groups and Constituencies in the Generic Names Supporting Organization (GNSO). In addition, 33 submissions came from individuals, external companies, and organizations.

The Team met in Toronto, Canada from 16 to 18 January to make the final preparations for the report. In order to effectively prepare for the face-to-face meeting, each member was asked to review all public comments received. Prior to the meeting, members were asked to (1) prepare updated language if he or she believed the public comments highlighted a necessary change; (2) provide a rationale if he or she believed no change was warranted; (3) highlight issues needing full Team discussion; and (4) use a discussion summary tool to compile concerns.

The meeting was very productive in the preparation of our Final Report. Through the assistance of mediators from the Consensus Building Institute and using breakouts when needed, the Team was able to provide support to six purposes for processing data and nine policy recommendations. We will continue working diligently over the next two weeks until the Final Report is delivered.

From the outset of this EPDP, we knew the work before us would be challenging and require patience, flexibility, and hard work. On behalf of the Leadership Team, we would like to personally thank each member of the EPDP Team for their contribution to this process towards publication of the Final Report.

More Information

The transcripts, recordings, and outputs of the EPDP Team's Toronto meeting is published on this wiki page.

We welcome the ICANN community to follow the EPDP by subscribing to our weekly update newsletter. All editions can be accessed here.

Comments

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