Skip to main content
Resources

Approved Resolution | Meeting of the New gTLD Program Committee

  1. Consent Agenda:
    1. Approval of Minutes of New gTLD Program Committee Meeting of January 10 2013
  2. Main Agenda:
    1. Update on Addressing GAC Advice on Enforcing Applicants' Commitments
      1. Rationale for Resolution 2013.02.01.NG02

 

  1. Consent Agenda:

    1. Approval of Minutes of New gTLD Program Committee Meeting of January 10 2013

      Resolved (2013.02.01.NG01), the New gTLD Program Committee approves the minutes of the 10 January 2013 Meeting of the New gTLD Program Committee.

  2. Main Agenda:

    1. Update on Addressing GAC Advice on Enforcing Applicants' Commitments

      Whereas, applicants for new gTLDs identified certain purposes of the applied for gTLD and certain business plans that they intend to incorporate into the operation of their registry, but much of these plans are not currently anticipated to be incorporated as obligations into Registry Agreements.

      Whereas, the GAC's Toronto Communiqué includes advice to ICANN that "it is necessary for all of these statements of commitment and objectives to be transformed into binding contractual commitments, subject to compliance oversight by ICANN."

      Whereas the New gTLD Program Committee has devised a proposed mechanism to address the advice of the GAC.

      Resolved (2013.02.01.NG02), the New gTLD Program Committee directs the President and CEO to seek public comment on a proposed mechanism to address the GAC advice on these additional applicant commitments.

      Rationale for Resolution 2013.02.01.NG02

      It is important to determine if it is possible to address the advice received from the GAC on this issue. Creating a mechanism through which applicants will make binding commitments to ICANN in alignment with their applications could serve to promote the transparency and accountability of all within the ICANN community. While work still remains in developing this mechanism, it is anticipated that the creation of these binding commitments will benefit the public interest.

      The work called for in this resolution will require resources to complete, though it is not anticipated that this planning work will exceed budgeted resources. If properly implemented, the introduction of a mechanism to incorporate additional binding commitments could result in a positive benefit on the security, stability and resiliency of the DNS.

Published on 5 February 2013

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