Skip to main content
Resources

Approved Resolution | Meeting of the New gTLD Program Committee

Whereas, the GAC Communiqué issued in Prague states that the GAC, "requires further clarification as to the status of its pending request for enhanced protections for the [International Olympic Committee] and Red Cross/Red Crescent names at the top and second levels, …"

Whereas, earlier GAC letters of 11 June 2011 and 12 April 2012 expressed the same advice that "the IOC and Red Cross and Red Crescent [names] should be protected at the first and second top levels, given that these organizations enjoy protection at both the international level through international treaties (e.g. the Nairobi Treaty and the Geneva Conventions) and through national laws in multiple jurisdictions. The GAC considers the existence of such two-tiered protection as creating the criteria relevant to determining whether any other entities should be afforded comparable enhanced protection."

Whereas, the GNSO is actively engaged in policy discussion regarding second-level protections for the IOC and Red Cross/Red Crescent names, and has convened a drafting team that is working on this issue, and is further considering initiating a PDP on the broader issue of whether to protect the names of international organizations in new gTLDS.

Whereas, protections for the IOC and Red Cross/Red Crescent names at the top-level are in place for the current round of new gTLDs.

Whereas, the protections for the second level, if they are provided and if they are to be effective, should be in place before the delegation of the first new gTLDs.

Whereas, the Board favors a conservative approach, that restrictions on second-level registration can be lifted at a later time, but restrictions cannot be applied retroactively after domain names are registered.

Resolved, the Board thanks the GNSO for its continued attention and ongoing work on this topic, and requests that the GNSO continue its work on a policy recommendation on second-level protections for the IOC and Red Cross/Red Crescent names on an expedited basis.

Resolved (NG2012.09.13.01), if it is not possible to conclude the policy work prior to 31 January 2013, the Board requests that the GNSO Council advise the Board by no later than that date if it is aware of any reason, such as concerns with the global public interest or the security or stability of the DNS, that the Board should take into account in making its decision about whether to include second level protections for the IOC and Red Cross/Red Crescent names listed in section 2.2.1.2.3 of the Applicant Guidebook by inclusion on a Reserved Names List applicable in all new gTLD registries approved in the first round of the New gTLD Program.

Rationale for Resolution NG 2012.09.13.01

The New gTLD Program Committee is undertaking this action now to remain accountable to all parts of its community. The New gTLD Program Committee recognizes all of the work that has been done to date on this issue, and the work that is currently underway. For example, a GNSO Drafting Team has already provided recommendations on protections at the top level, and work is continuing on reviewing protections at the second level. There is also work ongoing regarding the broader question of protections at the first and second level for Inter Governmental Organizations (IGO). Through this resolution, the New gTLD Program Committee is working to address the advice of the GAC regarding providing protections to the IOC and Red Cross/Red Crescent names at the second-level within the first round of New gTLDs. This action is not intended to preclude or supplant the ongoing policy work within the community, nor is it intended to direct the initiation of policy development work within the GNSO. The New gTLD Program Committee supports the continued work on these topics within the GNSO, and specifically limits the effect of this resolution to the first round of New gTLDs, to allow for further policy to be developed and implemented.

This resolution is not expected to have an impact on ICANN's fiscal resources. Nor Is it expected to impact the security, stability or resiliency of the DNS.

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