Appendix 2 Materials Related to Geographic Names

A2.1 Checklist of Requirements

Applicants are required to submit the following documentation with their application, which will be verified through the Geographic Names Review (Section 7.5.3.2):

1. A signed letter of support or non-objection from the relevant government(s) or public authority(ies).

   1. The documentation of support or non-objection should include a signed letter from the relevant government(s) or public authority(ies).

   2. The letter must clearly express the government’s or public authority’s support for or non-objection to the applicant’s application and demonstrate the government’s or public authority’s understanding of the string being requested and its intended use.

   3. The letter should also demonstrate the government’s or public authority’s understanding that the string is being sought through the gTLD application process and that the applicant is willing to accept the conditions under which the string will be available, that is, entry into a Base Registry Agreement with ICANN requiring compliance with consensus policies and payment of fees.

   4. The letter of support or non-objection should be dated no more than four months from the opening of the New gTLD Program application submission period, otherwise a fresh letter of support or non-objection will be required.

2. Contact information for a designated person in case the Geographic Names Panel (GNP) needs clarification or has questions.

A2.2 Sample Letter of Support or Non-Objection from a Government Entity/Public Authority

[This letter should be provided on official letterhead]

Internet Corporation for Assigned Names and Numbers

12025 Waterfront Dr

Los Angeles, CA 90094

United States of America

Attention: New gTLD Program Team

Subject: Letter of support or non-objection for [Requested TLD]

This letter [confirms that the Government Entity/Public Authority fully supports][expresses the Government Entity/Public Authority’s non-objection to] the application for [Requested gTLD(s)] submitted to the Internet Corporation for Assigned Names and Numbers (ICANN) by [Applicant] under the New gTLD Program. As the [Minister/Secretary/Title], I am authorized by the [Government Entity/Public Authority] to provide this formal letter of support. [Government Entity/Public Authority], through the [Department/Division/Office], is responsible for [brief summary of functions and responsibilities]. The [Government Entity/Public Authority] is confident in [Applicant’s] capacity to manage the gTLD in a responsible and effective manner.

The [Government Entity/Public Authority] understands that the gTLD will be used to [Insert understanding of how the name will be used by the applicant. This could include policies developed regarding who can register a name, pricing model and management structures.].

The [Government Entity/Public Authority] supports the application for [Requested gTLD(s)], and understands that if it is successful, [Applicant] will be required to enter into a Base Registry Agreement with ICANN. In the event of a dispute between [Government Entity/Public Authority] and [Applicant], we understand that ICANN will comply with a legally binding order from a court within our jurisdiction.

[Optional] This application is being submitted as a Community Application. The [Government Entity/Public Authority] understands that the Registry Agreement between ICANN and the applicant (if successful) will incorporate the Community Registration Policies proposed in the application that are approved, as-is or with modifications, by ICANN. Following the delegation of the gTLD, if the [Government Entity/Public Authority] determines that the registry is not adhering to these registration policies, we may seek recourse through the Registry Restrictions Dispute Resolution Procedure (RRDRP).

[Optional] If this application is successful the [Government Entity/Public Authority] will enter into a separate agreement with the applicant. This agreement will define the terms of the [Government Entity/Public Authority] support for the operation of the gTLD, and any conditions under which that support may be withdrawn. ICANN will not be a party to this agreement, and its enforcement will rest solely with the [Government Entity/Public Authority].

The [Government Entity/Public Authority] understands that the Geographic Names Panel engaged by ICANN will conduct due diligence to verify the authenticity of this documentation. Should additional information be required, please contact [Name, Title, Contact Details] as the primary point of contact.

Thank you for the opportunity to support this application.

Yours sincerely,

[Signature]

[Full Name]

[Official Title]

[Government Entity/Public Authority Department]

[Contact Information]

A2.3 Separable Country and Territory Names List

gTLD application restrictions on country or territory names are tied to the property fields of the ISO 3166-1 standard. Notionally, the ISO 3166-1 standard has an “English short name” field which is the common name for a country or territory and can be used for such protections; however, in some cases this does not represent the common name. This list seeks to add additional protected elements which are derived from definitions in the ISO 3166-1 standard. An explanation of the various classes is included below.

Separable components of a country or territory name designated on the “Separable Country and Territory Names List,” or a translation of a name appearing on the list, in any language, will not be approved. See Section 7.5.1 Treatment of Country or Territory Names for more information.

Table A2-1: Separable Country and Territory Names List

Methodology

This Separable Country and Territory Names List is produced by ICANN through analysis of the ISO 3166-1 standard, in accordance with the eligibility criteria below. This version of the list was produced based on the data published by ISO on 2025-05-05.

Codes reserved by the ISO 3166 Maintenance Agency do not have any implication on this list, only entries derived from normally assigned codes appearing in ISO 3166-1 are eligible.

If an ISO code is struck off the ISO 3166-1 standard, any entries in this list deriving from that code must also be struck.

Eligibility

• Class A: The ISO 3166-1 English Short Name is composed of multiple, separable parts whereby the country or territory comprises distinct sub-entities. Each of these separable parts is eligible in its own right for consideration as a country or territory name. For example, “Antigua and Barbuda” is composed of “Antigua” and “Barbuda.”

• Class B: The ISO 3166-1 English Short Name (1) or the ISO 3166-1 English Full Name (2) contains additional language that describes the type of country or territory the entity is, which is often not used in common usage when referencing the country or territory. For example, one such short name is “The Bolivarian Republic of Venezuela” for a country in common usage referred to as “Venezuela.”

• Class C: The ISO 3166-1 Remarks column contains synonyms of the country or territory name, or sub-national entities, as denoted by “often referred to as,” “includes”, “comprises”, “variant” or “principal islands”.