<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:"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;}
span.EmailStyle17
{mso-style-type:personal-compose;
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-family:"Calibri",sans-serif;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Work Track members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Please find below the action items and discussion notes from the call on 3 August. <i>These high-level notes are designed to help Work Track members navigate through the content of the call and are not a
substitute for the chat transcript or the recording.</i> The meeting recording and chat transcript will soon be available at: https://community.icann.org/x/uwAhB<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
The slides from the call are attached for reference.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Emily<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">_______________________________________________________________________<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Notes – New gTLD Subsequent Procedures PDP WG WT4 – 3 August 2017
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2. SOI updates - No updates<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">3. Universal Acceptance (slide 10)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Assumed policy scope -- encourage adoption by removing barriers to usage, not in a marketing sense<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Review of Principle B<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- WT4 and CC2 comments usually satisfied with UASG efforts, some suggestions to raise awareness of their effort<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Different from 2007, IDN TLDs (ccTLDs and gTLDs) are already in the root<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Possible language "Some new generic top-level domains should be international domain names (IDNs), although applicants should be made aware of univeral acceptance challenges in ASCII and IDN TLDs (<a href="https://uasg.tech/">https://uasg.tech</a>).<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">- ACTION ITEM: Change "should" to "could" in this text.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Question - is everyone on the call happy with this language? (several green checks in support, no expressions of opposition)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Are there additional items we should add to the text? Other things we should be doing to foster UA?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Question: how much participation in this WT do we have from people with experience with IDN TLDs?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Rubens has worked on the launch of ASCII new gTLDs and related acceptance issues, as well as IDN SLDs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Sarmad Hussain from ICANN org (on this call) has expertise in this topic. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Cheryl has participated in policy development related to IDN ccTLD Fast Track and other IDN-related initiatives.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">From the chat: <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Cheryl Langdon-Orr (CLO): </span></b><span style="font-size:11.0pt">we also bring in experts and key staff on the topics Alan <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Sometimes there is concern that we are talking about things without talking to people who actually experience them, although this may not apply to this group. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- We already covered IDNs and Universal Acceptance on the last two calls<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Suggestion on language of draft text on IDNs on slide 8 -- where it currently says "by force of agreement" -- change text to "by force of written agreement." (no opposition expressed)<br>
- <b>ACTION ITEM: Change text on slide 8 from "by force of agreement" to "by force of written agreement." <o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">From the chat:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Anne Aikman-Scalese (IPC): </span></b><span style="font-size:11.0pt">IN the proposed language for IDN variants of already existing or applied for TLDs, I believe we should add "written" to the language about "by force of agreement". In other words, "by force of written agreement" would mean the commitment is in the Registry Agreement with ICANN.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">4. Road ahead for WT4 <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Timing of technical capability being required<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Technical evaluation to be performed in aggregation<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Financial evaluations to be performed in aggregation<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Name collisions<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">--- Subject to possible new feedback from technical community outreach<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- On which of these topics do members need more information? Which topics are members ready to discuss?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Outstanding questions pending answers from ICANN org.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">From the chat: <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Jeff Neuman: </span></b><span style="font-size:11.0pt">If there is an RSP Program, we should discuss the implementation of that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Jeff Neuman: </span></b><span style="font-size:11.0pt">Evaluation criteria<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Question - from the slides on name collision - "depends on ICANN org response. . ." - which response are we addressing?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Request to ICANN org on name collisions that were reported.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Comment on name collisions - it would be helpful to have better understanding of the proposed language for the name collision framework. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- The proposed framework is very similar to the framework in 2012 with some clarifications. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Based on suggestion from the office of the CTO is to reach out to technical groups to see if they have additional input.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Language on slides from ICANN59 session on the exception to the controlled interruption period -- this appears to be a difference -- it would be helpful to understand the implications of this language. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- One of the known collisions is a case where there was a request to stop a controlled interruption. This changed text is intended to address the problem that came up in this case. <br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">From the chat:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Anne Aikman-Scalese (IPC): </span></b><span style="font-size:11.0pt">COMMENT: It does seem that exceptions to controlled interruption to be granted by ICANN.org in its discretion need some policy guidelines rather than being open-ended.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Anne Aikman-Scalese (IPC): </span></b><span style="font-size:11.0pt">Futher to Alan's previous comment, I doubt I personally have the technical knowledge necessary to provide the policy guidelines for ICANN.org granting exceptions to controlled interruption. Would need help from technical community so that IS an answer to your question as to whether we need more information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Anne Aikman-Scalese (IPC): </span></b><span style="font-size:11.0pt">COMMENT: Futher to Alan's previous comment, I doubt I personally have the technical knowledge necessary to provide the policy guidelines for ICANN.org granting exceptions to controlled interruption. Would need help from technical community so that IS an answer to your question as to whether we need more information.<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">New or further discussion needed <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Name collisions in legacy TLDs<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Name collisions 2-year readiness for both 2012 round gTLDs and subsequent procedures<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- depends on ICANN org response on the 2012 round collisions<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">- Root zone scaling<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Outreach to SSAC, RSSAC, and OCTO upcoming<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- ICANN org responded to questions on improvements to reduce the likelihood of SLA failures --- WT members are encouraged to review this feedback, which may feed into conversations on a number of WT topics. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:11.0pt">Emily Barabas
</span></b><span style="font-size:11.0pt">| Senior Policy Specialist<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">ICANN</span></b><span style="font-size:11.0pt"> | Internet Corporation for Assigned Names and Numbers<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>