<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Dear Katrin,<br><br>To be fair and clearer, may I suggest further amendments marked in red.....<br><br><p class="MsoNormal" style="font-family:Arial,Helvetica,sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif"></span><span class="gmail_default" style="font-family:arial,sans-serif"></span>2<font color="#000000">. An application for a city name, where the applicant declares that it intends to use the gTLD for purposes associated with the city name.<br><br></font></p><p class="MsoNormal" style="font-family:Arial,Helvetica,sans-serif"><font color="#000000"><u></u></font></p><p class="MsoNormal" style="font-family:Arial,Helvetica,sans-serif"><font color="#000000">City names present challenges because city names may also be generic terms or brand names, and in many cases city names are not unique.</font> <span style="color:rgb(0,112,192)">However, established lists can be used as objective references in the evaluation process.<br></span><br><font color="#000000">An application for a city name will be subject to the geographic names requirements (i.e., will require documentation of support or non-objection from the relevant governments or public authorities) if:<u></u><u></u></font></p><p class="MsoNormal" style="font-family:Arial,Helvetica,sans-serif"><font color="#000000">(a) It is clear from applicant statements within the application that the applicant will use the TLD primarily for purposes associated with the city name, </font><font color="#ff0000">and</font><u></u></p><p class="MsoNormal" style="font-family:Arial,Helvetica,sans-serif">(b)<font color="#ff0000">(i)</font> The applied-for string is a city name as listed on official city documents, or<u></u><u></u></p><p class="MsoNormal" style="font-family:Arial,Helvetica,sans-serif"><span style="color:rgb(0,112,192)">(b)</span><font color="#ff0000">(ii)</font><span style="color:rgb(0,112,192)"> The applied-for string is a </span><font color="#ff0000">(non-capital)</font><span style="color:rgb(0,112,192)"> city name as listed in <a href="http://unstats.un.org/unsd/demographic/products/dyb/dyb2015/Table08.xls" target="_blank"><span style="color:rgb(0,112,192)">http://unstats.un.org/unsd/demographic/products/dyb/dyb2015/Table08.xls</span></a>.</span></p></div><div><div dir="ltr" class="m_5653077343607329998m_-5923553629827458681m_1132239587857714962gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><span class="gmail_default" style="color:rgb(0,112,192)"></span><span style="font-family:Arial,Helvetica,sans-serif;color:rgb(0,112,192)">RATIONALE: This list contains capital cities and cities with 100 000 or more inhabitants and is thus very limited in nature. It would give applicants clear guidance and leaves no doubt whether their „category“ of TLD application is reflected in the AGB or not. If a .BRAND applies and </span><span style="font-family:Arial,Helvetica,sans-serif"><font color="#ff0000">meets the exemption </font></span><span style="font-family:Arial,Helvetica,sans-serif;color:rgb(0,112,192)">under (a), </span><span style="font-family:Arial,Helvetica,sans-serif"><font color="#ff0000">it</font></span><span style="font-family:Arial,Helvetica,sans-serif;color:rgb(0,112,192)"> has no further obligation; the same goes for any other category of TLD applications. </span><span style="font-family:Arial,Helvetica,sans-serif"><font color="#ff0000">The rule applicable to capital city names remains per the preceding section 2.2.1.4.2-1.</font></span></div><br><font face="arial, sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Thanks,</span><br>Justine </font><br>-----<br></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 26 Aug 2019 at 17:33, Katrin Ohlmer | DOTZON GmbH <<a href="mailto:ohlmer@dotzon.com" target="_blank">ohlmer@dotzon.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="DE">
<div class="m_5653077343607329998m_-5923553629827458681m_1132239587857714962gmail-m_-5582298316923481665WordSection1">
<p class="MsoNormal"><span>Dear All,<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>apparently there are positions in favour and in disagreement of the proposal for various reasons for the treatment of non-capital city names.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Let me put forward an amendment based on the proposal which aims at
<u></u><u></u></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="m_5653077343607329998m_-5923553629827458681m_1132239587857714962gmail-m_-5582298316923481665MsoListParagraph" style="margin-left:0cm"><span>adding greater clarity for applicants<u></u><u></u></span></li><li class="m_5653077343607329998m_-5923553629827458681m_1132239587857714962gmail-m_-5582298316923481665MsoListParagraph" style="margin-left:0cm"><span>not singling out one category of TLDs (.brands) and leaving undesired room for interpretation what happens with other categories of TLDs<u></u><u></u></span></li></ul>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>The text in blue is the addition to current rules:<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"></span>2. An application for a city name, where the applicant declares that it intends to use the gTLD for purposes associated with the city name.
<u></u><u></u></span></p>
<p class="MsoNormal"><span>City names present challenges because city names may also be generic terms or brand names, and in many cases city names are not unique.
<span style="color:rgb(0,112,192)">However, established lists can be used as objective references in the evaluation process.</span><u></u><u></u></span></p>
<p class="MsoNormal"><span><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"></span>An application for a city name will be subject to the geographic names requirements (i.e., will require documentation of support or non-objection from the relevant governments or public authorities)
if:<u></u><u></u></span></p>
<p class="MsoNormal"><span>(a) It is clear from applicant statements within the application that the applicant will use the TLD primarily for purposes associated with the city name, or<u></u><u></u></span></p>
<p class="MsoNormal"><span>(b) The applied-for string is a city name as listed on official city documents, or<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(0,112,192)">(c) The applied-for string is a city name as listed in
<a href="http://unstats.un.org/unsd/demographic/products/dyb/dyb2015/Table08.xls" target="_blank">
<span style="color:rgb(0,112,192)">http://unstats.un.org/unsd/demographic/products/dyb/dyb2015/Table08.xls</span></a>.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(0,112,192)"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"></span>RATIONALE: This list contains capital cities and cities with 100 000 or more inhabitants and is thus very limited in nature. It would give applicants clear guidance and leaves no doubt
whether their „category“ of TLD application is reflected in the AGB or not. If a .BRAND applies, it is covered under (a) and has no further obligations, the same goes for any other category of TLD applications.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>I’m looking forward to hearing your thoughts on this.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span>Kind regards<u></u><u></u></span></p>
<p class="MsoNormal"><span>Katrin<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="font-size:10pt;font-family:Arial,sans-serif">DOTZON GmbH - digital identities for tomorrow<br>
Akazienstrasse 28<br>
10823 Berlin<br>
Deutschland - Germany<br>
Tel: +49 30 49802722<br>
Fax: +49 30 49802727<br>
Mobile: +49 173 2019240<br>
<a href="mailto:ohlmer@dotzon.consulting" target="_blank">ohlmer@dotzon.consulting</a><br>
<a href="http://www.dotzon.consulting/" target="_blank">www.dotzon.consulting</a></span><span style="font-size:7.5pt;font-family:Arial,sans-serif"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">Besuchen Sie uns auf
<a href="https://de.linkedin.com/company/dotzon-gmbh" target="_blank">LinkedIn</a>.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:Arial,sans-serif"><br>
DOTZON GmbH<br>
Registergericht: Amtsgericht Berlin-Charlottenburg, HRB 118598<br>
Geschäftsführer: Katrin Ohlmer<br>
Sitz der Gesellschaft: Akazienstrasse 28, 10823 Berlin</span><u></u><u></u></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><b>Von:</b> Gnso-newgtld-wg-wt5 <<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org" target="_blank">gnso-newgtld-wg-wt5-bounces@icann.org</a>>
<b>Im Auftrag von </b>Olga Cavalli<br>
<b>Gesendet:</b> Samstag, 24. August 2019 19:52<br>
<b>An:</b> Icann Gnso Newgtld Wg Wt5 <<a href="mailto:gnso-newgtld-wg-wt5@icann.org" target="_blank">gnso-newgtld-wg-wt5@icann.org</a>><br>
<b>Betreff:</b> [Gnso-newgtld-wg-wt5] Remaining topics to be discussed on WT 5 next call on Wednesday<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dear WT5 colleagues,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I trust this email finds you well.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">As agreed in our last call, there would be a revision of 4 different issues, as a last chance to find a possible agreement in new text:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Subject 1: Final Discussion: Additional Geographic Terms<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Subject 2: TOPIC CLOSURE: Changes to String Contention Resolution<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Subject 3: Final Discussion: Non-Capital City Names<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Subject4 : TOPIC CLOSURE: Proposals to Increase or Decrease the Scope of Protections for Geographic Names<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">This email puts together all of them, please take a look, share your comments edits in this email list or in the shared document when available.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">We noted there are already comments in the email list on Subject 3. Please note that these and other suggestions will be summarised together with new input that these issues will receive during the next days.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Many thanks for your active involvement.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Kind regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Annebeth, Javier, Martin, and Olga<u></u><u></u></span></p>
</div>
<div>
<div style="border-top:none;border-right:none;border-left:none;border-bottom:1pt solid windowtext;padding:0cm 0cm 1pt">
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black;background:yellow">Subject 1: Final Discussion: Additional Geographic Terms</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">The WT is considering a proposal for additional geographic terms, which was discussed in detail on both email and most recently on the 21 August 2019 meeting.
As an action item, it was agreed that discussion should continue on list until <b>
28 August 2019</b>, where it is anticipated that a near-final proposal (if achievable) can be considered by the group on the call taking place that same day. To facilitate that discussion, the latest iteration of the proposal has been copied into a Google document
here: <a href="https://docs.google.com/document/d/1OKYbbvUVOqLJGk0a9S5K7H9sp-7833S6y5xg6c8yqa4/edit?usp=sharing" target="_blank">
https://docs.google.com/document/d/1OKYbbvUVOqLJGk0a9S5K7H9sp-7833S6y5xg6c8yqa4/edit?usp=sharing</a>. Staff has attempted to integrate some of the questions, concerns, and suggested improvements into that document for your consideration. Please either suggest
edits directly in the Google doc or reply to this email thread dedicated to this subject.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">In this case, unless consensus can be reached on this proposal, the co-leads do not envision that there will be any additional terms receiving geographic protections.<u></u><u></u></span></p>
<div style="border-top:none;border-right:none;border-left:none;border-bottom:1pt solid windowtext;padding:0cm 0cm 1pt">
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="color:black;background:yellow">Subject 2: TOPIC CLOSURE: Changes to String Contention Resolution</span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">As an action item on the 21 August 2019 meeting, the WT agreed to continue discussion on possible changes to string contention resolution. To date, there has
only been a single proposal put forth (see below), which the co-leads believe has received adequate discussion time, but has received considerable opposition both on list and during WT meetings. Discussion on this topic will be allowed to continue on list
until <b>28 August 2019. </b>Unless it becomes apparent to the co-leads that a consensus position is possible by that date, this topic will be considered closed.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">For avoidance of doubt, unless consensus is reached on this proposal, the 2012 Applicant Guidebook provisions will remain in place for string contention resolution. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Proposal:</span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US"> </span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Update Applicant Guidebook, Chapter 2.2.1.4.4 with:
</span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">If an application for a string representing a geographic name is in a contention set with applications for identical strings that have not been identified as
geographical names, the string contention will be resolved using the string contention procedures described in Module 4. <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Update Applicant Guidebook, Module 4. with:
</span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">A// In case there is contention for a string where one application intends to use the string as a non-capital city name or designated the TLD to targeting it
to a geographic meaning, preference should be given to the applicant who will use the TLD for geographic purposes if the applicant for the geoTLD is based in a country where national law gives precedent to city and/or regional names.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US">RATIONALE: This would reflect national law e.g. in countries like Switzerland and Germany, where e.g. city names have more rights that holders of the same
name. </span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">B// If there is more than one applicant for an identical string representing a geographic name, and the applications have requisite government approvals, the
applicant with the larger no of inhabitants will prevail over the smaller one. As the criteria “size” has been used in the CPE criteria, it is apparently a well-accepted criteria.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US">RATIONALE: This would reflect the current rule of the Applicant Guidebook capital city has priority over smaller city.</span></b><span lang="EN-US"><u></u><u></u></span></p>
<div style="border-top:none;border-right:none;border-left:none;border-bottom:1pt solid windowtext;padding:0cm 0cm 1pt">
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="color:black;background:yellow">Subject 3: Final Discussion: Non-Capital City Names</span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">The WT is considering [<span style="color:black;background:yellow">what appears to be a non-substantive – feel free to delete if you’re uncomfortable with this
statement</span>] proposal for a clarifying text change to section 2.2.1.4.2 part 2 in the Applicant Guidebook, on non-capital city names. This proposal has been discussed on both email and most recently on the 21 August 2019 meeting. As an action item, it
was agreed that discussion should continue on list until <b>28 August 2019</b>, where it is anticipated that a near-final proposal (if achievable) can be considered by the group on the call taking place that same day. To facilitate that discussion, the latest
iteration of the proposal has been copied into a Google document here, which includes Sophie’s latest proposal received after the 21 Aug meeting:
<a href="https://docs.google.com/document/d/13ZSuKTRm2y3mTg9FBZHv50ljP-dWE9N_okz9gcl2-2U/edit?usp=sharing" target="_blank">
https://docs.google.com/document/d/13ZSuKTRm2y3mTg9FBZHv50ljP-dWE9N_okz9gcl2-2U/edit?usp=sharing</a>. Please either suggest edits directly in the Google doc or reply to this email thread dedicated to this subject.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">For avoidance of doubt, unless consensus is reached on this proposal, the 2012 Applicant Guidebook provisions will remain in place for non-capital city names. <u></u><u></u></span></p>
<div style="border-top:none;border-right:none;border-left:none;border-bottom:1pt solid windowtext;padding:0cm 0cm 1pt">
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="color:black;background:yellow">Subject4 : TOPIC CLOSURE: Proposals to Increase or Decrease the Scope of Protections for Geographic Names</span></b><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">As an action item on the 21 August 2019 meeting, the WT agreed to continue discussion on several proposals that either increase or decrease the scope of protections
for Geographic Names. The relevant proposals are 8, 9, 10, 37, 6, and 7 and the fully detailed public comment can be found in the public comment review document here:
<a href="https://docs.google.com/spreadsheets/d/1WKSC_pPBviCnbHxW171ZIp4CzuhQXRCV1NR2ruagrxs/edit?usp=sharing" target="_blank">
https://docs.google.com/spreadsheets/d/1WKSC_pPBviCnbHxW171ZIp4CzuhQXRCV1NR2ruagrxs/edit?usp=sharing</a>. You can also review the public comment summary document beginning on page 32 here:
<a href="https://docs.google.com/document/d/1rsyxCEBd6ax3Rb_w1kms_E9n29XL1_lw3Yp9XQ4TeCY/edit?usp=sharing" target="_blank">
https://docs.google.com/document/d/1rsyxCEBd6ax3Rb_w1kms_E9n29XL1_lw3Yp9XQ4TeCY/edit?usp=sharing</a>. The co-leads believe that the proposals have received adequate discussion time and significantly, each appear to have received widely divergent opinions, which
leads us to believe that consensus will be difficult to achieve. However, discussion on this topic will be allowed to continue on list until
<b>28 August 2019. </b>Unless it becomes apparent to the co-leads that a consensus position is possible for any of these proposals by that date, this topic will be considered closed.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">For your convenience, the proposals are reproduced below:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><u><span lang="EN-US">Proposals:</span></u><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><u><span lang="EN-US">Increase in protections</span></u><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Proposal 8: If an applicant applies for a string that is confusingly similar to a geographic term that requires a letter of government support or non-objection,
the applicant should be required to obtain a letter of government support/non-objection. As an example, a common misspelling of a geographic name would be considered confusingly similar.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Proposal 9: At the end of the registry contract period, a government entity has the option of becoming engaged and can add provisions to the contract that specifies
conditions rather than there being an assumption that the contract will be renewed.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Proposal 10: A TLD associated with geography should be incorporated within the jurisdiction of the relevant government and subject to local law.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Proposal 37: Require that an applicant demonstrates that it has researched whether the applied-for string has a geographic meaning and performed any outreach
deemed necessary by the applicant prior to submitting the application. The proposal would be in addition to the existing measures related to the Geographic Names Panel.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><u><span lang="EN-US">Decrease in protections</span></u><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Proposal 6: Once a gTLD is delegated with an intended use that is geographic in nature, all other variations and translations of this term are unconditionally
available for application by any entity or person. Objection procedures could potentially still apply.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Proposal 7: An applicant for a string with geographic meaning must provide notice to each relevant government or public authority that the applicant is applying
for the string. The applicant is not required to obtain a letter of support on non-objection. This proposal relies on curative mechanisms to protect geographic names in contrast with support/non-objection requirements that are preventative in nature. Each
government or public authority has a defined opportunity to object based on standards to be established. The right to object expires after a set period of time. Objections are filed through one of the existing objection processes or a variation on an existing
process. A set of standards would need to be established to determine what constitutes a relevant government or public authority. This proposal could apply to all or some of the categories of geographic names included in the 2012 Applicant Guidebook.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> <u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> Kind regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Annebeth, Javier, Martin, and Olga<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Gnso-newgtld-wg-wt5 mailing list<br>
<a href="mailto:Gnso-newgtld-wg-wt5@icann.org" target="_blank">Gnso-newgtld-wg-wt5@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div><br></div>