Skip to main content

On New gTLDs and the Timeline…

ICANN recently published materials describing discussions, public comment and general progress on the New gTLD program. One area that has attracted particular interest is the timeline for moving forward.

If you have been following this program, you know that predicting timelines has been problematic because progress depends on community reaction to proposals and ensuring those proposals have been or will be considered.

The recent New gTLD announcement states that the next version of the Applicant Guidebook will be published in April – not long after the GAC–Board of Directors consultations in Brussels and at the Silicon Valley-San Francisco public meeting. The announcement simply refers to publication of the “Applicant Guidebook;” it does not state if it is “final” or if it would be posted for public comment.

That’s because a decision on timing and posting of a final Guidebook cannot be made yet. It’s up to the Board to decide on the disposition of the Guidebook and other program aspects, and that can’t happen until the GAC consultations conclude and the Board has a chance to listen to the community at the Silicon Valley meeting. They could decide on the launch of the process and could specify a different timing for publication.

So it would have been appropriate to mark the timeline we posted as “draft” or “proposed”; we’ll do that now. We aim to publish the Guidebook as soon as possible. The ICANN team and many community members are working diligently to complete the work: considering comments and amendments, drafting text, improving protections and consulting with community members.

Even at an accelerated pace, comments and open issues are being carefully considered and discussed. I hope that is evident in the quality and quantity of materials provided. We look forward to productive meetings with the Board and GAC and will provide more information on the timeline and the new gTLD launch as soon as it is available.


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