<div dir="ltr">Thank you Matthias!<div>It is worth noting that the project implementation spanned many years with numerous days and hours invested by the SSAC working group under the guidance of Suzanne & Matt. The project also required active involvement from ICANN org and many other ICANN stakeholders. This document stands as a testament to meticulous work, countless discussions, debates and compromises.<br></div><div>Great job!</div><div><br></div><div>--andrei</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 7, 2024 at 12:20 PM Matthias M. Hudobnik via At-Large <<a href="mailto:at-large@atlarge-lists.icann.org" target="_blank">at-large@atlarge-lists.icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div lang="DE-AT"><div><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">Hi colleagues, the SSAC has published SAC124.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black"><u></u> <u></u></span></p><p class="MsoNormal"><b><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">### SSAC Advice on Name Collision Analysis (SAC124):<u></u><u></u></span></b></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">The SSAC provides its advice on name collision analysis based on the NCAP Study Two report. The SSAC fully endorses the findings and recommendations presented in the report and recommends the ICANN Board adopt and implement these recommendations.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">The SSAC supports the centralized and coordinated approach proposed by Study Two. This approach is essential for implementing effective measures to mitigate the two data-access-related risks associated with name collisions:<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">Delegation Risk: Privacy and risks to users and end systems from name collisions associated with the delegation of a TLD.<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">Assessment Risk: Privacy risks associated with the execution of data collection methods in the proposed Name Collision Risk Assessment Framework.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">While acknowledging ICANN org's privacy concerns around the proposed data collection methods, the SSAC offers three considerations:<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">Privacy risks are inherent in managing name collision risk due to ICANN's role in coordinating gTLD allocation and assignment.<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">Avoiding data collection does not resolve delegation privacy risks, but rather transfers these risks to third parties, potentially amplifying harm.<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">Effective management of security, stability and resiliency risks requires a proactive approach to name collision identification and mitigation.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">Based on these, the SSAC recommends prioritizing solutions that allow sufficient data collection and analysis to properly inform name collision mitigation strategies. Failing to mitigate delegation risks due to assessment risk concerns would threaten DNS security/stability and end-user privacy.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">The SSAC's recommendations are:<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">Adopt and implement all recommendations in NCAP Study Two.<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">Prioritize finding appropriate solutions within the proposed framework that enable sufficient data collection and analysis for mitigation.<u></u><u></u></span></p><p><u></u><span lang="EN-US" style="font-family:Symbol;color:black"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif";color:black">The SSAC welcomes engagement from ICANN org and offers its expertise.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">The SSAC acknowledges more work is needed on privacy aspects and looks forward to collaborating with ICANN org and privacy experts.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">Link to the report: <a href="https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-124-01-05-2024-en.pdf" target="_blank"><span style="color:black">https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-124-01-05-2024-en.pdf</span></a></span><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:rgb(31,73,125)">. </span><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black"><u></u><u></u></span></p><div><div><div><div><div><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">Have a nice day!<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">Best,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif";color:black">Matthias<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-family:"Franklin Gothic Book","sans-serif""><u></u> <u></u></span></p><p>______________________________<u></u><u></u></p><p>Ing. Mag. Matthias M. Hudobnik<u></u><u></u></p><p>FIP • CIPP/E • CIPT • DPO • CIS LA<u></u><u></u></p><p><a href="mailto:matthias@hudobnik.at" target="_blank">matthias@hudobnik.at</a><u></u><u></u></p><p><a href="http://www.hudobnik.at" target="_blank">http://www.hudobnik.at</a><u></u><u></u></p><p>@mhudobnik<span lang="EN-US"><u></u><u></u></span></p></div></div></div></div></div></div></div>
_______________________________________________<br>
At-Large mailing list<br>
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank">At-Large@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site: <a href="http://atlarge.icann.org" rel="noreferrer" target="_blank">http://atlarge.icann.org</a><br>
_______________________________________________<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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">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.</div></blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Andrei Kolesnikov <a href="http://IOTAS.RU" target="_blank">IOTAS.RU</a> with calendar bot<br></div></div></div>