Skip to main content

Minutes | 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

A Meeting of the New gTLD Program Committee of the ICANN Board of Directors was held on 12 September 2012 at 5:00 p.m. local time in Los Angeles, California.

Committee Chairman Cherine Chalaby called the meeting to order.

In addition to the Chair the following Directors participated in all or part of the meeting: Akram Atallah, Chris Disspain, Bill Graham, Erika Mann, Gonzalo Navarro, Ray Plzak, R. Ramaraj, George Sadowsky, Mike Silber, Judith Vazquez and Kuo-Wei Wu.

Thomas Narten, IETF Liaison, and Thomas Roessler, TLG Liaison, were also in attendance as non-voting liaisons to the committee.

Fadi Chehadé, Olga Madruga-Forti and Heather Dryden, GAC Liaison, were in attendance as invited observers.

This is a preliminary report the Meeting of the New gTLD Program Committee, which took place on 12 September 2012.

  1. Enhanced Protections for IOC and Red Cross/Red Crescent Names

    Kurt Pritz introduced the topic, noting that ICANN has received advice from the GAC on three occasions on this topic, that ICANN should provide protections at the top and second levels for IOC and Red Cross names. Kurt provided history on the work within the GNSO on this topic, including that a drafting team provided recommendations at the top level. Recommendations regarding the second-level protections had have not yet issued. Kurt noted that the IOC and the Red Cross are in contact with ICANN, the GNSO and the GAC on this issue. The time-sensitive pressure on this is to review second-level protections so that if they are adopted, they will be in place before New gTLDs are delegated. There is a recommendation to request some specific advice from the GNSO regarding whether some names could be protected at the second level by adding them to the reserved names list within the TLD agreements.

    The New gTLD Program Committee then reviewed a proposed resolution and noted some concerns that the resolution as proposed did not state the correct question to the GNSO. The New gTLD Program Committee also noted that a rationale had not yet been drafted for the proposed resolution.

    Chris Disspain suggested that the proposed resolution be refined over the next day, as well as a proposed rationale drafted, and circulated to the Committee to review.

    The Chair noted the import of taking this decision before Toronto, to allow ICANN to respond to the GAC advice on this topic, as well as a commitment to providing further information at the beginning of 2013 after hearing from the GNSO.

    The Chair called the meeting to a close.

Posted on 5 November 2012.

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