Skip to main content

Temporary Drafting Group Work Session on New gTLD Implementation Issues – to be held 3 May 2010

The 23 April 2010 blog post about a New gTLD Consultation referenced exploration of a legal working group and a follow-up consultation to be convened on 3 May 2010. This blog post provides information about an open drafting consultation group and its first session that has been scheduled for 3 May at 15:30 UTC ( As such, there is no need for the follow-up consultation announced on 23 April 2010.


Open drafting consultation group to assist ICANN General Counsel’s Office and Staff in drafting proposed language for new gTLD agreement and related issues. The Group will convene in an open forum to consider language proposals for new gTLD agreements and related issues on issues that have been difficult to resolve or have received significant input.

The two issues open for drafting/discussion during the consultation will include:

1) The Trademark PDDRP and the inclusion of it in the new gTLD Agreement
2) Inclusion of Amendment Processes in new gTLD Agreement


Any results from the Temporary Drafting Group will be included in documents that will be posted for public comments. No results from the Group will necessarily be used in any agreement drafts, but inputs from the Group will be considered by the ICANN Staff in making recommendations relating to questions discussed or posed to the Group.


The first Temporary Drafting Group session will be held via teleconference on 3 May 2010 at 15.30 UTC/8.30 PDT Marina del Rey, CA, (, and is scheduled to last for 90 minutes.


If you would like to participate, please submit your name to, and we will provide you with call information. If you have proposed text for discussion during the meeting, please provide it no later than 30 April 2010 at 19.00 UTC/12.00 Noon Marina del Rey, CA, ( Language provided after that time will be considered as well, but not necessarily during that session.

This is not a formal public consultation, but is intended to inform drafting which might make up a later public consultation.

Staff Responsible: John Jeffrey, General Counsel and Secretary


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