Skip to main content

Approved Resolution | Meeting of the New gTLD Program Committee

Note: On 10 April 2012, the Board established the New gTLD Program Committee, comprised of all voting members of the Board that are not conflicted with respect to the New gTLD Program. The Committee was granted all of the powers of the Board (subject to the limitations set forth by law, the Articles of incorporation, Bylaws or ICANN's Conflicts of Interest Policy) to exercise Board-level authority for any and all issues that may arise relating to the New gTLD Program. The full scope of the Committee's authority is set forth in its charter at

  1. Defensive Applications for New gTLDs

    Whereas, the Board approved the New gTLD Program with protections for certain interests and rights, and intellectual property rights in particular (;

    Whereas, the Board provided its rationale for approving the New gTLD Program with these elements (;

    Whereas, the availability of the objection process and other aspects of the program have been actively communicated;

    Whereas, ICANN received comment describing an apparent need to submit gTLD applications for defensive purposes to protect established legal rights;

    Whereas, ICANN responded by establishing a public comment period to seek input on the sources of this perception and how it could be addressed (;

    Whereas, ICANN held a public workshop during ICANN's public meeting in Costa Rica to hold a community discussion regarding suggestions raised during the comment period, and additional suggestions with participation from the community (;

    Whereas the New gTLD Program goals include the protection of established legal rights,;

    Whereas, a summary and analysis of public comment was performed and the discussion in the public workshop was transcribed;

    Whereas the sense of the public discussion indicated that trademark protections should continue to be discussed and developed for the registration of second-level domain names and also indicated that cybersquatting was not likely to be a significant issue in the registration of top-level domain names;

    Whereas, ICANN is committed to reviewing the effectiveness of the application and evaluation process, and of the safeguards put in place to mitigate issues involved in the introduction of new gTLDs, following the initial application round;

    Whereas, the comments indicated that significant concerns about awareness of the protections available and that renewed efforts should be undertaken to broadly communicate those protections to rights holders;

    Resolved (2012.04.10.NG1), the New gTLD Program Committee thanks the community for its participation in the discussion of this issue.

    Resolved (2012.04.10.NG2), while the New gTLD Program Committee is not directing any changes to the Applicant Guidebook to address defensive gTLD applications at this time, the New gTLD Program Committee directs staff to provide a briefing paper on the topic of defensive registrations at the second level and requests the GNSO to consider whether additional work on defensive registrations at the second level should be undertaken;

    Resolved (2012.04.10.NG3), the New gTLD Program Committee directs staff to continue implementing targeted communications about the processes used and protections available in the New gTLD Program.

    Rationale for Resolutions 2012.04.10.NG1-2012.04.10.NG3

    [Rationale to be provided with Minutes.]

  2. GNSO Recommendation for Protection of Red Cross and International Olympic Committee Names in New gTLDs

    Resolved (2012.04.10.NG4), the New gTLD Program Committee acknowledges receipt of the GNSO's recommendation on extending certain protections to the Red Cross/Red Crescent and the International Olympic Committee names at the top level.

    Resolved (2012.04.10.NG5), the New gTLD Program Committee chooses to not change the Applicant Guidebook at this time.

    Rationale for Resolutions 2012.04.10.NG4-2012.04.10.NG5

    [Rationale to be provided with Minutes.]

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