<html 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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText><span style='font-size:12.0pt'>Dear Work Track 5 members,</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Please see below the action items and notes from the meeting today (30 May). <i>These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat, which will be posted at: </i><a href="https://community.icann.org/display/NGSPP/2018-02-07+New+gTLD+Subsequent+Procedures+PDP+Work+Track+5">https://community.icann.org/display/NGSPP/2018-02-07+New+gTLD+Subsequent+Procedures+PDP+Work+Track+5</a>. </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>See also the slides posted on the wiki above.</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Kind regards,</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Julie</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Julie Hedlund, Policy Director</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>----------------------------------------------------------------------------------------------------------------------------------</span><o:p></o:p></p><p class=MsoPlainText><b><span style='font-size:12.0pt'>Notes/Action Items:</span></b><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><b><span style='font-size:12.0pt'>Action Items:</span></b><span style='font-size:12.0pt'> WT5 members should review and comment on the collaborative working document (google document) when it is sent to the list.</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:12.0pt'>Notes:</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>1. Welcome/Agenda Review/SOI Updates: No SOI updates</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>2. Process Map Improvements</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Slides 4, 5, & 6:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- The Work Track has reviewed the process from the 2012 round and validated the chart documenting this process.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- We considered five elements of the process: 1) Submitting Application; 2) Geographic Names Review; 3) Objections Mechanisms; 4) String Contention; 5) Contractual Requirements</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- No objections to the process map for the 2012 AGB treatment of geographic names</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Slide 7: Suggestions for Future Process Improvements</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Do you have ideas for process improvements in one or more of these areas?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- The discussion will focus on one area at a time:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>1. Submitting Application</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>2. Geographic Names Review</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>3. Objections Mechanisms</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>4. String Contention</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>5. Contractual Requirements </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Slide 5, Stage 5 – Contractual Requirements</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- post-delegation controls – are these adequate to protect the needs of applicants. What if an applicant applies for a name that is the same as a geographic term, but says it won’t use it in a geographic sense, but then changes after delegation to a geographic use.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Gaps or improvements in the post delegation phase</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Discussion:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- There are very strong opinions about the non-geo use clause in the 2012 AGB. Hardly any support for maintaining that clause. Risk of creating a loophole.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Disagree. This is very much a live issue.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Determine in this WT what is or isn’t enforceable re: PICs and statements in applications.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>From the chat: Katrin Ohlmer: PICs will not be enforceable by Governments as they do not have the bandwidth to monitor them regularly</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Re: conditions attached to the use of a top-level name and any intended use: important that we don’t only hear from those people who are being vocal, but consider all opinions on intended use. From the email discussion we see that the notion of intended use is considered problematic from participants coming from all SOs and ACs, perhaps 20 people.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- If the public authority is not consulted ahead of time it will have to intervene during delegation.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- What we are seeing here and part of the difficulties -- 5 different vectors where protection can be put in place. People have different opinions on how the range of each vector can be implemented. Good to look at each vector and lay out the full range of mechanism available -- both hypothetical and actual. With few exceptions I don't think everyone is imagining that the protection is all in the application phase. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Could use the above suggestions and replay different types of situations and where there could be improvements.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- This could be a value-neutral process of laying out all the options as a useful step forward to keep things constructive. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Recent work re: two-character labels at the second level: a new mechanism for post-delegation to enable monitoring and enforcement of any kind of confusion, which also is how trademark law works. There are many mechanisms beyond ICANN in domestic trademark law to prevent confusion.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Confusion is not key when considering Top Level Domains which are unique - the question is about the scarceness, the uniqueness of the resource, which requires that all interested parties, included the relevant public authorities are at a table at the very start of the process.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- There could be improvements in a monitoring and enforcement mechanism.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Re: string contention -- the area of digit-letter two-character strings -- there are already mechanisms to reduce confusion. Is there anything that we should consider to improve?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Make sure there are fair processes that are reasonably well publicized.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- We should be responding when there are complaints and that it quite reasonable.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- If we have reserved names that are geographic names at the top level that should be dealt with in this Work Track.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Re: Objection mechanisms -- quite a lot of discussion on letters of non-objection, but this is focused on the GAC early warning and advice. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>3. Next Steps on Working Document (slide 9)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Over the last few weeks there have been a lot of comments on the list.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Working with staff to build out a collaborative working document (in Google Docs) -- or an essential data capture tool -- in the format of the Initial Report.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Populated it with background, previous treatment, and opinions that have been expressed.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Will send the document after this call and allow WT member to add comments to the document as to whether it represents discussions in the email list and the meetings. To see if there are any gaps.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>4. ICANN62 Preparation (slide 10)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Two Cross-Community Sessions will be held at ICANN62 on geo names. Expected session times:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Monday 25 June from 15:15-16:45Thursday 28 June from 15:15-16:45</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Work Track leaders are working on a proposed structure and focus for these sessions.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Other SOs and ACs are discussing these topics and those sessions also will be open.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>5. AOB: Timing of Meetings</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Sessions have been weekly for 60 minutes.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>-- Work Track leaders will review this schedule, but we'll continue 60-minute weekly meeting up to ICANN62. </span><o:p></o:p></p></div></body></html>