<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><blockquote type="cite"><p style="margin-bottom: 0in;">Dear Martin Sutton, Dear WT5 Co-Leads:</p><p style="margin-bottom: 0in;"><br></p><p style="margin-bottom: 0in;">Thank you for this update, with a view to the next WT5 meeting on Wednesday 4 April (14.00 UTC).</p><p style="margin-bottom: 0in;"><br></p><p style="margin-bottom: 0in;">May I say that, for many participants, in view of the Easter long weekend, this is extremely short notice</p></blockquote><blockquote type="cite"><p style="margin-bottom: 0in;">I have several comments and suggestions:</p></blockquote><p style="margin-bottom: 0in;"><br></p><ol><li><p style="margin-bottom: 0in;">ISO-3166: Allow me to recall that WT5 has already spent more time than necessary to achieve 'status quo' with regard to the 2012 AGB.<br><br>Regarding long and short form ISO 3166 names, I have seen nothing recently in WT5 or on the List that would treat these differently from the 3-character codes. It would not be appropriate to 'defer broader questions…' about these. After all, that is what WT5 is here for.<br><br></p></li><li><p style="margin-bottom: 0in;">WT5 has yet to begin addressing the outstanding issues, including:<br><br>- terms and conditions for the delegation of the generality of geographical names; including a wide range of sub-national and regional terms that are not addressed by ISO 3166.<br><br>- protection of individual users' interests in the transparency and predictability of geographical names relating to their locations, communities and economies.<br><br>- the overlap – in the past - between a few geographical names and some brands;<br><br>- the treatment of IDN geographical names, including three character expressions.<br><br>N.B. The CCWG-UNCT Final Paper, June 2017, has nothing in it that is useful in these respects.<br><br></p></li><li><p style="margin-bottom: 0in;">Time Line: I would question the wisdom of deferring until May 2012 discussion of 'terms not included in the 2012 AGB'. Since WT5 has already taken several months to reach a qualified consensus on ISO 3166, I wonder what can be achieved in the next few weeks regarding all the remaining issues, for which discussion has yet to begin.<br><br></p></li></ol><p style="margin-bottom: 0in;">I would request that the agenda of the next conference calls be adapted to address in priority the terms not included in the AGB.</p><p style="margin-bottom: 0in;"><br></p><p style="margin-bottom: 0in;">Regards to you all,</p><p style="margin-bottom: 0in;"><br></p><p style="margin-bottom: 0in;">Christopher Wilkinson<br><br><br></p><br><div><div><br> Begin forwarded message:<br> <br></div><div><strong>From:</strong> BRG <<a href="mailto:martin@brandregistrygroup.org">martin@brandregistrygroup.org</a>><br> <strong>Date:</strong> 29 March 2018 at 17:37:08 BST<br> <strong>To:</strong> <a href="mailto:ntfy-gnso-newgtld-wg-wt5@icann.org">ntfy-gnso-newgtld-wg-wt5@icann.org</a><br> <strong>Subject:</strong> <strong>WT5 Update and Next Meeting</strong><br> <br></div><div> <br></div><div><div class=""><div class=""><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Dear WT5 colleagues,</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">Post- ICANN61 WT5 update</strong></div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">WT5 held a public session at ICANN61, providing a brief background and summary of progress, presenting the timeline the group is working towards to deliver an Initial Report in July (see further information below for timeline). Slides, transcript and video stream can be accessed via the ICANN61 Meeting Schedule page - <a class="" style="color: purple;" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_meetings_647704&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=9hZtlLcQOELtRr-rWR8_KmkrK6psv6S3UZ2tgOQzfBw&s=L31rLnhbLZ_rIlEidFFNn-3lW-x4VT_SPJ1hUOSAc84&e=" color="color" purple="purple">https://61.schedule.icann.org/meetings/647704[61.schedule.icann.org]</a> (transcript is also attached).</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The main part of the session focused on future treatment of geographic terms contained within the 2012 Applicant Guidebook (AGB). By way of summary, the general direction of discussions and comments were:</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">2-character country codes (ISO 3166)</strong></div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Support for maintaining the status quo, reserving all 2 letter-letter ASCII combinations for existing and future country codes.</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><div class="" style="font-family: Helvetica; font-size: 12px;"><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">3-character country codes (ISO 3166)</strong></div></div><div class="" style="font-family: Helvetica; font-size: 12px;"><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Support for maintaining the status quo, i.e. not available, and may be appropriate to defer broader questions about which entity/entities can apply for these strings and how they may be treated (for instance, as a gTLD, a ccTLD or something else).</div></div><div class="" style="font-family: Helvetica; font-size: 12px;"><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class="" style="font-family: Helvetica; font-size: 12px;"><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">Long and short form of country and territory names (ISO 3166)</strong></div></div><div class="" style="font-family: Helvetica; font-size: 12px;"><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Support for maintaining the status quo, i.e. not available, and may be appropriate to defer broader questions about which entity/entities can <span class="">apply for</span> these strings <span class="">and how they may be treated (for instance, as a gTLD, a ccTLD or something else).</span></div></div></div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The spreadsheet has been updated to reflect the comments and discussion points and is available here - <a class="" style="color: purple;" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spreadsheets_d_1FuPEq0y-2DcdSUQ1nvhWKhVnG8PLaC2RYXsCpQu91FDqo_edit-23gid-3D358523414&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=9hZtlLcQOELtRr-rWR8_KmkrK6psv6S3UZ2tgOQzfBw&s=ex9SC1DN3VrBGttw9uOUWJnP9-xPcUf5sxc8LfP_nLE&e=" color="color" purple="purple">https://docs.google.com/spreadsheets/d/1FuPEq0y-cdSUQ1nvhWKhVnG8PLaC2RYXsCpQu91FDqo/edit#gid=358523414[docs.google.com]</a>.</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Some practical issues were raised in respect of using the working document. This is currently a spreadsheet within Googledocs, with some members unable to access or edit the document. It can also be difficult to track changes. We would be happy to hear suggestions to make this working document easier to use (for instance, transfer the content to a word document within Googledocs, to allow for easier editing and tracking), please provide your preferences and we will consider a more efficient method to use a shared document. </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">WT5 Timeline</strong></div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">A copy of the timeline leading to the publication of the Initial Report is below. This will lag the PDP WG Initial Report, as previously discussed with WT5. </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Some concerns were raised during the ICANN61 session regarding the challenges of working to the timeline. The co-leaders reminded the group that WT5 is focused on a single issue, whereas WT1-4 have had multiple topics to cover. In addition, there has already been multiple efforts within the ICANN community to explore the issue of geographic terms, including the Cross Community Working Group that concluded in 2017, from which we can draw from to support the deliberations within WT5.</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The WT5 co-leaders accept that the timeline may be challenging but it is also realistic based on the reasons that were re-stated during the ICANN61 session.</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><img id="ox-f59385501f-_x0000_i1025" style="width: 640px; height: 329px;" src="cid:image001.png@01D3C780.6CFDF3C0" alt="cid:9e1a8610-a310-4ed9-b4a8-e15bffb0676d@eurprd02.prod.outlook.com" width="640" height="329" border="0"></div></div><div class=""><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">Next Meeting - 4th April, 14:00 UTC</strong></div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Our next meeting will focus on working through all the remaining 2012 AGB terms to consider their future treatment. As a reminder, WT5 needs to consider the gap between policy and what was actually implemented in the AGB, so even if WT5 concludes that the AGB treatment of the geographic terms should be retained, our recommendations need to state this to ensure that there is consistency between future policy and implementation.</div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">We can then focus our attention on other terms not included in the AGB.</div></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><br class=""></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Please note the changes to the remote access which were circulated earlier. Adobe Connect is not currently available and Webex will be used instead. </div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">Initial Report</strong></div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The content of the Initial Report is being developed as we progress our work, summarising our discussions and highlighting a sense of where the group is heading towards potential recommendations or where there are different options we would like the community to consider and provide input. </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"> </div></div><div class=""><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">We look forward to you joining our next call on 4th April and continuing our work. </div></div></div></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><br class=""></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Kind regards,</div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><br class=""></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><strong class="">WT5 Co-Leads</strong></div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Annebeth Lange</div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Olga Cavalli</div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Javier Rua</div><div class="" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Martin Sutton</div><div class=""><br class=""></div><br class=""><div class=""><div class="" style="color: #000000; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;"><div class="" style="color: #000000; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;"><div class="" style="word-wrap: break-word;"><div style="color: #000000; font-family: Helvetica; font-size: 12px; font-style: normal; font-weight: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><br class=""></div></div></div></div></div><br class=""></div></div><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>