<html xmlns:v="urn:schemas-microsoft-com:vml" 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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Jeff. You make it sound as though the Sub Pro Working group was somehow going to recommend or require additional policy work to arrive at a new Name Collision Framework. This is not the case. The Recommendation
and Implementation Guidance appears below. In this regard, I know that you know that the term “MUST” is a defined term in the Final Report. I consider the work being done in NCAP to be fulfilling Recommendation 29.1 and “use the old system from 2012” is
certainly not an answer to this Final Report Recommendation 29.1. (This will only slow the process if we cannot achieve constructive participation to fulfill 29.1 because the Board will say – as part of ODP – “go back and work it out”.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Anne<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt;font-family:"Arial",sans-serif">Topic 29: Name Collisions</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">a. Recommendations and/or implementation guidelines</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Recommendation 4 from the 2007 policy is affirmed under Topic 26: Security and</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Stability. Recommendation 4 is also relevant to this topic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Recommendation 29.1: ICANN
<b>must</b> (emphasis mine) have ready prior to the opening of the Application</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Submission Period a mechanism to evaluate the risk of name collisions in the New gTLD</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">evaluation process as well as during the transition to delegation phase.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Affirmation 29.2: The Working Group affirms continued use of the New gTLD Collision</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Occurrence Management framework
<b>unless and until the ICANN Board adopts a new</b></span><b><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span></b><b><span style="font-size:15.0pt;font-family:"Arial",sans-serif">mitigation framework.</span></b><span style="font-size:15.0pt;font-family:"Arial",sans-serif"> This includes not changing the controlled interruption duration</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">and the required readiness for human-life threatening conditions for currently delegated</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">gTLDs and future new gTLDs.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">186</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Implementation Guidance 29.3: To the extent possible, ICANN should seek to</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">identify high-risk strings in advance of opening the Application Submission</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Period, which should constitute a “Do Not Apply” list. ICANN should also seek</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif">186 </span><span style="font-size:12.5pt;font-family:"Arial",sans-serif">“Registry Operators will implement a period of, at least, 90 days of continuous controlled interruption.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:12.5pt;font-family:"Arial",sans-serif">ICANN will monitor and time the implementation of the measure, primarily using the zone files that are</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:12.5pt;font-family:"Arial",sans-serif">transferred to ICANN from new gTLD registries once they are delegated (per Specification 4 off the new</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:12.5pt;font-family:"Arial",sans-serif">gTLD Registry Agreement).”, 3. Controlled Interruption, and 7. Emergency Response, pages 2 and 4, in the</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:12.5pt;font-family:"Arial",sans-serif">New gTLD Collision Occurrence Management framework. See:</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:12.5pt;font-family:"Arial",sans-serif">https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:15.0pt;font-family:"Arial",sans-serif">New gTLD Subsequent Procedures Final Report Date: 20 January 2021</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Page 135 of 400</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">to identify aggravated risk strings in advance of the next application window</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">opening and whether it would require a specific name collision mitigation</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">framework.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Implementation Guidance 29.4: To the extent possible, all applied-for strings</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">should be subject to a DNS Stability evaluation to determine whether they</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">represent a name collision risk.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Implementation Guidance 29.5: The ICANN community should develop name</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">collision risk criteria and a test to provide information to an applicant for any</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">given string after the application window closes so that the applicant can</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">determine if they should move forward with evaluation.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">Implementation Guidance 29.6: If controlled interruption (CI) for a specific label</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">(usually a 2nd-level domain) is found to cause disruption, ICANN may decide to</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">allow CI to be disabled for that label while the disruption is fixed, provided that</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">the minimum CI period is still applied to that label.</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:106%"><b><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Anne E. Aikman-Scalese</span></b><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:106%"><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Of Counsel</span><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:40%"><span style="font-size:10.0pt;line-height:40%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><img width="17" height="7" style="width:.1805in;height:.0763in" id="_x0000_i1033" src="cid:image002.png@01D82965.BCA38B60"></span><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:106%"><span style="font-size:10.0pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><a href="mailto:AAikman@lewisroca.com" target="_new" title="Email User"><span style="color:#323232">AAikman@lewisroca.com</span></a></span><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:.25in;line-height:106%"><span style="font-size:10.0pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:#323232">D. 520.629.4428</span><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:106%"><span style="font-size:10.0pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><img border="0" width="160" height="22" style="width:1.6666in;height:.2291in" id="_x0000_i1032" src="cid:image007.png@01D82965.BABACE30"></span><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jeff Neuman <jeff@jjnsolutions.com> <br>
<b>Sent:</b> Thursday, February 24, 2022 8:01 AM<br>
<b>To:</b> Aikman-Scalese, Anne <AAikman@lewisroca.com>; ncap-discuss@icann.org<br>
<b>Subject:</b> RE: Enhanced Controlled Interruption and Predictability<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="3" width="100%" align="center">
</span></div>
</div>
<p class="MsoNormal">Anne,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">That is a misstatement of SubPro Recommendations:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Here is what it says: “The Working Group affirms continued use of the New gTLD Collision Occurrence Management framework unless and until the ICANN Board adopts a new mitigation framework.” It references the NCAP in the rationale of course
as working on the issue, but it never just delegated all policy to the NCAP or SSAC to decide. That is no where in the recommendations or rationale. The SubPro Recommendation never states that the GNSO waives all of its policy development rights in favor
of the NCAP Study Group. In fact, it is quite the opposite by stating “The Working Group agreed that it is up to the ICANN community and ICANN Board of Directors to determine any dependencies between the NCAP and the next round of new gTLD applications” See
<a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-20jan21-en.pdf">
https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-20jan21-en.pdf</a>, starting on Page 134 (Topic 29).<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">So, putting the recommendations of SubPro aside for the moment, I am not saying that the SSAC should develop the mitigation plans, but rather that this group, the SSAC, and the community need to make the process incredibly predictable and
provide guidelines to applicants (and instructions) on how to create an acceptable mitigation plan. ICANN can ask an applicant to submit a mitigation plan addressing the issues found, but who the heck is going to know how to come up with an acceptable mitigation
plan. There are very few experts globally that even know what name collision means, much less know what the implications of collision are. I would venture to say that there are even few people that would know how to draft a Name Collision mitigation plan,
especially because we cant even quantify the harm that needs to be mitigated. In short, it is an impossible task that is fraught with unknown subjectivity depending on the beliefs, expertise and biases of the evaluator. That is a process to me that is doomed
to fail, cause expensive litigation, and in exchange for what? ---- Trying to solve a situation which we really will never know is a problem or not.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Yes, we have data that there are collisions going on. Great. We have no idea if it is causing actual harm, no idea if those causing the collisions actually know or care about the collisions, have no idea whether the collisions are intentional
or accidental, etc. Yet, by requiring “mitigation”, we are assuming (a) the collisions are unintentional, (b) they are causing harm, (c) the benefit of implementing controlled interruption is greater than the risks associated with the name collision, etc……<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Having lots of data with no understanding of what it means is not a great way to set policies that can have significant repercussions and costs.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="193" valign="bottom" style="width:144.3pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0in"><img border="0" width="178" height="81" style="width:1.8541in;height:.8402in" id="Picture_x0020_3" src="cid:image003.png@01D82965.BCA38B60"></span><o:p></o:p></p>
</td>
<td width="173" valign="bottom" style="width:129.95pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">E:
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><a href="mailto:jeff@jjnsolutions.com"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black"><a href="http://jjnsolutions.com">http://jjnsolutions.com</a></span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com">AAikman@lewisroca.com</a>>
<br>
<b>Sent:</b> Wednesday, February 23, 2022 3:25 PM<br>
<b>To:</b> Jeff Neuman <<a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a>>;
<a href="mailto:ncap-discuss@icann.org">ncap-discuss@icann.org</a><br>
<b>Subject:</b> RE: Enhanced Controlled Interruption and Predictability<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Jeff – the policy was already developed in Sub Pro. As far as I know, it states very clearly that if NCAP develops a new Name Collision Framework that is recommended to the Board and the Board adopts it, that
new Name Collision Framework will apply. It’s one of the formal Recommendations in the Sub Pro Final Report and this contingency is noted in the ODP for the next round.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">What am I missing as to your comment re policy development?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Anne</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:105%"><b><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Anne E. Aikman-Scalese</span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:105%"><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Of Counsel</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:40%"><span style="font-size:10.0pt;line-height:40%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><img border="0" width="17" height="7" style="width:.1805in;height:.0763in" id="_x0000_i1027" src="cid:image004.png@01D82965.BCA38B60"></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:105%"><span style="font-size:10.0pt;line-height:105%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><a href="mailto:AAikman@lewisroca.com" target="_new" title="Email User"><span style="color:#323232">AAikman@lewisroca.com</span></a></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:.25in;line-height:105%"><span style="font-size:10.0pt;line-height:105%;font-family:"Trebuchet MS",sans-serif;color:#323232">D. 520.629.4428</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:105%"><span style="font-size:10.0pt;line-height:105%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><img border="0" width="160" height="22" style="width:1.6666in;height:.2291in" id="Picture_x0020_2" src="cid:image007.png@01D82965.BABACE30"></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org">ncap-discuss-bounces@icann.org</a>>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Tuesday, February 22, 2022 11:58 AM<br>
<b>To:</b> <a href="mailto:ncap-discuss@icann.org">ncap-discuss@icann.org</a><br>
<b>Subject:</b> [NCAP-Discuss] Enhanced Controlled Interruption and Predictability<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="2" width="100%" align="center">
</span></div>
</div>
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Purposefully, I am going to ignore all of the legal, policy and business reasons to do (or not do) Enhanced Controlled Interruption. The question I have is whether ECI violates the GNSO Unanimous Consensus Policy that all processed and
procedures surrounding the introduction of new gTLDs be predictable.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Lets suppose we do Enhanced Controlled Interruption and there is a whole lot of data collected by some Honeypot operator. Then what? The Honeypot Operator (HPO) attempts to contact those that have misconfigured servers or whatever. But
what then? Who makes the decision to allow (or not allow) the delegation of the TLD to the Registry Operator to continue so that it can launch the TLD? What criteria is used by the decision maker to either allow or not allow the next steps to go forward?
Does this just create more uncertainty by another decision maker inserted into the process to decide if and when the next steps of the launch can proceed? How does that enhance predictability in the process?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I understand that this is a “technical group”, but the Board needs to be told explicitly that we are only recommending what we as the technical group think should happen, but that the policy needs to be developed to determine whether the
benefits of this new technical approach are outweighed by the other policy aspects of implementing the next rounds of new TLDs.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I hope that makes sense.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="192" valign="bottom" style="width:144.3pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0in"><img border="0" width="178" height="81" style="width:1.8541in;height:.8402in" id="Picture_x0020_1" src="cid:image005.png@01D82965.BCA38B60"></span><o:p></o:p></p>
</td>
<td width="173" valign="bottom" style="width:129.95pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">E:
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><a href="mailto:jeff@jjnsolutions.com"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black"><a href="http://jjnsolutions.com">http://jjnsolutions.com</a></span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
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><o:p></o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
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.
<br>
</font>
</body>
</html>