Skip to main content

NGPC Begins Consideration of GAC Durban Advice on New gTLDs

The ICANN Board New gTLD Program Committee (NGPC) met on 13 August 2013 to begin consideration of the GAC's further advice regarding new gTLD applications in the GAC Durban Communiqué [PDF, 103 KB], issued on 18 July 2013.

The NGPC is developing a GAC scorecard similar to the one used to address the Beijing Advice as well as during the GAC and the Board meetings in Brussels on 28 February and 1 March 2011.

Each GAC scorecard item will be noted with a "1A", "1B", or "2":

  • "1A" indicates that the NGPC's proposed position is consistent with GAC advice as described in the Scorecard.
  • "1B" indicates that the NGPC's proposed position is consistent with GAC advice as described in the Scorecard in principle, with some revisions to be made.
  • "2" indicates that the NGPC's current position is not consistent with GAC advice as described in the Scorecard, and further discussion with the GAC is required following relevant procedures in the ICANN Bylaws.

The Durban scorecard is not yet finalized and, with respect to some of the items, cannot be finalized until after the review of applicant responses due on 23 August 2013.

At its most recent meeting, the NGPC also adopted resolutions prohibiting Dotless Domains in new gTLDs and adopting the BGC's Recommendation to deny Reconsideration Request 13-4.

The NGPC will next meet on or about 10 September 2013 and will provide a further update following that meeting.

The New gTLD evaluation and objection processes remain on track while the NGPC continues its deliberations on GAC Advice. The NGPC is prioritizing its work in order to allow the greatest number of applications to move forward as soon as possible. We will continue to provide updates on the NGPC's progress in responding to the GAC Beijing and Durban Advice.


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