<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=utf-8">
<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:"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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">James,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The approach you have set forth sounds good in theory, but in practice is fraught with uncertainty and will invariably lead to incredible amounts of delay for a situation where even if there is data of collisions, there may be no evidence
of truly adverse consequences from the collisions. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And to top if off, the concept of mitigating collisions with one or more organizations that may not know (or care) about the collisions is a nearly impossible task.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The reason I am not in favor of this new approach is that it shifts all of the burden to the those wanting to see the TLD delegated as opposed to the those that either (a) misconfigured their systems, or worse (b) intentionally configured
their systems in such a way to take advantage of the fact that ICANN has not delegated that particular string. And this is where it all breaks down.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It would be one thing if we could show that entities are (or will be) truly hurt by these collisions. But to assume that they will be hurt and then to put a burden on those seeking delegation when it is just as possible that the collisions
are being caused by intentional activities to me seems wrong.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Therefore, when you state that the applicant needs to have a mitigation plan, what does that mean? What guidance do we have for those plans? How is an applicant supposed to know what to do. And how can an applicant mitigate a situation
where the colliding entity does not know (or potentially does not care) that there are collisions.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>If we require a mitigation plan</b>, it needs to be one that is predictable and not outcome based. In other words, the Applicant should only be required to do what is reasonable and if the colliding entity(ies) do not know about it,
or care about it, then the applicant should not be held responsible at all.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Finally, any technical solution requires policy folks to look at the technical solution to see if it is an acceptable policy outcome. In other words, the policy folks should be able to override any technical solution if it is determined
that there are other more important policy considerations than the ones we are attempting to mitigate.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ICANN too frequently takes “advice” from the SSAC as being advice from up above and therefore feels compelled to adopt it for fear of risking the security and stability of the Internet. However, I do not see our proposed solution as solving
something that threatens the security and stability of the Internet, but rather as solving a situation that
<i>perhaps</i> threatens an individual organization that is causing the potential collisions. I am not saying that it is not important work, but perhaps the policies of predictability and the other new gTLD policies could override the speculative potential
harm by any of these collisions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just some food for thought.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none">
<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 width="178" height="81" style="width:1.8489in;height:.8437in" id="Picture_x0020_2" src="cid:image001.png@01D827FF.A919BE50"></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><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></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><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">http://jjnsolutions.com</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></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> James Galvin <galvin@elistx.com> <br>
<b>Sent:</b> Tuesday, February 22, 2022 2:46 PM<br>
<b>To:</b> Jeff Neuman <jeff@jjnsolutions.com><br>
<b>Cc:</b> ncap-discuss@icann.org<br>
<b>Subject:</b> Re: [NCAP-Discuss] Enhanced Controlled Interruption and Predictability<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p><span style="font-family:"Arial",sans-serif">Excellent questions, Jeff. Speaking personally, I think your questions fit in that space between purely technical and purely legal. policy, and business.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">I would say we are obligated to inform the Board with our best advice on how to interpret the data showing the existence of name collisions and then how to review mitigation and remediation plans. So we have to
say something about your questions, beyond just listing them.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">I don’t think we’re going to be able to propose a solution that is 100% predictable though. I’d be delighted to be educated differently.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">Other folks should certainly offer their own ideas for how to answer your questions. Here are some ideas from me for folks to consider.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">1. ECI is conducted, data is collected (details still to be defined), and data is made available to Applicant and Technical Review Team.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">2. Applicant develops either or both a mitigation plan or remediation plan.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">3. Technical Review Team develops summary of what the collected data means, the Applicant plan(s), and a technical indication of the extent to which the plan(s) address the aforementioned issues. Think of this
as technical due diligence in much the same way that Staff effectuate due diligence on the rest of the application.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">4. The Board reviews the original application, its due diligence report from ICANN staff, the plan(s) from the Applicant, and the independent review conducted by the Technical Review Team to decide whether or
not to delegate the TLD to the Applicant.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">What are the benefits of our approach?<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">Data will be collected about the existence of name collisions for each proposed application, each Applicant will have the opportunity to address what the data shows, and then the Board will be able to make a decision
about the Application. These three steps had an extremely limited presence in the 2012 round. In particular, although most TLDs were granted, we have three that are still officially “deferred”, since we didn’t have a means to properly evaluate them.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">We are developing a proposal to do just that.<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">Alternate points of view and proposals are most welcome!<o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">Jim<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p><span style="font-family:"Arial",sans-serif">On 22 Feb 2022, at 13:58, Jeff Neuman wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #777777 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<div id="C01DDB2A-4A9D-4D94-84BE-80C5C36DFEFA">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777">All,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777">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></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777">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></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777">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></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777">I hope that makes sense.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777"> <o:p></o:p></span></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="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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:.8437in" id="_x0000_i1025" src="cid:image001.png@01D827F4.364CB590"></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="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify">
<span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#777777"> <o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<blockquote style="border:none;border-left:solid #777777 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:0in;margin-right:0in;margin-bottom:3.75pt">
<p><span style="font-family:"Arial",sans-serif;color:#777777">_______________________________________________
<br>
NCAP-Discuss mailing list <br>
<a href="mailto:NCAP-Discuss@icann.org">NCAP-Discuss@icann.org</a> <br>
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss"><span style="color:#777777">https://mm.icann.org/mailman/listinfo/ncap-discuss</span></a><o:p></o:p></span></p>
<p><span style="font-family:"Arial",sans-serif;color:#777777">_______________________________________________
<br>
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 (<a href="https://www.icann.org/privacy/policy"><span style="color:#777777">https://www.icann.org/privacy/policy</span></a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos"><span style="color:#777777">https://www.icann.org/privacy/tos</span></a>). 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.<o:p></o:p></span></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>