<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="Title" content="">
<meta name="Keywords" content="">
<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:12.0pt;
font-family:"Times New Roman",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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
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.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dear Sub Team Members,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">On the call today, WT members requested an editable version of text on the slides, so that they can more easily review the content, offer suggestions, and propose edits. This
text has now been added to the very beginning of the WT4 working document (under the header
<b>FOR WT MEMBER REVIEW -- ITEMS DISCUSSED ON 19 JUNE CALL)</b>, available at <a href="https://docs.google.com/document/d/1Axd1hmt6-qSaCGxC9UbTqBM4gP7aVxySOH3fMZ1W5hE/edit#heading=h.q3yqx325o7">
https://docs.google.com/document/d/1Axd1hmt6-qSaCGxC9UbTqBM4gP7aVxySOH3fMZ1W5hE/edit#heading=h.q3yqx325o7</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you are having trouble with this document or prefer to work with a Word version of the text, please get in touch.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Emily<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black"><gnso-newgtld-wg-wt4-bounces@icann.org> on behalf of Julie Hedlund <julie.hedlund@icann.org><br>
<b>Date: </b>Tuesday 20 June 2017 at 16:24<br>
<b>To: </b>"gnso-newgtld-wg-wt4@icann.org" <gnso-newgtld-wg-wt4@icann.org><br>
<b>Subject: </b>[Gnso-newgtld-wg-wt4] Actions/Discussion Notes: Work Track 4 Sub Team Meeting 20 June<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Dear Sub Team Members,</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Please see below the action items and discussion notes captured by staff from the meeting on 20 June.
<i>These high-level notes are designed to help Work Track Sub Team members navigate through the content of the call and are not meant to be a substitute for the recording.</i> Please also see the recording on the meetings page at:
<a href="https://community.icann.org/display/NGSPP/Work+Track+4+Meetings">https://community.icann.org/display/NGSPP/Work+Track+4+Meetings</a>.
</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Note also that the referenced slides for today’s meeting are attached and excerpts from the chat room are included below.</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Julie</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Julie Hedlund, Policy Director</span><o:p></o:p></p>
<div style="border:none;border-bottom:solid windowtext 1.5pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Action Items/Discussion Notes 20 June</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Action Item: Create an editable text.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">1. Full Work Group Update</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Next meeting is in ICANN59. See:
<a href="https://schedule.icann.org/event/B49Q/gnso-new-gtld-subsequent-procedures-pdp-working-group-face-to-face-meeting">
https://schedule.icann.org/event/B49Q/gnso-new-gtld-subsequent-procedures-pdp-working-group-face-to-face-meeting</a>
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Geographic Name session</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Putting the different proposals into documents for review.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Working with CBI to arrange GeoNames sessions at ICANN59</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">2. Tentative consensus discussions:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Demonstrating technical capability only after evaluation</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Technical Evaluation to be performed as aggregated / consolidated as feasible</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Financial Evaluation to be performed in aggregation of a registry family</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Universal Acceptance</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- IDNs Security and stability review</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- IDNs 1-char TLDs</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- IDN Variant TLDs</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Name collision framework for subsequent procedures</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">5. Topic still requiring more discussion: (time permitting)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Name collisions in legacy and current gTLDs</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- 2-year readiness in name collision framework</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Slide 6: Demonstrating technical capacity only after evaluation (revised after CC2).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Slide 7: Technical Evaluation to be performed as aggregated/consolidated as feasible:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Slide 8: Financial Evaluating to be performed in aggregation of a registry family.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Slide 9: Universal Acceptance</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Great to know what questions people would want prior to any new language.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Not saying anything very different.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Slide 10: IDNs: Security and Stability Review
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Need to adjust language related to RFCs (e.g., required versus informational)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- LGRs should be singular</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Slide 11: IDNs: I-Char IDN TLDs (revised after WT4, SSAC, ICANN Org, and CC2 Comments)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Not sure the role of this section is to comment on country or territory names here.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">-- Ideogragh or ideogram -- not sure these are the right terms.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">From the chat:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): @Avir and Jeff re Strawperson on geo names - it is going to be tough when you ask the country whether the name is protected by national legal right
or not.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): *@Avri - not Avir!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Jeff Neuman: Thanks....been having some power issues at my home</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Jeff Neuman: But I am back</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Jeff Neuman: Strawbunnies hopped away</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">avri doria: Anne, just one of the challenging subjects, I expect</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Cheryl Langdon-Orr (CLO): Yes this is an aspirational Agenda... To Be Continued if needs be..</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): @Avri - yes - but Strawperson very interesting for discussion!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): QUESTION: Does previously approved "infrastructure" mean a previously approved back-end provider? QUESTION</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): I just dont know what "infrastructure' means</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Cheryl Langdon-Orr (CLO): I agree Harmonized language will be useful///</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Cheryl Langdon-Orr (CLO): Yes All tracks</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): Agree about harmonized language. How does a new provider get approved</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Cheryl Langdon-Orr (CLO): and a glossary in our reports</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): QUESTION: Are we suggesting that timing of consideration/evaluation of an application would depend on who the back-end provider is? QUESTION</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): COMMENT: That seems prejudicial to new entrants in the arena of back-end registry operator services if so. COMMENT</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif">Anne Aikman-Scalese (IPC): Thanks Ruben for clarifying it does not affect priority of evaluation. But even if it speeds things up in terms of evaluation, it might be prejudicial
to new entrants because applicants won't choose new entrants.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>