<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>Anne,<div class=""><br class=""></div><div class="">Compromise and commitment to forward movement goes both ways. What Jeff Schmidt reminded us can be summarized by two things:</div><div class="">- There is a new analysis process being suggested, but there is no rationale on which goals this new process is aiming to achieve, and why those are worthy pursuing. </div><div class="">- There is an old mechanism being yet again reintroduced, while the underlying conditions for its use only became worse since 2012. </div><div class=""><br class=""></div><div class="">Wanting to change just because is not good enough. Change needs to be meaningful to be called progress. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Rubens</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 17 Feb 2022, at 14:30, Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com" class="">AAikman@lewisroca.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Sorry Jeff. I got my “Jeffs” mixed up. I guess there is no reason Jeff Schmidt would be aware of the Sub Pro Policy outcomes. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">At any rate, I keep trying to get references to the Sub Pro Final Report incorporated somehow into the work of the NCAP because, let’s face it – when the Board has conflicting advice from two different sources, in recent years they tend to send it back to the Community for further policy work or else it comes to a standstill because they have conflicting advice. That “bottleneck” is a killer for the ICANN DNS and the MSM system. Now decentralized domains are flourishing. ICANN is starting to look like a gigantic slow-moving dinosaur. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">If different arms/elements of the Community don’t start coordinating their efforts toward RESULTS, we will rot on the vine. The Board routinely takes the position that it does not “make policy” but if the result of that is “no forward movement”, then the ICANN Mission is not being accomplished. I think the Board is looking for us to resolve issues before they take action. Sub Pro said that if NCAP process develops a new Name Collision Framework that is recommended by the SSAC and then adopted by the Board, then it should apply to the next round. That Recommendation in the Sub Pro Final Report is important because it eliminates a conflict. Some folks may want to stop this NCAP process in its tracks because they believe 90-day controlled interruption should apply. We do have to take into account what is happening at the Board level. There is also a responsibility for members of this NCAP Discussion Group to proceed in a manner that seeks compromise, not just insist on a position in favor of 90-day controlled interruption when we are all participating in good faith in the NCAP process. <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">At any rate, Casey is looking at some additional data over the past few years which may be enlightening.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Anne<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse: collapse;"><tbody class=""><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.959999084472656px;" class=""><b class=""><span style="font-size: 11pt; line-height: 15.546667098999023px; font-family: "Trebuchet MS", sans-serif; color: rgb(50, 50, 50);" class="">Anne E. Aikman-Scalese</span></b><span style="font-size: 11pt; line-height: 15.546667098999023px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><p class="MsoNormal" style="margin: 0in 0in 3pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.959999084472656px;"><span style="font-size: 11pt; line-height: 15.546667098999023px; font-family: "Trebuchet MS", sans-serif; color: rgb(50, 50, 50);" class="">Of Counsel</span><span style="font-size: 11pt; line-height: 15.546667098999023px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></p></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><p class="MsoNormal" style="margin: 0in 0in 3pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 6.400000095367432px;"><span style="font-size: 10pt; line-height: 5.3333330154418945px; font-family: "Trebuchet MS", sans-serif; color: rgb(31, 73, 125);" class=""><span id="cid:image003.png@01D823E9.6EFF3200"><image003.png></span></span><span style="font-size: 11pt; line-height: 5.866666793823242px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></p></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.959999084472656px;" class=""><span style="font-size: 10pt; line-height: 14.133332252502441px; font-family: "Trebuchet MS", sans-serif; color: rgb(31, 73, 125);" class=""><a href="mailto:AAikman@lewisroca.com" target="_new" title="Email User" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(50, 50, 50);" class="">AAikman@lewisroca.com</span></a></span><span style="font-size: 11pt; line-height: 15.546667098999023px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.25in; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.959999084472656px;" class=""><span style="font-size: 10pt; line-height: 14.133332252502441px; font-family: "Trebuchet MS", sans-serif; color: rgb(50, 50, 50);" class="">D. 520.629.4428</span><span style="font-size: 11pt; line-height: 15.546667098999023px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.959999084472656px;" class=""><span style="font-size: 10pt; line-height: 14.133332252502441px; font-family: "Trebuchet MS", sans-serif; color: rgb(31, 73, 125);" class=""><span id="cid:image006.png@01D823E7.FBA39950"><image006.png></span></span><span style="font-size: 11pt; line-height: 15.546667098999023px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""></td></tr></tbody></table></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span>Jeff Neuman <<a href="mailto:jeff@jjnsolutions.com" style="color: purple; text-decoration: underline;" class="">jeff@jjnsolutions.com</a>><span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Thursday, February 17, 2022 12:28 AM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com" style="color: purple; text-decoration: underline;" class="">AAikman@lewisroca.com</a>>;<span class="Apple-converted-space"> </span><a href="mailto:rubensk@nic.br" style="color: purple; text-decoration: underline;" class="">rubensk@nic.br</a><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span><a href="mailto:ncap-discuss@icann.org" style="color: purple; text-decoration: underline;" class="">ncap-discuss@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>RE: [NCAP-Discuss] Reflecting on the 'big picture' and making our outputs helpful to the Community<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><strong class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">[EXTERNAL]</span></strong><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""></o:p></span></div><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: center;"><hr size="3" width="100%" align="center" class=""></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Anne,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">I am not sure why you addressed this to me as I have not weighed in on this yet. I believe you meant Jeff Schmidt who sent this e-mail. I do, however, support the statements that Jeff S. has made.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Sincerely,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Jeff Neuman<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div class=""><table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse: collapse;"><tbody class=""><tr class=""><td width="193" valign="bottom" style="width: 144.3pt; border-style: solid none none; border-top-width: 3pt; border-top-color: rgb(6, 23, 95); padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: justify;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif; border: 1pt none windowtext; padding: 0in;" class=""><span id="cid:image005.png@01D823E9.6EFF3200"><image005.png></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div></td><td width="173" valign="bottom" style="width: 129.95pt; border-style: solid none none; border-top-width: 3pt; border-top-color: rgb(6, 23, 95); padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: justify;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(6, 23, 95);" class="">Jeffrey J. Neuman</span><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: justify;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif;" class="">Founder & CEO</span><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: justify;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(6, 23, 95);" class="">JJN Solutions, LLC</span><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: justify;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif;" class="">p: +1.202.549.5079</span><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: justify;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif;" class="">E:<span class="Apple-converted-space"> </span></span><span style="font-family: Calibri, sans-serif;" class=""><a href="mailto:jeff@jjnsolutions.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif; color: rgb(17, 85, 204);" class="">jeff@jjnsolutions.com</span></a><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: justify;" class=""><span style="font-size: 11pt; font-family: Arial, sans-serif;" class=""><a href="http://jjnsolutions.com/" style="color: purple; text-decoration: underline;" class="">http://jjnsolutions.com</a></span><span style="font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div></td></tr></tbody></table><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span>Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com" style="color: purple; text-decoration: underline;" class="">AAikman@lewisroca.com</a>><span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Wednesday, February 16, 2022 1:48 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span><a href="mailto:rubensk@nic.br" style="color: purple; text-decoration: underline;" class="">rubensk@nic.br</a>; Jeff Neuman <<a href="mailto:jeff@jjnsolutions.com" style="color: purple; text-decoration: underline;" class="">jeff@jjnsolutions.com</a>><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span><a href="mailto:ncap-discuss@icann.org" style="color: purple; text-decoration: underline;" class="">ncap-discuss@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>RE: [NCAP-Discuss] Reflecting on the 'big picture' and making our outputs helpful to the Community<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Jeff and Rubens,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Having participated actively in Sub Pro, I am not surprised by the approach you have both taken in your comments, though they do seem to be a bit “late-breaking” in terms of the process the DG has been following. The Workflow document has been around for a long time.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">I’ll also note that Sub Pro Recommendations in the Final Report (adopted by the GNSO Council and sent to the ICANN Board) state that<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><span class="">(1)<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">ICANN should develop a DO NOT APPLY list for names that have too great a risk of potential harm. (The potential harms were identified in NCAP Study 1).<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><span class="">(2)<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Any New Name Collision Framework coming out of the NCAP process and recommended to the Board by SSAC (which is adopted by the Board in time for the next round) should govern. Considering the projected time frame for the ODP, there should be ample time for this process to “dovetail” the development of an AGB. And the ODP notes that this issue of a possible new Name Collision Framework has to be resolved.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Reports of name collision issues to ICANN based on the 2012 round and the “lack of litigation” in this realm is not a reliable measure for answering the issues raised by NCAP Study 1 or the Board’s specific questions to the SSAC on this topic. Those Board questions have been guiding the work of the DG for months and there is also recognition that the DNS is not static.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">I don’t think NCAP DG is a forum designed to revisit the policy work already done in Sub Pro and the Recommendations that came out of that process. And I don’t think the NCAP DG can ignore the specific questions posed by the Board and the results of Study 1 by simply saying – “well, it seems to us it all went just fine in the 2012 round.” <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Anne<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse: collapse;"><tbody class=""><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.799999237060547px;" class=""><b class=""><span style="font-size: 11pt; line-height: 15.399999618530273px; font-family: "Trebuchet MS", sans-serif; color: rgb(50, 50, 50);" class="">Anne E. Aikman-Scalese</span></b><span style="font-size: 11pt; line-height: 15.399999618530273px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><p class="MsoNormal" style="margin: 0in 0in 3pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.799999237060547px;"><span style="font-size: 11pt; line-height: 15.399999618530273px; font-family: "Trebuchet MS", sans-serif; color: rgb(50, 50, 50);" class="">Of Counsel</span><span style="font-size: 11pt; line-height: 15.399999618530273px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></p></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><p class="MsoNormal" style="margin: 0in 0in 3pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 6.400000095367432px;"><span style="font-size: 10pt; line-height: 5.3333330154418945px; font-family: "Trebuchet MS", sans-serif; color: rgb(31, 73, 125);" class=""><span id="cid:image003.png@01D823E9.6EFF3200"><image003.png></span></span><span style="font-size: 11pt; line-height: 5.866666793823242px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></p></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.799999237060547px;" class=""><span style="font-size: 10pt; line-height: 14px; font-family: "Trebuchet MS", sans-serif; color: rgb(31, 73, 125);" class=""><a href="mailto:AAikman@lewisroca.com" target="_new" title="Email User" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(50, 50, 50);" class="">AAikman@lewisroca.com</span></a></span><span style="font-size: 11pt; line-height: 15.399999618530273px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.25in; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.799999237060547px;" class=""><span style="font-size: 10pt; line-height: 14px; font-family: "Trebuchet MS", sans-serif; color: rgb(50, 50, 50);" class="">D. 520.629.4428</span><span style="font-size: 11pt; line-height: 15.399999618530273px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 16.799999237060547px;" class=""><span style="font-size: 10pt; line-height: 14px; font-family: "Trebuchet MS", sans-serif; color: rgb(31, 73, 125);" class=""><span id="cid:image006.png@01D823E7.FBA39950"><image006.png></span></span><span style="font-size: 11pt; line-height: 15.399999618530273px; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div></td></tr><tr class=""><td width="336" valign="top" style="width: 3.5in; padding: 0in 5.4pt;" class=""></td></tr></tbody></table></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span>NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" style="color: purple; text-decoration: underline;" class="">ncap-discuss-bounces@icann.org</a>><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Rubens Kuhl via NCAP-Discuss<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Wednesday, February 16, 2022 11:18 AM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span><a href="mailto:ncap-discuss@icann.org" style="color: purple; text-decoration: underline;" class="">ncap-discuss@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [NCAP-Discuss] Reflecting on the 'big picture' and making our outputs helpful to the Community<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">Besides agreeing wholeheartedly with Jeff, I will just add that this rehashing of old ideas is a good part of the paralysis disease plaguing ICANN (Org + Community) at this point. <o:p class=""></o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">But name collisions has been used in the past to stall this same root zone expansion program, so this is not a new script, just a new episode of the series. <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">Rubens<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><div class=""><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 12pt; font-family: "Times New Roman", serif;"><o:p class=""> </o:p></p><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">On 16 Feb 2022, at 13:25, Jeff Schmidt via NCAP-Discuss <<a href="mailto:ncap-discuss@icann.org" style="color: purple; text-decoration: underline;" class="">ncap-discuss@icann.org</a>> wrote:<o:p class=""></o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><div class=""><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Team:<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">TL;DR:<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">We should start by recognizing the effectiveness of the 2012 procedures (as codified in the 2014 Name Collision Occurrence Management Framework)[1] and make surgical improvements for predictability as suggested by SubPro. We should not invent new procedures that introduce enormous and unnecessary new costs, risks, and uncertainty in exchange for unclear value. Our recommendations must be supported by a sober cost-benefit analysis.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Long Version:<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">I am responding to the 9 Feb meeting minutes, the “Workflow” slides, and indirectly the recent exchange of letters between the RySG and the ICANN Board. We need to take note of the recent exchange of letters as it speaks to the importance of providing high-quality, succinct, practical, and actionable advice to the Board. Emphasis on practical and actionable.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Collisions are well understood.</span></b><span class="apple-converted-space"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">We know under what circumstances they occur, and we have real, practical, global-scale operational experience and data after delegating > 1,200 TLDs over the past decade.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Study 1 provides an excellent summary of the enormous amount of thought and data that has been assembled over the past 25 years regarding collisions. We must ask ourselves the hard question: what are we really adding at this point? We can create new charts and graphs, but the phenomenon remains the same. It is well understood. There isn’t much to add. I have yet to see evidence to the contrary. We have reached the threshold of analysis paralysis and ambled over it.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><i class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">We must be aware of and equipped to encounter another “.corp” but not fall into the sensationalist trap that every new TLD is a disaster waiting to happen. The numbers and the history simply don’t support this FUD (Fear, Uncertainty, and Doubt).</span></i><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">I am very concerned that in failing to overtly recognize these realities, perpetuating calls for “more data!” and “more research!” and esoteric academic debate that is accessible and of interest to only a very few, we are at risk of providing unhelpful and/or unimplementable advice to the Board that is indeed “ambiguous, incomplete, or unclear” (reference from Botterman-to-Demetriou).<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">What was done in 2012 worked</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">. I would encourage everyone to look at the Name Collision Reports data and Figure 1 in Study 1 and attempt to convince themselves otherwise.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Study 1 summarizes: “The vast majority of new TLDs delegated since July 2014 have not been the subject of any name collision reports to ICANN” and “Of all the reports to ICANN, only one led to action by a registry.” There were no contemporaneous large-scale technical/operational problems, no litigation, and in the decade following widespread use of the 2012 procedures no evidence they caused harm and some evidence they were effective. A decade following the largest changes to the root in the History of the Internet and the attention of more technical experts than you can fit shoulder-to-shoulder in Oklahoma, this is not “absence of evidence” but rather “evidence of absence.” If this isn’t success, then what is? What specific problems are left to solve?<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">We should tweak 2012 procedures.</span></b><span class="apple-converted-space"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">I strongly feel that an upfront and deliberate discussion of the null hypothesis (do exactly what was done in 2012) would help better communicate our story and recommendations in a practical and actionable manner to the broad audience. There should be a high bar to recommend changes to procedures that largely worked by any reasonable definition of “worked.” <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">There should be a strong bias to “not break what isn’t broken” and a very high bar to invent new, risky, unproven, and expensive procedures with unclear value. When we are recommending implementation of a new procedure, it should be against a clear and compelling cost-benefit analysis not mere intellectual curiosity.<span class="apple-converted-space"> </span><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Moreover, we cannot simply ignore the realities of the increasing Balkanization of global privacy frameworks in Europe, Brazil, and in an increasing number of U.S. States to name a few – and their associated expense and risk. Any recommendation we make to the Board must not invite the kind of risk, expense, and frankly embarrassment ICANN was delt while debating WHOIS with the EU. ICANN’s “yes but we have really good wholesome reasons!” arguments largely fell on deaf ears with EU regulators and courts ending badly for ICANN; anything we recommend that invites that risk is impractical and a non-starter. <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">There is no perfect answer to the collisions issue, but with the exception of the predictability issues that plagued the 2012 round, I have yet to see a shred of evidence that would lead a reasonable person to believe that we can materially improve on what was done previously.<span class="apple-converted-space"> </span><i class="">The counter risk is apropos: we can certainly make it much, much worse.</i><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">“Enhanced Controlled Interruption” is a rebranded Honeypot.</span></b><span class="apple-converted-space"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">I don’t understand why we keep celebrating Groundhog Day by rehashing this same tired concept – it’s a terrible idea for all the reasons stated previously. It’s not just me saying this: <span class="apple-converted-space"> </span><i class="">“Verisign maintains its position that directing requesters to an internal address during the controlled interruption period is preferable to an external honeypot, because as previously stated, it avoids “controlled exfiltration” where sensitive traffic from an installed system – without the advance consent of the user or system administrator – may be drawn outside the local network.” [2]</i><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">The biggest problem to solve is the one of predictability (or lack thereof).</span></b><span class="apple-converted-space"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">In 2012, the collisions issue was not covered in pre-application procedures/documentation and unfortunately “sprung” on applicants late in the process. This caused applicants to face many delays and unknowns.<span class="apple-converted-space"> </span><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">As for the “Workflow” slides and the process they suggest, I have major concerns:<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">(a) It places the enormous burden of evaluating and mitigating collision risk on the applicant a-priori, something this group discussed and rejected last year as uneven, ripe for abuse and gaming, expensive, burdensome, and fundamentally impossible;<span class="apple-converted-space"> </span><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">(b) it uses honeypots rebranded as “enhanced controlled interruption” which is a practical nonstarter adding material (and likely insurmountable) risk and cost for no clear value;<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">(c) creates operational risk and costs by performing multiple delegations and re-delegations at the root per applied-for string with no clear value;<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">(d) suggests string-wise “mitigation proposals” and “remediation proposals” which are undefined, impossible to evaluate, will be enormously expensive given the liability implications, and unnecessary in nearly all cases;<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">(e) suggests a number of steps that simply create more data for which analysis is fundamentally subjective and open-ended and will require enormous resources in terms of both time and cost and add tremendous uncertainty, gamesmanship, and litigation risk; and<span class="apple-converted-space"> </span><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">(f) kicks the can to “the Board” to make several *per-string* decisions along the way with little in the way of frameworks or guidance - inviting litigation and other (expensive, high risk) conflict that was successfully avoided in 2012 by specifically avoiding all but three string-wise Board decisions.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">While many of us (myself included) find collisions intellectually interesting, we must avoid the temptation to “do more stuff” because it’s interesting and instead focus on providing succinct, practical, and implementable guidance to the Board. A decade later, there is no evidence to indicate that material improvements can be made to the 2012 procedures without also introducing material new costs and risks, so we should state that and make surgical improvements. Don’t break what isn’t broken. Don’t trade the tested and familiar – albeit imperfect – for high-risk, unknown, unproven, impractical, and in many cases unimplementable science experiments.<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Jeff<o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">[1]<span class="apple-converted-space"> </span><a href="https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(5, 99, 193);" class="">https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf</span></a><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">[2]<span class="apple-converted-space"> </span><a href="https://itp.cdn.icann.org/en/files/name-collision/report-comments-name-collision-10jun14-en.pdf" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(5, 99, 193);" class="">https://itp.cdn.icann.org/en/files/name-collision/report-comments-name-collision-10jun14-en.pdf</span></a><o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 8pt; font-size: 12pt; font-family: "Times New Roman", serif; line-height: 11.55pt;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></span></p><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">_______________________________________________<br class="">NCAP-Discuss mailing list<br class=""></span><a href="mailto:NCAP-Discuss@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: rgb(5, 99, 193);" class="">NCAP-Discuss@icann.org</span></a><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><br class=""></span><a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: rgb(5, 99, 193);" class="">https://mm.icann.org/mailman/listinfo/ncap-discuss</span></a><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><br class=""><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (</span><a href="https://www.icann.org/privacy/policy" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: rgb(5, 99, 193);" class="">https://www.icann.org/privacy/policy</span></a><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">) and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: rgb(5, 99, 193);" class="">https://www.icann.org/privacy/tos</span></a><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</span><o:p class=""></o:p></div></div></blockquote></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></span></div><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif; text-align: center;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><hr size="2" width="100%" align="center" class=""></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 7.5pt; font-family: Arial, sans-serif; color: gray;" class=""><br class="">This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.</span><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""></o:p></span></div></div><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><hr style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><font face="Arial" color="Gray" size="1" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class="">This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.</font></div></blockquote></div><br class=""></div></body></html>