<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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size: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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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="MsoPlainText">Thanks Jim. I note the following statement has been an underlying premise of our discussions for quite some time now – I believe from the first review of the draft Workflow document.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="color:#0070C0">"ECI exists because it is currently the only mechanism that has been proposed to obtain sufficient information to develop a mitigation or remediation plan. We can certainly note the additional risks that
the ICANN Board will need to consider, that are outside the technical scope of our work."<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I support the approach taken by your email below in relation to identification of risks and corresponding legal issues that would have to be addressed. I also note that getting to the bottom of these issues may be very important to
being able to conduct Study 3, which is designed to develop mitigation strategies. In other words, it looks to me as though appropriate mitigation strategies cannot be developed without ECI and that an inability to proceed to that step means more strings
with high Impact (Volume and Diversity) will simply be ruled “not approved for delegation”.<o:p></o:p></p>
<p class="MsoPlainText">Anne<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Anne E. Aikman-Scalese<o:p></o:p></p>
<p class="MsoPlainText">Of Counsel<o:p></o:p></p>
<p class="MsoPlainText">AAikman@lewisroca.com<o:p></o:p></p>
<p class="MsoPlainText">D. 520.629.4428<o:p></o:p></p>
<p class="MsoPlainText">Lewis Roca Rothgerber Christie LLP<o:p></o:p></p>
<p class="MsoPlainText">One South Church Avenue, Suite 2000<o:p></o:p></p>
<p class="MsoPlainText">Tucson, Arizona 85701-1611<o:p></o:p></p>
<p class="MsoPlainText">lewisroca.com<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: NCAP-Discuss <ncap-discuss-bounces@icann.org> On Behalf Of James Galvin<br>
Sent: Monday, February 21, 2022 12:45 PM<br>
To: NCAP Discussion Group <ncap-discuss@icann.org><br>
Subject: [NCAP-Discuss] why enhanced controlled interruption - not legal</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">[EXTERNAL]<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Speaking as co-Chair:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This discussion of the purpose and value of enhanced controlled interruption is essential. As a group we need to understand all points of view, make sure to defend any choice we make, and mention relevant counterpoints so the community
understands why we made our choice.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Toward that end I want to remind us that this is a technical group and we ultimately will make the best technical choice we can based on the data we have at hand.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">There are legal questions associated with the use of enhanced controlled interruption. There are related business, privacy, and liability questions. These questions have very limited scope in our work. It is appropriate for us to
note the questions and suggest future study of them, but in general it is not within scope for us to resolve them.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Let’s remind ourselves as to why enhanced controlled interruption (ECI) is part of our currently proposed solution.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">We have been asked to provide guidance on how to assess name collisions and consider what mitigation and remediation might be possible. The data we have tells us the following.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">1. Root servers do not have a full picture of name collisions by themselves.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">2. What we do know from root servers is only from DNS queries and that information is waning as the DNS infrastructure evolves.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Those two facts alone tell us the development of a mitigation and remediation plan is problematic at best.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">ECI exists because it is currently the only mechanism that has been proposed to obtain sufficient information to develop a mitigation or remediation plan. We can certainly note the additional risks that the ICANN Board will need to
consider, that are outside the technical scope of our work.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Or, if another mechanism or procedure manifests in our discussions, then we’ll certainly consider that.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I don’t want to repeat discussion we’ve already had. As we develop text for our final work product all of this will get discussed again and captured appropriately. Please do continue the discussion on the list as it will inform our
final work product.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Jim<o:p></o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">NCAP-Discuss mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:NCAP-Discuss@icann.org"><span style="color:windowtext;text-decoration:none">NCAP-Discuss@icann.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><a href="https://mm.icann.org/mailman/listinfo/ncap-discuss"><span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/ncap-discuss</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">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:windowtext;text-decoration:none">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:windowtext;text-decoration:none">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></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>