<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:222915999;
mso-list-template-ids:1859013904;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:554313567;
mso-list-template-ids:912438820;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:1074738716;
mso-list-template-ids:-132075890;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:1806046445;
mso-list-template-ids:-83979414;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4
{mso-list-id:2069763500;
mso-list-template-ids:1005641170;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l4:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>After having received personal emails to clarify:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>“Ripe to abuse”: by applicant entities – who try to sneak under the radar in various sneaky ways.<br><br>So I support Jorge’s suggestion of the “repository”. But let’s keep the APPLICANTS out of the loop and have the geo panel organizing the notifications. It would be a NOTIFICATION ONLY – with no resulting rights. The mechanism would be meant to relieve Governments of the necessity to constantly monitor ICANN application rounds – and especially in the future the “ongoing application submission”; aka “no rounds”. Governments would however submit “geo names” (strings) – and only those would be subject of the notification. <br><br>ICANN would also provide access to this repository via easy to use web-based tool so applicants may “check” their string before they apply: this way they can’t later claim to “have never heard” about the geo entity.<br><br>So the notification portion of Jorge’s suggestion could read:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>“Upon closure of the application window ICANN’s geo panel will inform respective Government entities if a matching string has been applied for. ICANN will also provide a web based tool so applicants may check their string for a potential match with the repository.”<br>How the Governments will be informed exactly might be subject to “implementation”. Probably 1<sup>st</sup> via email – with the request for a confirmation of the receipt. If no receipt is received in X days a certified letter will follow – and the respective GAC member will be on notification as well. As this would be executed by the geo panel – there won’t be any “foul play”.<br><br><br>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Alexander<br><br><br><o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Gnso-newgtld-wg-wt5 [mailto:gnso-newgtld-wg-wt5-bounces@icann.org] <b>On Behalf Of </b>Alexander Schubert<br><b>Sent:</b> Montag, 19. August 2019 20:29<br><b>To:</b> gnso-newgtld-wg-wt5@icann.org<br><b>Subject:</b> Re: [Gnso-newgtld-wg-wt5] Preparation for WT5 Meeting 14 August and Final Topic Discussion - non-AGB terms<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I would STRONGLY oppose allowing applicants to notify the relevant Government authority. This would be ripe for abuse.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We are likely talking about a couple of affected applications only - and it would incur next to ZERO effort for the geo-panel to inform the respective Government contact. The geo panel could feed the system with the data while applications are feeded into the system - and the minute the application system is shutting down (application window closed) emails are being sent. My best guess is roughly 5 affected strings (gut feeling). How difficult can that be? <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This avoids complicated enforcement and validation issues like those that you mentioned.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Again: we are NOT talking about hundreds of instances - just a few strings. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This system becomes especially useful once we switch from rounds to ongoing application process:<o:p></o:p></p></div><div><p class=MsoNormal>We can't require all countries to monitor the irregularly occurring application submission instances.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Alexander<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div id="composer_signature"><div><p class=MsoNormal><span style='font-size:10.5pt;color:#364F67'>Sent from my Samsung device<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br>-------- Original message --------<br>From: Nick Wenban-Smith <<a href="mailto:Nick.Wenban-Smith@nominet.uk">Nick.Wenban-Smith@nominet.uk</a>> <br>Date: 8/19/19 19:29 (GMT+02:00) <br>To: <a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a>, <a href="mailto:susan.payne@valideus.com">susan.payne@valideus.com</a>, <a href="mailto:gnso-newgtld-wg-wt5@icann.org">gnso-newgtld-wg-wt5@icann.org</a> <br>Subject: Re: [Gnso-newgtld-wg-wt5] Preparation for WT5 Meeting 14 August and Final Topic Discussion - non-AGB terms <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks Jorge,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I am quite sympathetic to some of the applicants who experienced problems post application even where they had (apparently) notified the relevant countries or authorities of their intentions in advance, and in principle can see that a dialogue to explore concerns could be beneficial. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Just exploring this idea further, what should the sanction be if the notification/ contact obligation is not followed by the applicant?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>For confidentiality reasons and basic common sense I can see that applicants won’t want to advertise their applications before the close date (to avoid possible additional applications and contention). So this ties into the question about PICs and whether applications could by consent be varied (to include even possibly the string applied for). <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>But ultimately what would happen where you’ve got someone applying for a term (let’s say .bennevis the highest mountain in the UK but which also used as the name of multiple guest houses, whiskey distilleries etc and is subject to multiple trade mark registrations), they go through the notification process, the national authorities in Scotland are furious but have no remedy and cannot do anything about the application?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Best wishes<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Nick <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> Gnso-newgtld-wg-wt5 <<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org">gnso-newgtld-wg-wt5-bounces@icann.org</a>> <b>On Behalf Of </b><a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a><br><b>Sent:</b> 19 August 2019 07:43<br><b>To:</b> <a href="mailto:susan.payne@valideus.com">susan.payne@valideus.com</a>; <a href="mailto:gnso-newgtld-wg-wt5@icann.org">gnso-newgtld-wg-wt5@icann.org</a><br><b>Subject:</b> Re: [Gnso-newgtld-wg-wt5] Preparation for WT5 Meeting 14 August and Final Topic Discussion - non-AGB terms<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=DE-CH style='color:#1F497D'>Dear all</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=DE-CH style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Pursuant to last week’s call and especially the questions posed by Jeff and others during our discussions, let me make the following additional amendments </span><span style='color:red'>in red </span><span style='color:#1F497D'>to my proposal on on-AGB terms:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>==</span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo1'><span style='font-size:10.0pt'>Terms beyond the 2012 AGB rules with geographic meaning shall be subject to a contact obligation with the relevant public authorities, in order to put them on notice.</span><o:p></o:p></li></ul><p class=MsoListParagraph><span style='font-size:10.0pt'> </span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level1 lfo2'><span style='font-size:10.0pt'>For the application of the abovementioned rule <b>only</b> the following terms will be considered as being “terms with geographic meaning”:</span><o:p></o:p></li></ul><ul type=disc><ul type=circle><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level2 lfo2'><span style='font-size:10.0pt'>Adjectival forms of country names (country names to be identified from the ISO 3166-1 list);</span><o:p></o:p></li><li class=MsoNormal style='color:red;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l4 level2 lfo2'><span style='font-size:10.0pt;color:windowtext'>and/or other terms with geographic meaning, as notified by GAC Members states or other UN Member states to the ICANN Organization within a deadline of 12 months following the adoption of this proposal. </span><span style='font-size:10.0pt'>In such notifications the interested countries must provide the <b>source in national law or public policy</b> for considering the relevant term as especially protected. </span><span style='font-size:10.0pt;color:windowtext'>Interested countries would provide relevant contact details with said notification;</span><o:p></o:p></li></ul></ul><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt'><span style='font-size:10.0pt'> </span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'><span style='font-size:10.0pt'>Applicants for such a term will then be under an obligation to contact the relevant country. That contact notification must happen, at the latest, in the period between applications closing and reveal day, but an applicant may choose to notify earlier than this. <span style='color:red'>There is <b>no further obligation whatsoever arising from this provision</b> and it may not be construed as requiring a letter of non-objection from the relevant public authority.</span></span><o:p></o:p></li></ul><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>==</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>As explained during the call, the gist of this provision is focused on allowing for an early contact between applicants and interested countries. This, by itself, would probably avoid many conflictual situations, as applicants will be early aware of the interests of the relevant country, while countries will be notified well in advance of the plans of the applicant…</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Hope that the changes above will help us to safely land this improvement to the 2012 AGB…</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Best</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Jorge </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span lang=DE>Von:</span></b><span lang=DE> Cancio Jorge BAKOM <br><b>Gesendet:</b> Mittwoch, 14. August 2019 14:03<br><b>An:</b> 'Susan Payne' <</span><a href="mailto:susan.payne@valideus.com"><span lang=DE>susan.payne@valideus.com</span></a><span lang=DE>>; Icann Gnso Newgtld Wg Wt5 <</span><a href="mailto:gnso-newgtld-wg-wt5@icann.org"><span lang=DE>gnso-newgtld-wg-wt5@icann.org</span></a><span lang=DE>><br><b>Betreff:</b> AW: [Gnso-newgtld-wg-wt5] Preparation for WT5 Meeting 14 August and Final Topic Discussion</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=DE-CH> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=DE-CH style='color:#1F497D'>Dear Susan, dear all</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=DE-CH style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Thanks for the constructive spirit in making your proposal, which certainly would mean a step ahead in providing for a more stable and predictable framework for all interested parties.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>However, adjective forms of country names are but a very small subset of terms with a geographic meaning beyond the AGB terms…</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>At the same time, I understand the wish to have a closed list of terms, on which applicants could rely on before each round is opened.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>In this sense, please consider the following compromise proposal, based on my initial and your wording:</span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo4'><span style='font-size:10.0pt'>Terms beyond the 2012 AGB rules with geographic meaning shall be subject to a contact obligation with the relevant public authorities, in order to put them on notice.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo4'><span style='font-size:10.0pt'>For the application of the abovementioned rule <b>only</b> the following terms will be considered as being “terms with geographic meaning”:</span> <o:p></o:p></li></ul><ul type=disc><ul type=circle><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level2 lfo4'><span style='font-size:10.0pt'>Adjectival forms of country names (country names to be identified from the ISO 3166-1 list) and/or other terms with geographic meaning, as notified by GAC Members states or other UN Member states to the ICANN Organization within a deadline of 12 months following the adoption of this proposal;</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level2 lfo4'><span style='font-size:10.0pt'>Interested countries would provide relevant contact details with said notification;</span><o:p></o:p></li></ul></ul><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3 level1 lfo4'><span style='font-size:10.0pt'>Applicants for such a term will then be under an obligation to contact the relevant country. That contact notification must happen, at the latest, in the period between applications closing and reveal day, but an applicant may choose to notify earlier than this.</span><o:p></o:p></li></ul><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>I hope that we may agree on this contact requirement, which IMHO would help avoiding repeating long-standing conflicts in non-AGB applications with geographic meaning.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Kindly</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Jorge </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span lang=DE>Von:</span></b><span lang=DE> Gnso-newgtld-wg-wt5 <</span><a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org"><span lang=DE>gnso-newgtld-wg-wt5-bounces@icann.org</span></a><span lang=DE>> <b>Im Auftrag von </b>Susan Payne<br><b>Gesendet:</b> Mittwoch, 14. August 2019 12:29<br><b>An:</b> Icann Gnso Newgtld Wg Wt5 <</span><a href="mailto:gnso-newgtld-wg-wt5@icann.org"><span lang=DE>gnso-newgtld-wg-wt5@icann.org</span></a><span lang=DE>><br><b>Betreff:</b> Re: [Gnso-newgtld-wg-wt5] Preparation for WT5 Meeting 14 August and Final Topic Discussion</span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=DE-CH> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Dear Work Track 5 members </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Thank you to Olga for the clarification on next steps and circulating the various proposals. This email is in response to proposal 2, which was proposed by Jorge Cancio. I am proposing this variation to your proposal as an adviser to an number of new gTLD operators and potential future round applicants, .Brands and non-brands, and I have also taken the opportunity to discuss this with a few other WT5 participants.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Jorge, I do recognise your concerns and desire to set up a process which would give relevant governments/public authorities advance notice that an application is being filed which may match a term that has a geographic meaning in the particular country. However, I cannot support your proposal in full. The AGB2012 tried to give certainty to all by setting out identifiable lists. Imposing a requirement for research outside of such clear lists is not something that can be objectively measured or complied-with. Whether an applicant has done the appropriate level of research is too subjective and open for interpretation. An applicant may consider that they have done so, but another person’s interpretation may differ, and what would be the impact on an application in that scenario? It does not seem to me that this delivers the certainty we all want to achieve.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Your proposal would also create a new Geographic Names Panel which would have a much larger remit than the one currently in the AGB2012. The role of the Geo Names Panel under the AGB2012 was to check whether any of the applications were “geographic” as that term was used in the Guidebook. In other words, was a term on the relevant lists, if so, was it a term which was prohibited or one which required support/non-objection and, if the latter, was the relevant documentation in order? This was an objective test. Appointing a panel to determine whether an applicant has done the requisite amount of diligence in determining whether its application has any geographic meaning would require that panel to make subjective determinations on matters where reasonable minds could easily differ. This increases uncertainty and could also dramatically increase the costs of the program. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Nevertheless, in the interests of exploring a possible compromise which would, I think, address the concerns that you and some other governments have about descriptors for your country and citizenry, but without introducing open-ended and uncertain obligations, I would like to propose the following variation on your proposal:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo5'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>That this should apply to adjectival forms of country names (country names to be identified from the ISO 3166-1 list); This would capture terms like .swiss, .american, .british, etc.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo5'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Since this relates only to these terms, which have a close association with the country name, there is no intended use requirement;</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo5'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Countries who desire to be notified of applications which match such terms should identify that this is the case before the application window opens so that applicants have certainty. The practical and fair way to do this would be for countries who have this requirement to confirm this and provide relevant contact details before the AGB is finalised so that these details can be included in, or linked-from, the AGB;</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo5'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Applicants for such a term will then be under an obligation to notify. That notification must happen, at the latest, in the period between applications closing and reveal day, but an applicant may choose to notify earlier than this.</span><o:p></o:p></li></ul><p class=MsoListParagraph><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>I hope that this might serve as a compromise which the work track members as a whole might be able to support. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:black'>Susan Payne</span></b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:black'>Head of Legal Policy <br><b>Valideus <br></b>D: +44 (0) 20 7421 8255</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:black'>E: </span><a href="mailto:susan.payne@valideus.com"><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>susan.payne@valideus.com </span></a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> Gnso-newgtld-wg-wt5 <<a href="mailto:gnso-newgtld-wg-wt5-bounces@icann.org">gnso-newgtld-wg-wt5-bounces@icann.org</a>> <b>On Behalf Of </b>Olga Cavalli<br><b>Sent:</b> 12 August 2019 20:33<br><b>To:</b> Icann Gnso Newgtld Wg Wt5 <<a href="mailto:gnso-newgtld-wg-wt5@icann.org">gnso-newgtld-wg-wt5@icann.org</a>><br><b>Subject:</b> [Gnso-newgtld-wg-wt5] Preparation for WT5 Meeting 14 August and Final Topic Discussion<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Dear Work Track 5 members,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I trust this email finds you well.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thank you to everyone who participated in this week’s call and contributed on the mailing list to recent discussions. As documented in the meeting notes, there are several items that require your attention between now and our next call on Wednesday 14 August at 14:00 UTC. Please see the slides from Wednesday’s call (attached) for background on these issues. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i>By including these items in the email we are not implying that these proposals have support from the leadership team, but rather that we are attempting to assess whether any of these proposals are likely to receive consensus support as is or with some level of modification.</i></b> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Please provide your views on the proposals below by<b> tomorrow</b> <b>Tuesday, 13 August</b> to help the co-leaders assess whether any might be able to receive consensus support. Please include a rationale with your response.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><u>-</u><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><u>1. Translations/Languages</u>: At this stage, there does not seem to be agreement to change the “in any language” standard for protection/restriction of Country and Territory Names and Capital City Names. If there is no agreement on a specific change, the status quo from the 2012 New gTLD Round will remain. If you think the Work Track co-leaders have missed something and there is, indeed, a path forward that can achieve consensus, this is your final opportunity to raise it. However, if there is agreement by the WG to change the “in any language” standard then the following two proposals will be considered.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>A WT member had previously put forward a proposal on transposition of Capital City Names that was proposed as an addition to the “official and UN languages” proposal (see attached slides). <b>For Capital City Names, require support/non-objection letter for the transposition of accented and diacritic characters in Latin-based scripts to their equivalent ASCII root. This would protect for example sao-tome as a DNS-Label of São Tomé alongside the IDN version of the name (xn—so-tom-3ta7c). Additional example provided in the proposal: denhaag/den-haag would require letter of support/non-objection. </b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>An addition, a WT member has proposed the following: In AGB 2.2.1.4.1 Treatment of Country or Territory Names, replace “in any language” with:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>a. The official language of the country or territory; and<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>b. The de facto official language of the country or territory; and<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>c. The UN languages; and<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>d. The translations set out in a, b or c with the substitution of diacritical characters for ASCII characters, special characters, or spaces (eg. Austria as Österreich, or Osterreich).<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>For the purposes of the Applicant Guidebook, a de facto official language of a country or territory is a language that is used for official translations of the country or territory’s national laws. <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>For 2.2.1.4.2 part 1 on capital city names, rephrase to the following language:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>An application for any string that is a representation of the capital city of any country or territory listed in the ISO 3166-1 standard in<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>a. The official language of the country or territory of the capital city; or<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>b. The de facto official language of the country or territory of the capital city; or<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>c. The UN languages; or<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>d. Either a, b or c with the substitution of diacritical characters for ASCII characters, special characters, or spaces (eg Den Haag as denhaag or den-haag, São Tomé as sao-tome, saotome, sãotomé, são-tomé)<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <i>Rationale:</i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i>There appears to be general agreement in the work track that the current text referring to “all languages” is unmanageable and does not provide certainty for potential applicants. The concerns flagged around previous proposals to narrowing the scope relate to uncertainty and a lack of predictability. Further, on the 17 July call the position appeared to me to be that UN languages were not necessarily relevant and excluded other relevant languages to communities. However, I appreciate that some people feel strongly about this and have included them in the proposal. To ensure that relevant languages are relied upon and acknowledging not all countries and territories have a clearly defined official language, I suggest we include de facto official languages with a clear and defined scope. Official translations of national laws are a public and verifiable source that is readily available and reflects the language(s) the people of the country or territory speak ie the language(s) are relevant. </i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><u>2. Additional Categories of Terms Not Included in the 2012 AGB</u>: Last week, there was a final call for proposals that members believe could achieve consensus support on this topic. One proposal was put forward: <b>“Terms beyond the 2012 AGB rules with geographic meaning (e.g. adjective forms of countries, such as “Swiss”) which may be identified as such with a modicum of diligence by the prospective applicant and/or after consulting, under confidentiality terms, the Advisory Geonames Panel, shall be subject to a contact obligation with the relevant public authorities, in order to put them on notice.”</b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Other WT5 members suggest that this would only apply if the gTLD or string was being used in connection with the geographic meaning.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><u>3. String Contention Resolution – Geographic Names</u>: Last week one proposal was put forward that required additional time for WT5 members to review:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>Update Applicant Guidebook, Chapter 2.2.1.4.4 with: 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. </b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b> </b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>Update Applicant Guidebook, Module 4. with:</b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>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.</b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i>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.</i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>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.</b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i>RATIONALE: This would reflect the current rule of the Applicant Guidebook capital city has priority over smaller city.</i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><u>4. Member Proposals from the Initial Report on Scope of Protections (Proposals</u> <b><u>6, 7, 8, 9, 10, and 37)</u></b><u>:</u> Over the last couple of months, we have been referencing <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1rsyxCEBd6ax3Rb-5Fw1kms-5FE9n29XL1-5Flw3Yp9XQ4TeCY_edit-3Fts-3D5ce64d6d-23heading-3Dh.j7jy935ryg4k&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=ibk5NLRIVEyM8BmUAuiyFZFoV87dA6GCJADyQmNq0Zk&s=kqYJykVu4sGjVFR2cFjplDm81zbVZ0GnnkdEfx3RMbc&e=" target="_blank">this document[docs.google.com]</a>, which summarizes comments on the WT5 supplemental Initial Report (full text of comments <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spreadsheets_d_1WKSC-5FpPBviCnbHxW171ZIp4CzuhQXRCV1NR2ruagrxs_edit-3Fusp-3Dsharing&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=ibk5NLRIVEyM8BmUAuiyFZFoV87dA6GCJADyQmNq0Zk&s=Bsx0wWBZYVTvb6bMWJTTbgnuVlPV4GRSN_CBc22YpTM&e=" target="_blank">here [docs.google.com]</a>). Beginning at the bottom of page 32 of the summary document, you will find a summary of comments on some of the proposals included in the report. Elements of these proposals have been discussed in the context of revisiting the draft recommendations as well as broader discussions in the Work Track. Public comments reflect that there is a mix of perspectives in the community on the different proposals – some in favor and some opposed to each, similar to what the co-leaders have observed in WT discussions. At this stage, the co-leaders do not anticipate that re-reviewing the proposals will lead to agreement in the Work Track on specific changes to the draft recommendations.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><u>5. Non-Capital City Names</u>: A WT member has proposed amending the text in AGB 2.2.1.4.2 part 2 on non-capital city names by adding the blue text: <span style='color:#4472C4'>“It is clear from applicant statements within the application that the applicant will use the TLD primarily for purposes associated with the city name. For the avoidance of doubt, where the applicant states in their application that they intend to use the TLD as a .Brand (intend to have Specification 13 in their Registry Agreement) it will be taken that the TLD will not be used primarily for purposes associated with the city name.”</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i> Rationale:</i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i>The current AGB text states that “city names present challenges because city names may also be generic terms or brand names, and in many cases city names are not unique”. This language does not aim to change the position from the AGB 2012, but merely aims to provide greater clarity and certainty for potential applicants. At the same time, it ensures that the relevant authorities are consulted when an applicant intends to use a TLD for purposes associated with a city. If a government or local authority is concerned with an application, they are not precluded from filing an objection (as they could in 2012) or filing their own application. The current rules on resolving contention sets in AGB 2.2.1.4.4 or module 4 will not be impacted by the text.</i><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Please remember to provide your views on these below by<b> tomorrow</b> <b>Tuesday, 13 August,</b> including a rationale with your response.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Kind regards,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Olga<o:p></o:p></p></div></div></div></div><div id=DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><table class=MsoNormalTable border=1 cellspacing=3 cellpadding=0 style='border:none;border-top:solid #D3D4DE 1.0pt'><tr><td width=59 style='width:41.25pt;border:none;padding:13.5pt .75pt .75pt .75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank"><span style='text-decoration:none'><img border=0 width=46 height=29 id="_x0000_i1025" src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"></span></a><o:p></o:p></p></td><td width=474 style='width:352.5pt;border:none;padding:12.75pt .75pt .75pt .75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:13.5pt'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#41424E'>Libre de virus. </span><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank"><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#4453EA'>www.avast.com</span></a><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#41424E'> </span><o:p></o:p></p></td></tr></table><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see <a href="https://comlaude.com" target="_blank">www.comlaude.com</a> <o:p></o:p></p></div></div></body></html>