<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>Dear Emily, Dear Friends and Colleagues:</p><p>Please find below and in the attachments, my initial - and no doubt partial - comments on this initial draft.<br><br>I note that the balance of the presentation leans too heavily towards maintaining the 2007 and 2012 situation. Also there are serious lacunae notably concerning ISO 4217 alpha-3 codes and Geographical Indications.</p><p>Regards</p><p>Christopher Wilkinson</p><p><br></p><p>----------------------------</p><p><br></p><p lang="en-US"><strong>Draft of Initial Report Sections c, d, and e.<br><br>Initial comments, corrections and suggestions</strong></p><p lang="en-US"><br>Christopher Wilkinson</p><p lang="en-US"><br>This is a brief reaction and correction to the Draft of Initial Report Sections, of 27 September. I expect that we shall have an opportunity to discuss this at the next conference call on 3 October. Meanwhile I must say that the balance of this initial draft leans too heavily towards maintaining the 2007 and 2012 positions whereas the very creation and cross-community composition of WT5 was designed to correct those previous experiences.<br><br><strong>RECOMMENDATION #1</strong></p><p lang="en-US">The use of the term 'certain strings' implies prematurely that there will be other strings that are not protected. There is not a consensus on that point.<br><br>Remedy: please delete 'certain'.<br><br><strong>RECOMMENDATIOM #11</strong><br><br>This text, and elsewhere, omits to refer to the issue of non-geographical use. Whereas that has been a major issue for Work Track 5. The recommendation must address non-geographical use as also requiring prior authorisation.</p><p lang="en-US">Use of geographical names for 'generic and brand contexts' has the major Drawback that future geographical use would be prevented, whereas under Proposed Problem<strong>6.1</strong>, (p.16) we have Proposed solution 6.1.2 “… to maximize the opportunities for future applicants for geographic names.” (Names that meanwhile have been freely available for non-geographic use. I don't think so!)</p><p lang="en-US">This dichotomy must be explained clearly in the text.</p><p lang="en-US">Remedy: The <u>only</u>exception to geographic use could be limited to <u>pre-existing</u>trademark rights recognised in the jurisdiction concerned and subject to prior authorisations.<br><br><strong>Recommendation #12</strong></p><p lang="en-US">In spite of several references in meetings and on the List, there is still no reference to the three letter currency codes in ISO 4217. The currency codes are derived directly from ISO 3166, and consequently in this context are the competence of WT5.<br><br>Failure to appropriately protect the currency codes (which are by definition national or regional) could give rise to serious difficulties further down the line. I would argue that this is even more important than the three letter country codes in ISO 3166.<br><br><strong>d. What are the options under consideration…</strong></p><p lang="en-US"><strong>Non-Capital City Names</strong></p><p lang="en-US">The text, again, presupposes that non-geographical use is not protected. We know very well by now that this would not be acceptable. <br><br>Specifically, the reference to 'curative' measures in this context is unrealistic. <br><br>Furthermore the appeal to 'the overall design of the program…' is perplexing. What is this 'overall design' that obliges WT5 to consider unsustainable proposals?</p><p lang="en-US">The reference in sub para 3 to 'Objectors pay for the objection…' is so far off-the-wall, that I am surprised that it is still being maintained. Note that in any eventual 'curative' regime for non-geographic use, most of the objectors might be private parties.</p><p lang="en-US"><strong>Sub para 8 on preventing misrepresentation (p.10) and elsewhere:</strong><br><br></p><p lang="en-US">This proposal has been made very recently by one WT5 member, several other members have already explained why it falls far short of adequate protection of geographic names and it has not yet been discussed by WT5 as a whole. It is surprising that it has already made it to an 'Option' in thisca Draft Initial Report. It would be a large step backwards in the existing levels of protection.<br><br>N.B. The concept of a 'bright-line rule' (p.11) is not widely used or understood (not included in the OED). Quite apart from the merits of the case, if any, that expression is likely to suffer considerably in translation.<br><br></p><ol start="3"><li><p lang="en-US" style="text-align: left;"><strong>Too Little Restriction… (p.14)</strong><br><br>The drawbacks to Proposed Solution 3.2.1 should be clearly expressed, including a clear need in such a case for Incorporation in the Jurisdiction concerned.<br><br>We know from ccTLD experience that it can be quite difficult and time consuming for a government to 'become engaged' with a misappropriated TLD that is operated outside the national jurisdiction.<br><br></p><p lang="en-US" style="text-align: left;"><strong>Additional Categories or Terms (p.20) – Geographical Indications<br><br></strong>One would have thought, after all the time and effort that has been expended on Work Track 5, that there should be a specific Recommendation on Geographical Indications. To find these relegated, again, to an afterthought right at the end of the document, is not correct.<br><br>We know from the previous Round that the issue is a live one and must be addressed. Appropriate text is available on the List and in the Transcripts.<br><br></p><p lang="en-US" style="text-align: center;"><br>____________<br><br><br></p><p lang="en-US" style="text-align: left;">CW/ 28 September 2018<br><br><br></p><p lang="en-US"><strong><br><br><br></strong><br></p></li></ol><p lang="en-US"><br><br><br></p><p lang="en-US"><br><br><br></p><blockquote type="cite"><!-- [if gte mso 9]><xml>
<o shapedefaults v:ext="edit" spidmax="1026" ></o>
</xml><![endif] --><!-- [if gte mso 9]><xml>
<o shapelayout v:ext="edit">
<o idmap v:ext="edit" data="1" ></o>
</o:shapelayout></xml><![endif] -->El 27 de septiembre de 2018 a las 20:11 Emily Barabas <emily.barabas@icann.org> escribió:<br><br><div class="ox-db307c077f-WordSection1"><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">Dear WT5 members,</span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;"> </span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">Please find attached draft text for the following sections of the Initial Report: </span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;"> </span></p><ul style="margin-top: 0cm;" type="disc"><li class="ox-db307c077f-MsoListParagraph" style="margin-left: 0cm;"><em><span style="font-size: 11.0pt;">c. What are the preliminary recommendations and/or implementation guidelines?<u></u></span></em></li><li class="ox-db307c077f-MsoListParagraph" style="margin-left: 0cm;"><em><span style="font-size: 11.0pt;">d. What are the options under consideration, along with the associated benefits / drawbacks?<u></u></span></em></li><li class="ox-db307c077f-MsoListParagraph" style="margin-left: 0cm;"><em><span style="font-size: 11.0pt;">e. What specific questions are the PDP WG seeking feedback on?<u></u></span></em></li></ul><p class="ox-db307c077f-MsoNormal"><em><u><span style="font-size: 11.0pt;"><span style="text-decoration: none;"> </span></span></u></em></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">These sections will be discussed on our upcoming call scheduled for Wednesday 3 October at 20:00 UTC. <strong>Please review this document prior to the call.</strong> <strong>If you would like to provide comments or raise concerns about sections of the text prior to the call for further discussion on the call, please send your comments in the body of an email, clearly identifying the page number and passage on which you are commenting. Please <u>do not</u> send your own redline version of the text to the mailing list. </strong>Given the very large number of WT members, it will be very difficult to reconcile many different redline versions. </span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;"> </span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">The following sections of the report are still being drafted and will be shared when ready:</span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;"> </span></p><ul style="margin-top: 0cm;" type="disc"><li class="ox-db307c077f-MsoListParagraph" style="margin-left: 0cm;"><em><span style="font-size: 11.0pt; color: black;">a. What is the relevant 2007 policy and/or implementation guidance (if any)?</span></em></li><li class="ox-db307c077f-MsoListParagraph" style="margin-left: 0cm;"><em><span style="font-size: 11.0pt; color: black;">b. How was it implemented in the 2012 round of the New gTLD Program?</span></em></li><li class="ox-db307c077f-MsoListParagraph" style="margin-left: 0cm;"><em><span style="font-size: 11.0pt; color: black;">f. Deliberations</span></em></li><li class="ox-db307c077f-MsoListParagraph" style="margin-left: 0cm;"><em><span style="font-size: 11.0pt; color: black;">g. Are there other activities in the community that may serve as a dependency or future input to this topic?</span></em></li></ul><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;"> </span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">The Deliberations section will contain the summary of different positions and perspectives raised in WT discussions and on the mailing list. </span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;"> </span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">Kind regards,</span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">Emily</span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;"> </span></p><p class="ox-db307c077f-MsoNormal"><strong><span style="font-size: 11.0pt;">Emily Barabas </span></strong><span style="font-size: 11.0pt;">| Policy Manager</span></p><p class="ox-db307c077f-MsoNormal"><strong><span style="font-size: 11.0pt;">ICANN</span></strong><span style="font-size: 11.0pt;"> | Internet Corporation for Assigned Names and Numbers</span></p><p class="ox-db307c077f-MsoNormal"><span style="font-size: 11.0pt;">Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976</span></p><p class="ox-db307c077f-MsoNormal"> </p></div></blockquote><p><br> </p><blockquote type="cite">_______________________________________________<br>Gnso-newgtld-wg-wt5 mailing list<br>Gnso-newgtld-wg-wt5@icann.org<br>https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5</blockquote></body></html>