<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 name=Title content=""><meta name=Keywords content=""><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:12.0pt;
font-family:"Times New Roman";}
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:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal-reply;
font-family:Calibri;
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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'>Dear Sub Team Members,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'>Please see below the action items and discussion notes captured by staff from the meeting on 20 April. <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>. <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'>Note also that the referenced slides for today’s meeting are attached and excerpts from the chat room are included.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'>Best regards,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'>Julie<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Julie Hedlund, Policy Director<o:p></o:p></span></p><div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Action Items/Discussion Notes 20 April</span></b><span style='font-size:10.5pt;font-family:Calibri'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:Calibri'>1. Full Work Group Update<o:p></o:p></span></i></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Spent the last meeting working on the CCT-RT issues.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Put together a response to the CCT-RT open comment that is up for review. See: https://docs.google.com/document/d/1LC-1-Z2auN2XTSJXyW34eWnGgNuuDInIOeJ1TcZ7z58/edit.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Next meeting talk through sending off the comment.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Getting ready for the Geo Names at the top level 25 April at two different times. Everyone is invited and please sign up in advance.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Drafting Teams on the open issues working. Staff has provided initial documents to work from.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- CC2 comment: Got a formal request for an extension. Looks like we can offer an extension of 3 weeks and still meet the document deadline for ICANN59. Out for discussion in case there are objections -- none yet. If comments are done people should send them in an not wait.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:Calibri'>2. Name collisions in legacy gTLDs (.com, .net, .org, etc.)<o:p></o:p></span></i></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Slide 6: Name Collisions: New Name, Old Phenomena (1/2)<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- End user expecting the DNS to work in one way and it works in a different names.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- No policy allowing those problems to be addressed by Contracted Parties.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- ICANN does not hold itself as the DNS police. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Adopting a policy could be somewhat unprecedented.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>For discussion: Contracted Parties should be forced or could be allowed to take collision domains away from users (policy change)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Possible threats does not warrent policy changes; no new policy required.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Discussion:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- How many names are we talking about? Not clear what is the set of collision domains. SAC090 report and JAS report.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- One of the problems in defining a policy is such domains are generated by software bugs so we can't anticipate. Not knowing the scope is one of the things that makes it hard to have a policy on this.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Question: How does this area relate to the APB reports issued with the new round? Is there a relationship? Answer: No connect.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- When we are talking about the SSAC and JAS report we are talking about collisions at the top level, but here we are talking about lower levels. For the last round they did devise certain mitigations.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Have there been any studies on second level collisions? Do we have any follow on data on the mitigation strategies used in the previous round. Any suggestions as to their being a yellow track in this that perhaps we aren't changing the policy but nor are we forcing any behavior, but coming up with a recommendation for greater study of mitigation -- how inform, how educate, etc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Discussion in Copenhagen with Board on name space and coordination with the IETF.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Shouldn't we be getting a presentation from the SSAC on name space/name collisions? Get advice and input from the SSAC.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Need to make some recommendations out of this WG.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Mark this as a topic to bring in external expertise.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Steve Chan: SAC090: https://www.icann.org/en/system/files/files/sac-090-en.pdf<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Cheryl Langdon-Orr (CLO): with us yes, but management must in my Biased view, be looked at and resolved <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Cheryl Langdon-Orr (CLO): thus the importance of this and similar conversations <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Julie Hedlund: Also, SAC062: SAC Advisory Concerning the Mitigation of Name Collision Risk (07 November 2013) at https://www.icann.org/en/groups/ssac/documents/sac-062-en.pdf<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Julie Hedlund: SAC090 is SSAC Advisory on the Stability of the Domain Namespace (22 December 2016) <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Alan Greenberg: Middle ground is almost certainly where we will end up.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Slide 7: Name collisions: New Name, Old Phenomena (2/2)<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>For Discussion: Expired Domain Deletion and Expired Registration Recovery policies should be revised and changed?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Possible threats does not warrant policy changes?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Discussion:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Are these policies enough? <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Seems like there is a lack of data.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Note sure we are missing data and need to do studies. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Still a lot of issues that are hard to digest and not every word in them is gospel. The studies that have been done are old. There doesn't seem to be new data. Find out if there is new data.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Alan Greenberg: Middle ground is almost certainly where we will end up.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Cheryl Langdon-Orr (CLO): personal view is that I suspect so Alan<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>avri doria: Alan, we often stick with status quo.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>avri doria: mitigation is a good middle postion in many things<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Alan Greenberg: Agreed. Just hazarding a guess.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:Calibri'>3. Name Collisions Framework in 2012 Round (slide 9)<o:p></o:p></span></i></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Requirement to pass a controlled interruption period.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Current number of collision reports is 37 -- 0 life threatening.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- ICANN has not published the collision reports.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>For discussion: 2012-round registries should extend such support beyond the 2-year period (implementation change)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Occurrence experience does not warrant creation of policy to override what is in the agreements (keep as is)?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Is the current 2012-round process enough?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- No idea of how close occurrences came to being life threatening. Can't make an informed decision. Need to understand what the collisions were.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Need to err on the side of caution but not to such an extent that it impacts the industry. You do have instances where you can analyze risk and the cost of mitigations compared to the cost of something going wrong.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Just because something hasn't happened yet doesn't mean it won't. Need to know the consequences if it does. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p></div></body></html>