<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="">Jim,<div class=""><br class=""></div><div class="">Part of our disagreement is that we are understanding terms very differently.<div class=""><br class=""></div><div class="">To me, "user notification" is ambiguous. It might refer to either or both of the following: disruption, which falls under the "effective alerting coverage" category (i.e., "something is wrong"); or root cause identification, which leads to the user to know what caused the issue. This is why the root causes analysis uses both "disruption" and "root cause identification".</div><div class=""><br class=""></div><div class="">Additionally, the finding quoted below has been quoted in isolation. Please see other findings for more context to support this. For example: "Usage of private DNS suffixes colliding with newly delegated TLDs has decreased over time." The analysis shows that private use of DNS suffixes has decreased over time, and the only mechanism that has been deployed thus far is controlled interruption. I would not therefore call that "ineffective."</div><div class=""><br class=""></div><div class="">Precision in language is important, particularly as we are categorically evaluating past and future methods.</div><div class=""><br class=""></div><div class="">Casey<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 1, 2023, at 11:41 AM, James Galvin <<a href="mailto:galvin@elistx.com" class="">galvin@elistx.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8" class="">
<div class=""><div style="font-family: sans-serif;" class=""><div class="plaintext" style="white-space: normal;"><p dir="auto" class="">These notes do not capture an important point that I made during the meeting.</p>
<br class=""><p dir="auto" class="">These notes say:</p><p dir="auto" class="">Finding E.a: Controlled Interruption is not effective for user notification: Casey believes this is a misrepresentation and noted the root cause analysis data supports his statement on this.</p>
<br class=""><p dir="auto" class="">The notes do not capture the point I made:</p><p dir="auto" class="">This finding is an accurate reflection supported by the Root Cause Analysis research.</p>
<br class=""><p dir="auto" class="">It would seem that Casey and I are drawing different conclusions from the report. However, in partial support of my support for the Study 2 Finding I submit the following Root Cause Analysis Finding (page 47):</p><p dir="auto" class="">Controlled interruption is effective at disruption, but not at root cause identification.</p><p dir="auto" class="">Controlled interruption has shown to be good at disruption, but not at helping affected users identify the cause of the problem—at least not in the way that was intended. Evidences. Of the survey respondents that indicated that they used of TLDs, 70% reported having experienced technical issues related to their suffix. Of those, 43% experienced the problems within days of delegation of the TLD. Over two-thirds (71%) of organizations experiencing technical problems indicated that they knew that the issues were related to TLD delegation before the problem was resolved. It appears that most of the ineffectiveness was due to the controlled interruption IP address not even being observed, which occurred in 71% of cases, according to the survey. However, when the controlled interruption IP address was observed, the success rate in identifying ICANN and controlled interruption as the cause was between 50% and 76%, according to the survey results and the Web search results analysis, respectively.</p>
<br class=""><p dir="auto" class="">I also made the point during the meeting that it seemed to me the issue being debated was simply the wording of the Study 2 Finding, not its factual assertion. I said then and I’m repeating now that I welcome suggestions for how to restate the Study 2 Finding.</p>
<br class=""><p dir="auto" class="">Thanks,</p><p dir="auto" class="">Jim</p>
<br class=""><br class=""><p dir="auto" class="">On 23 Feb 2023, at 6:02, Jennifer Bryce wrote:</p>
</div><blockquote class="embedded" style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><div id="AC309020-B35C-48B5-9DB1-A12E0EE22D8F" class="">
<div lang="EN-GB" link="#0563C1" vlink="purple" style="word-wrap:break-word" class="">
<div class="WordSection1" style="page: WordSection1;"><p class="MsoNormal">Dear NCAP Discussion Group members,</p><div class=""> <br class="webkit-block-placeholder"></div><p class="MsoNormal">The notes from the 22 February NCAP Discussion Group meeting are attached and will be posted to the meeting record on the wiki: <a href="https://community.icann.org/x/4YTKDQ" class="">https://community.icann.org/x/4YTKDQ</a>.</p><div class=""> <br class="webkit-block-placeholder"></div><p class="MsoNormal">The recording can be directly accessed here: <a href="https://icann.zoom.us/rec/play/sbcwTpyP5v0lmz_OTQFZOsWgFe056FPBSFGAo0pkQjKZ3WEmrCnLCmvgqEwLbFLTiQ619ysohCmhR35l.oNOIneK13LjTRyFh?continueMode=true&_x_zm_rtaid=69f-25JgT9uQd9f13bYzDw.1677121850114.64d0c334f967482c6f176722421c11dd&_x_zm_rhtaid=110" class="">https://icann.zoom.us/rec/play/sbcwTpyP5v0lmz_OTQFZOsWgFe056FPBSFGAo0pkQjKZ3WEmrCnLCmvgqEwLbFLTiQ619ysohCmhR35l.oNOIneK13LjTRyFh?continueMode=true&_x_zm_rtaid=69f-25JgT9uQd9f13bYzDw.1677121850114.64d0c334f967482c6f176722421c11dd&_x_zm_rhtaid=110</a></p><div class=""><span style="mso-fareast-language:EN-GB" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="mso-fareast-language:EN-GB" class="">One action item was captured:</span></p><div class=""><span style="mso-fareast-language:EN-GB" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><u class=""><span style="" class="">Action item</span></u><span style="" class="">: Discussion Group members should review <a href="https://docs.google.com/document/d/1H89gyy31dGVXQjn304PEGv85EKIpHUAR3vPm76YQMcc/edit" class="">Section 4: Findings</a> and make comments in the document to highlight the areas where they have concerns. This will aid discussion next week.</span></p><p class="p2" style="mso-style-name: p2; margin: 0cm; font-size: 8.5pt; font-family: 'Calibri',sans-serif;"><span style="font-size:11.0pt" class=""> </span></p><div style="margin: 0cm; font-size: 8.5pt; font-family: Calibri, sans-serif;" class=""><span style="font-size:11.0pt" class="">Best,</span></div><p class="MsoNormal">Jennifer</p>
<div class="">
<div class=""><p class="MsoNormal"><span style="mso-fareast-language:EN-GB" class="">-- </span></p>
</div>
<div class=""><p class="MsoNormal"><span lang="EN-US" style="color:#A6A6A6" class="">Jennifer Bryce</span></p><p class="MsoNormal"><span lang="EN-US" style="color:#A6A6A6" class="">Project Manager, Office of the Chief Technology Officer (OCTO)</span></p><p class="MsoNormal"><span lang="EN-US" style="color:#A6A6A6" class="">Internet Corporation for Assigned Names and Numbers (ICANN)</span></p><div class=""><span lang="EN-US" style="color:#A6A6A6" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span lang="EN-US" style="color:#A6A6A6" class="">Skype: jennifer.bryce.icann</span></p><p class="MsoNormal"><span lang="EN-US" style="color:#A6A6A6" class=""><a href="mailto:jennifer.bryce@icann.org" class="">Email: jennifer.bryce@icann.org</a></span></p>
</div>
</div>
</div>
</div></div></blockquote>
<div class="plaintext" style="white-space: normal;">
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;" class=""><p dir="auto" class="">_______________________________________________
<br class="">
NCAP-Discuss mailing list
<br class="">
<a href="mailto:NCAP-Discuss@icann.org" class="">NCAP-Discuss@icann.org</a>
<br class="">
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" style="color: #777777;" class="">https://mm.icann.org/mailman/listinfo/ncap-discuss</a></p><p dir="auto" 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 (<a href="https://www.icann.org/privacy/policy" style="color: #777777;" class="">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" style="color: #777777;" class="">https://www.icann.org/privacy/tos</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.</p>
</blockquote></div>
</div></div>
_______________________________________________<br class="">NCAP-Discuss mailing list<br class=""><a href="mailto:NCAP-Discuss@icann.org" class="">NCAP-Discuss@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/ncap-discuss<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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). 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.</div></blockquote></div><br class=""></div></div></body></html>