<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Thanks Christopher.<br><br><div id="AppleMailSignature">Javier Rúa-Jovet<div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">+1-787-396-6511</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">twitter: @javrua</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">skype: javier.rua1</span></div><div><font color="#000000" style="background-color: rgba(255, 255, 255, 0);"><a href="https://www.linkedin.com/in/javrua" style="background-color: rgba(255, 255, 255, 0);">https://www.linkedin.com/in/javrua</a> </font></div><div><br></div></div></div><div><br>On Mar 25, 2018, at 3:12 PM, "<a href="mailto:lists@christopherwilkinson.eu">lists@christopherwilkinson.eu</a>" <<a href="mailto:lists@christopherwilkinson.eu">lists@christopherwilkinson.eu</a>> wrote:<br><br></div><blockquote type="cite"><div><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Dear WT5 Participants:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Further to the Wt5 meeting in San Juan on 14 March, this is just to recall the main points that I made during that discussion.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>1. For the new gTLD PDP to move forward with a reasonable delay, we need a new geo-TLD policy now. It would not be a good idea to wait for, or to out-source to other external entities, although in due course, external contributions may become relevant.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>2. I suggested that WT5 would save time by discontinuing discussion about ISO 3166. That is an international standard for codes and names representing countries and their subdivisions. As such, it is a well codified sub-set of the generality of geographical names. The bottom line is that within the scope of ISO 3166, ICANN is bound to respect the international standard.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>3. It is also not advisable to pursue the idea that the 2012 Applicant Guide Book (AGB) definition of geo-names is a relevant ‘default’. That text failed to address several classes of names that are of significant interest to user communities, a lacunae which gave rise to several disagreements and delays last time around. That should be corrected for the next round, as unambiguously as possible, in the interests of transparency and predictability for the individual users in the locations concerned. </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>In that context, I regret that the WT5 Terms of Reference do not address those issues explicitly. They will now have to be addressed by WT5.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>3. Geographical names are not Generic in the usual semantic or, indeed, ICANN sense. Nearly all of those names are specific to places, cultures, regions, communities and their local economies.</span><br></blockquote><blockquote type="cite"><span>The fact that GNSO has taken the lead in the PDP WT5, does not diminish in any way the specific characteristics of geo-names.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The approach to geographical names requires a tailored approach to the evaluation and implementation of such applications, to which I shall return in due course as the WT5 agenda evolves.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Regards</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Christopher Wilkinson</span><br></blockquote><span></span><br><span>PS: Resending, because the original message was sent from a non-WT5 registered address. Apologies for any duplication.</span></div></blockquote></body></html>