<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)">
<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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.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;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear Work Track 5 members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Please see below the action items and discussion<span class="apple-converted-space"> </span>notes<span class="apple-converted-space"> </span>captured by staff from the meeting on 25 July 2018.
These high-level<span class="apple-converted-space"> </span>notes are designed to help WT members navigate through the content of the call and are not meant to be a substitute for the recording or transcript, which are posted on the wiki at:<span class="apple-converted-space"> <a href="https://community.icann.org/x/v4pHBQ">https://community.icann.org/x/v4pHBQ</a>
. Slides from the call are attached.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="apple-converted-space"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span class="apple-converted-space"><span style="font-size:12.0pt;color:black">For those who missed today’s call, the Work Track leaders would like to highlight an upcoming change in the call rotation. The WT currently
<b>meets alternate Wednesdays for 90 mins at three rotating times</b>: 5:00 UTC, 14:00 UTC, and 20:00 UTC. Due to a standing conflict for staff that will overlap with the 14:00 UTC call, the WT will try meeting at 13:00 UTC instead of 14:00 UTC. Therefore,
<b>the new rotation will be: 5:00 UTC, 13:00 UTC, and 20:00 UTC</b>. Noting that there will always be challenges associated with scheduling across time zones, the WT co-leaders will continue to monitor attendance, accept feedback, and revisit the schedule going
forward.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="apple-converted-space"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span class="apple-converted-space"><span style="font-size:12.0pt;color:black">Kind regards,<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="apple-converted-space"><span style="font-size:12.0pt;color:black">Emily</span></span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="font-size:12.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">------------------------------------------------------------------------------------------------------------------------------------------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Notes:<o:p></o:p></p>
<p><span style="color:black">1. Welcome/Agenda Review/SOI Updates </span><o:p></o:p></p>
<p><span style="color:black">- no SOI updates</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="color:black">2. Problems to be Solved from the 2012 round </span><o:p></o:p></p>
<p><span style="color:black">- Emphasis: focus on real problems observed or experienced, so that we can identify solutions that target th</span>ose<span style="color:black"> problems.</span><o:p></o:p></p>
<p><span style="color:black">- Some examples</span> of possible problems to discuss<span style="color:black">: lack of timely response from governments when seeking support/non-objection, uncertainty about which govt/public authority to contact, unauthorized change of use after delegation. </span><o:p></o:p></p>
<p><span style="color:black">- Suggestion related to lack of timely response from governments when seeking support/non-objection</span>:<span style="color:black"> ICANN can ask all governments whether they are concerned about an application. If they are not concerned, the application can move forward. If they are concerned, ICANN can work with the government to find a timeframe within which the government can provide additional detail about the concern. The government can also indicate whether it prefers </span>to
provide <span style="color:black">implicit or explic</span>i<span style="color:black">t approval of the application.</span><o:p></o:p></p>
<p><span style="color:black">- </span>Problem suggested<span style="color:black">: governments may not have experience dealing with ICANN, which may cause longer timeframes to reply to requests for support/non-objection.</span><o:p></o:p></p>
<p><span style="color:black">- Question</span> raised<span style="color:black">: Other than .spa, are there cases the group can identify where there was an application that was coincindentally a geographic term but was applied for in non-geographic use and resulted in objection?</span><o:p></o:p></p>
<p><span style="color:black">From the chat: </span><o:p></o:p></p>
<p><b><span style="color:black">Katrin Ohlmer: </span></b><span style="color:black">Problem: CIty opposed application. Examples: .spa Possible solution(s): Require a pre-check to avoid delays and increase predictability.</span><o:p></o:p></p>
<p><span style="color:black">- Suggestion</span> for a solution<span style="color:black">: GAC should work more closely with governments to make sure applicants reach the right focal point </span>within<span style="color:black"> a government in relation to obtaining support/non-objection.</span><o:p></o:p></p>
<p><span style="color:black">- </span>Comment<span style="color:black">: it would be helpful of staff to do an analysis of how frequently these issues emerged.</span><o:p></o:p></p>
<p><span style="color:black">- Comment: The situation in many countries and places will be different in subse</span>q<span style="color:black">uent procedures. Problems experienced in 2012 may not reflect problems that will be experienced in the future. </span><o:p></o:p></p>
<p><span style="color:black">- Problem</span> suggested<span style="color:black">: Changes in the public authorities concer</span>n<span style="color:black">ed. Solution proposed: agreements should be time limited. </span><o:p></o:p></p>
<p class="MsoNormal">From the chat:<o:p></o:p></p>
<p><b><span style="color:black">Kavouss Arasteh: </span></b><span style="color:black">Ouzur departure point should always be the 2012 ERound, what problem we have identified for that round</span><o:p></o:p></p>
<p><b><span style="color:black">Kavouss Arasteh: </span></b><span style="color:black">For capital city, the example given by Alexander such as .Paris ,who we have to ciontact and in what sequence? France or Texas State ?</span><o:p></o:p></p>
<p><span style="color:black">- Challenge for this group identified</span> in this exercise:<span style="color:black"> members of the WT may not have visibility into the experiences of parties involved in the 2012 round. The WT may want to reach out to parties involved in the round for input about problems experienced.</span><o:p></o:p></p>
<p><span style="color:black">- </span>Problem suggested<span style="color:black">: Challenge of potentially needing to reach out to multiple governments or public authorities to obtain support/non-objection for a single application.</span><o:p></o:p></p>
<p><span style="color:black">- Question: to what extent did applicants have difficulty working with city governments? Some </span>city TLDs
<span style="color:black">were run by the city and others had a more tenuous relationship</span> with the city<span style="color:black">. This may be a business issue and not an ICANN issue to resolve.</span><o:p></o:p></p>
<p><span style="color:black">- Problem </span>suggested <span style="color:black">
(not specific to non-capital city): Some applicants applied for strings that were reserved or had other requirements and the applicant was not aware that the requirements existed. Possible solution: mechanism to have a warning that a term is a geographic name and has specific requirements or restriction</span>s<span style="color:black">. </span><o:p></o:p></p>
<p>- Staff response: In the instances where the string could NOT be applied for by anyone, and there was a defined list, there were programmatic measures in place. Adding in a notification for geographic names that COULD be applied for could be something new
that this WT could recommend.<o:p></o:p></p>
<p><span style="color:black">- For non-capital cities - it may not be straightforward to provide this type of information for non-capital city names upfront, but this could be explored further.</span><o:p></o:p></p>
<p>- Suggestion: a<span style="color:black">dditional fact finding </span>about issues experienced
<span style="color:black">might be helpful through a questionnaire or by asking questions in the Initial Report for public comment. </span><o:p></o:p></p>
<p><span style="color:black">- </span>Staff suggestion for structuring the discussion:
<span style="color:black">One possible way to think of </span>issues is in a series of categories:<span style="color:black"> 1. </span>The<span style="color:black"> string is used </span>as
<span style="color:black">a city name a. problems for the applicant and b. problems for the government. 2. </span>The<span style="color:black"> string is not intended to be used as a city name a. problem</span>s<span style="color:black"> for the applicant and b. problems for the government. </span><o:p></o:p></p>
<p>From the chat:<o:p></o:p></p>
<p><span style="color:black">- <b>Katrin Ohlmer: </b>@Steve: It would be helpful if ICANN org could provide more details about the geographic names panel work - e.g. how did they identify a geo name, what happened if they identified a string as geo name, did they inform someone..</span><o:p></o:p></p>
<p><span style="color:black">- Staff response to Katrin: In instances that the applicant did not identify a string as a geographic name but the geo panel found that it was a geo term, the applicant was given additional time to obtain support/non-objection from the relevant governments/public authorities.</span><o:p></o:p></p>
<p><span style="color:black">- Slide 9: view of different perspectives expressed on possible paths forward for non-capital city names. Given the diversity of perspectives, is a possible middle ground to keep the 2012 protections? </span><o:p></o:p></p>
<p><span style="color:black">- Suggestion</span> for path forward<span style="color:black">: focus on the process. From this perspective, there were some cases where a term was obviously geographic terms. There should be list. In other cases, the applicant may not know that a term has geographic meaning.</span><o:p></o:p></p>
<p><span style="color:black">- Comment</span> about level of protections for subsequent procedures<span style="color:black">: There are attractive elements </span>to<span style="color:black"> reducing restrictions, but there is concern about stability of the outcome. The registry has to be protected against changes in governments and ex-post facto concerns raised. If we want to have predictability throughout the life of the registry there has to be a formal agreement between the registry and the government.</span><o:p></o:p></p>
<p><span style="color:black">- </span>Question: <span style="color:black">Could the use of PICs provide some of that assurance?</span><o:p></o:p></p>
<p><span style="color:black">- Comment: At some point we need to talk about process</span>. I<span style="color:black">t is premature to talk about process until we talk about what that process applies to. Disagree that everything included in the 2012 AGB should be restricted in the future. Sub-national place names are an example, .tata was a consequence. </span><o:p></o:p></p>
<p><span style="color:black">- Comment: For strings that are applied for that correspond to geographic term but are used in a generic sense, we do not yet have agreement about whether we need to treat these as geographic terms.</span><o:p></o:p></p>
<p><span style="color:black">- Comment: it is important to identify which governments/public authorities we are referring to in slide 9. In column 3/row 2</span> of the table<span style="color:black">, will need to be more specific about the proposals put forward regarding city size/population/significance.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="color:black">2b. Problems identified for non-AGB terms. </span><o:p></o:p></p>
<p><span style="color:black">- All are encouraged to share concrete problems and possible solutions on the list.</span><o:p></o:p></p>
<p><span style="color:black">- This agenda item will be addressed further in the future.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="color:black">3. Focus on Implementation Guidance</span><o:p></o:p></p>
<p><span style="color:black">- </span>R<span style="color:black">eview of suggestions received so far regarding implementation guidance. </span><o:p></o:p></p>
<p><span style="color:black">- By reviewing implementation ideas, it may help the group think about issues to address at a policy level.</span><o:p></o:p></p>
<p><span style="color:black">- Examples: advisory panel, leverage GAC members to get input on geographic sensitivities, repository of geographic names, rules for strings that are similar to geographic term, online tool for applicants, applicant research requirements, government involved at contract renewal, mediation related to support/non-objection letter.</span><o:p></o:p></p>
<p><span style="color:black"> - Comment: </span>Concern expressed that<span style="color:black"> anything that has a geographic meaning will be caught in the geographic "net." We can't take the text part of an atlas and say this is a restricted zone. We can't assume that everything that someone considers a geographic term is in fact a geographic term for treatment in the AGB.</span><o:p></o:p></p>
<p><span style="color:black">- Suggestion: We need to draw a boundary outside of which there are no additional rights, powers, or privileges for governments. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="color:black">4. Looking Ahead: Work Plan and Initial Report </span><o:p></o:p></p>
<p><span style="color:black">- Leadership team is working on a work plan to reach the Initial Report</span>. This will be shared soon with the WT.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="color:black">5. AOB</span><o:p></o:p></p>
<p><span style="color:black">- The co-leaders are proposing moving the 14:00 time slot in the rotation to the 13:00 time slot to avoid scheduling conflicts.</span><o:p></o:p></p>
</div>
</body>
</html>