[NCAP-Discuss] Root Cause Analysis Report

[Aikman-Scalese, Anne]

Thank you, Casey.
Anne

Anne E. Aikman-Scalese

Of Counsel



AAikman at lewisroca.com<mailto:AAikman at lewisroca.com>

D. 520.629.4428

[cid:image003.png at 01D856EE.621729C0]



From: Casey Deccio <casey at deccio.net>
Sent: Friday, April 22, 2022 3:40 PM
To: Aikman-Scalese, Anne <AAikman at lewisroca.com>
Cc: NCAP Discussion Group <ncap-discuss at icann.org>
Subject: Re: [NCAP-Discuss] Root Cause Analysis Report

[EXTERNAL]
________________________________
Hi Anne,


On Apr 21, 2022, at 2:46 PM, Aikman-Scalese, Anne <AAikman at lewisroca.com<mailto:AAikman at lewisroca.com>> wrote:


1.       Could you please supply the blank survey forms that are referenced as Appendix A General Name Collisions Survey and Appendix B Targeted Name Collisions Survey as well as the survey form that appears at the link that is referenced in Appendix C General Email Sent to NANOG Subscribers and Appendix D  - Targeted Email Sent to AS Contacts?

I've added these.

2.       For appropriate context for the data you have been collecting and analyzing, I think it is important to add language in the section on “Name Collisions Reports Submitted via ICANN’s Web Form”  (on page 5?) which accurately describes the circumstances under which ICANN was soliciting reports as shown in the link you provided.   This is necessary because no one will actually go to that link when reading your report.    (Another possible location for the recommended text to be added is under the section called “Name Collisions Report Analysis”  (on page 7?)


I have added a new Appendix A, which contains the form in its entirety.  I've also added the following paragraph to the "Impact" subsection of the "Name Collisions Reports Analysis":

Our analysis shows that only half (50%) were classified as either severe or significant.  However, we note that the text on the Web site suggests that reports are for systems “suffering demonstrably severe harm as a consequence of name collision” and that emergency response actions would be taken “only where there is a reasonable belief that the name collision presents a clear and present danger to human life” (See Appendix A).  Thus, either our classifications are inaccurate, the reports understate the magnitude of the problems experienced, and/or the reports were submitted notwithstanding the suggested criteria—perhaps to officially document the problem.  Nonetheless, this creates additional bias in the reports: potential submitters might have been dissuaded from submitting the form because of the above criteria.

Thanks,
Casey

________________________________

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20220423/e0c0ca6c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 2031 bytes
Desc: image003.png
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20220423/e0c0ca6c/image003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 212 bytes
Desc: image004.png
URL: <https://mm.icann.org/pipermail/ncap-discuss/attachments/20220423/e0c0ca6c/image004.png>