Geographic Names Proposals
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2 Character3 CharacterCountry and Territory NamesCity/State/Region NamesOther Strings with Possible Geographic Significance
2
Webinar Presentation / ProposalOn the ISO listNot on the ISO list (ASCII)Non-ASCIIOn the ISO listNot on the ISO list (ASCII)Non-ASCIIOn the ISO list and translations (Long and Short Form)How a country is commonly known. ref. AGB Section 2.2.1.4.1 (vii) (ASCII & Non-ASCII)Captital City Names of country or territory (in national languages and scripts/in other languages)City Names (in national languages and scripts/in other languages)Sub-national places listed in the ISO 3166-2 standard (in national languages and scripts/in other languages)UNESCO region (in national languages and scripts/in other languages)Rivers, mountains, valleys (in national languages and scripts/in other languages)Culturally significant terms (in national languages and scripts/in other languages)
3
WG Co-Chairs Compromise StrawpersonNot allowed - Must be three or more charactersTwo character IDNs are allowed unless (a) it is visually similar to any one-character label (in any script); or (2) it is visually similar to any possible two character ASCII combination. See Section 2.2.1.3.2, Part III.Allowed, unless applicant desires to use the string in a geographic capacity. In this case, the applicant needs to get a Letter of Consent or Non-objection from the applicable government(s). If the string is contained within the advisory Repository of Geographic names (RGN), then provisions related to the RGN apply.

*Note, the RGN is defined in the WG Co-Chairs Geographic Names Strawperson, available here: https://docs.google.com/document/d/1m69loOZthxrQdcCj1dIUJLkezQXr9rwGxXrechdFv1Y/edit?usp=sharing
Allowed, unless it is in the RGN. If the string is contained within the RGN (described in compromise proposal), then provisions related to the RGN apply.If it is a translation of a string on the ISO list:
Allowed unless applicant desires to use the string in a geographic capacity. In this case, the applicant needs to get a Letter of Consent or Non-objection from the applicable government(s). If the string is contained within the RGN (described in compromise proposal), then provisions related to the RGN apply.

If it is not a translation of a string on the ISO list:
Allowed, unless it is in the RGN. If the string is contained within the RGN (described in compromise proposal), then provisions related to the RGN apply.
Not allowed per AGB Section 2.2.1.4.1Government support or non-objection required per AGB Section 2.2.1.4.2Allowed, unless applicant desires to use the string in a geographic capacity. In this case, the applicant needs to get a Letter of Consent or Non-objection from the applicable government(s). If the string is contained within the RGN (described below), then provisions related to the RGN apply.Government support or non-objection from at least 60% of the respective national governments in the region required per AGB Section 2.2.1.4.2. No more than one written statement of objection.For iterms in the Repository of Geographical Names (RGN) (see proposal for details):

1. If the proposed use by the applicant of the TLD is in its geographic sense, the applicant must reach out to the authorized contact (s) in the impacted country (or countries) for a Letter of Consent or Non-objection.

2. If the proposed use by the potential applicant is in a context that does not imply any association with the country, the potential applicant can either:
a. Get a Letter of Consent or Non-objection from the applicable government(s); or

b. Submit a Geo-Pic that the TLD Applicant will not use TLD in a manner that falsely suggests to the public that a connection exists between the TLD or its Operator and the geographic term. The Geo-PIC will be included in the TLD Applicant’s Registry Agreement, should such Agreement be executed by ICANN.
4
GNSO Policy RecommendationsNot allowed - Must be three or more charactersAllowed - Applicants must represent that the use of the proposed string is not in violation of the national laws in which the applicant is incorporated. Challege mechanisms are available to governments.Allowed - Applicants must represent that the use of the proposed string is not in violation of the national laws in which the applicant is incorporated. Challege mechanisms are available to governments.Allowed - Applicants must represent that the use of the proposed string is not in violation of the national laws in which the applicant is incorporated. Challege mechanisms are available to governments.
5
Current AGBNot allowed - Must be three or more charactersTwo character IDNs are allowed unless (a) it is visually similar to any one-character label (in any script); or (2) it is visually similar to any possible two chracter ASCII combination. See Section 2.2.1.3.2, Part III.Not allowed per AGB Section 2.2.1.4.1AllowedNot allowed per AGB Section 2.2.1.4.1Government support or non-objection required per AGB Section 2.2.1.4.2If intended to be used for purposes associated with the city name, government support or non-objection required per AGB Section 2.2.1.4.2Government support or non-objection required per AGB Section 2.2.1.4.2Government support or non-objection from at least 60% of the respective national governments in the region required per AGB Section 2.2.1.4.2. No more than one written statement of objection.Allowed
6
Olga Cavalli and Jorge CancioNot allowed - Must be three or more charactersTwo character IDNs are allowed unless (a) it is visually similar to any one-character label (in any script); or (2) it is visually similar to any possible two chracter ASCII combination. See Section 2.2.1.3.2, Part III.Not allowed per AGB Section 2.2.1.4.1AllowedNot allowed per AGB Section 2.2.1.4.1Government support or non-objection required per AGB Section 2.2.1.4.2If intended to be used for purposes associated with the city name, government support or non-objection required per AGB Section 2.2.1.4.2Government support or non-objection required per AGB Section 2.2.1.4.2Government support or non-objection from at least 60% of the respective national governments in the region required per AGB Section 2.2.1.4.2. No more than one written statement of objection.Draft proposal for repository of terms with Geographic significance to be maintained by ICANN.
•Governments, public authorities and relevant lists and/or terms to the repository.
•Effective public consultation requirement: opportunity to raise any concerns about any such strings.
•Contact obligation: In case of a match or a confusingly similar name, applicant would be obliged to contact the relevant government, public authority, etc.
•No objection requirement: Applicant would be required to obtain a non-objection statement from the respective community and government
•Dispute resolution process in cases that a non-objection is not obtained.
•Documentation obligation
7
Alexander SchubertNot allowed - Must be three or more charactersDid Not AddressAllowed - Government support or non-objection required (optionally, support or non-objection also required from relevant GAC member and ccTLD manager)AllowedAllowed - Government support or non-objection required (optionally, support or non-objection also required from relevant GAC member and ccTLD manager)Did Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not Address
8
Geo TLD GroupDid Not AddressDid Not AddressDid Not AddressAllowed - Government support or non-objection required; geo TLDs get priority in case of contention.Did Not AddressDid Not Address
9
BRGDid Not AddressDid Not AddressDid Not AddressAllowed - no restrictions to the use of geographic terms at the top level for applicants that hold a matching trademark, whereby the use of the TLD is to identify the brand and not to represent the geographic term, and where there is no conflict with national or international law.
10
CENTROnly allowed as ccTLDs.Not allowed - reserved for possible future use as ccTLDs.Did Not AddressIf allowed, at a minimum should only be delegated with government support or non-objection per AGB Section 2.2.1.4.2.Did Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not Address
11
Thomas LowenhauptDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressDid Not AddressWork towards multistakeholder approach to managing city TLDs.Did Not AddressDid Not AddressDid Not AddressDid Not Address
12
Paul McGradyIf geographic or territorial term is protected under national law ("Geographic Protected Term), a timely GAC Objection (several possible working definitions) may result in applicant agreeing to a Public Interest Commitment that the TLD Applicant not use TLD in a manner that falsely suggests to the public that a connection exists between the TLD or its Operator and the Geographic Protected Term (“GeoPIC”). GeoPIC will be included in the TLD Applicant’s Registry Agreement.
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...