Skip to main content
Resources

Approved Resolution | Meeting of the New gTLD Program Committee

  1. Response to 17 June 2012 GAC Letter

    Resolved (2012.07.27.NG01), the New gTLD Program Committee approves the sending of a response [PDF, 577 KB] to the Governmental Advisory Committee's (GAC's) 17 June 2012 letter regarding the New gTLD Program.

    Rationale for Resolution 2012.07.27.NG01

    On 17 June 2012, the GAC notified the Board of three items:

    First: The GAC advises the Board to consult with the community as a matter of urgency to consider ways to improve its assessment and delegation processes in order to minimise the downside risks and uncertainty for applicants. In line with the concerns raised by the community, this should include a focus on competition and fairness with delegation timing. The GAC intends to address the issue of the digital archery and batching system at the Prague meeting with the Board.

    Second: The GAC advises the Board that it is planning to issue any Early Warnings shortly after the Toronto ICANN meeting, in October 2012.

    Third: The GAC advises the Board that it will not be in a position to offer any advice on new gTLD applications in 2012. For this reason, the GAC is considering the implications of providing any GAC advice on gTLD applications. These considerations are not expected to be finalised before the Asia-Pacific meeting in April 2013.

    The Board responded to the first item above on 20 June 2012. The sending of the response as approved by the New gTLD Program Committee now provides the GAC with a response to the other two items above, and furthers ICANN's commitment to accountability and transparency. These items are also tracked on the recently-released Register of GAC advice. The communication to the GAC notes that the Board looks forward to receiving the results of GAC deliberations in timely fashion, and that ICANN's CEO will be reaching out to the GAC for further clarification on the intended timeframe for providing further advice.

    Providing a response to the GAC has no financial impact on ICANN and will not negatively impact the systemic security, stability and resiliency of the domain name system.

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