<div dir="ltr">Matthias,<div><br></div><div>thanks very much for this rich information. The summaries alone should be considered as strong alarm signs. The foci of attention of ALAC and At-Large seem way out of phase, lagging years behind these developments. This is not uniform; some RALOs are in even worse shape, considering recent publicly available evidence. </div><div><br></div><div>Alejandro Pisanty</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 21, 2023 at 12:21 AM Matthias M. Hudobnik via At-Large <<a href="mailto:at-large@atlarge-lists.icann.org">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 class="msg2838165630227609614"><div lang="DE-AT"><div class="m_2838165630227609614WordSection1"><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">Hi colleagues, the SSAC has published SAC123 and SAC122.<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:rgb(31,73,125)"><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:rgb(31,73,125)"><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"">### SSAC Report on the Evolution of Internet Name Resolution (SAC123):<u></u><u></u></span></b></p><p class="m_2838165630227609614MsoListParagraphCxSpFirst"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Internet name resolution is evolving beyond just the global DNS to include alternative naming systems that are experimenting with different approaches for reasons like speed, privacy, censorship resistance, and governance.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Many alternative systems adopt DNS name syntax to leverage existing software.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Two concerning trends are increased ambiguity where the same name can resolve differently in different systems, and less visibility of names to end users even as names remain vital for security and trust.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Maintaining integrity and coordination in the shared domain namespace is important.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">The report explores different perspectives on these trends from end users and developers.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpLast"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">It identifies proposals to facilitate namespace coordination and recommends ICANN continue tracking these issues and provide regular updates to the community.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">I highly recommend having a look at chapter: <b>7.1 End Users </b>(some key aspects as follows):<b><u></u><u></u></b></span></p><p class="m_2838165630227609614MsoListParagraphCxSpFirst" style="margin-left:54pt"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Domain names used to play an important role for end users in discovering web resources, but search engines have now replaced them as the primary method of discovery.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle" style="margin-left:54pt"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">End users today rarely directly interact with domain names due to the dominance of search engines and mobile devices. Features like browser "omnibars" also allow more free-form input.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle" style="margin-left:54pt"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Other identifiers like QR codes and social media handles now also compete for users' attention rather than domain names.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle" style="margin-left:54pt"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Domain names are becoming less visible in users' environments, yet they still provide an underlying ubiquitous resolution context relied upon by other technologies.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle" style="margin-left:54pt"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Surveys found search engines are by far the predominant method for accessing websites, with domain name usage declining. QR code usage is increasing but still limited except in Asia.<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpLast" style="margin-left:54pt"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Decreased domain name visibility makes it easier for fraudsters to deceive users with lookalike names. Users are also generally unaware that some TLDs signal a different resolution context.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">In summary, domain names are no longer the primary method end users employ to find and access Internet resources, decreasing their visibility and understandability while introducing security issues.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif""><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">Link to the report: </span><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif""><a href="https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-123-15-12-2023-en.pdf" target="_blank"><span lang="EN-US">https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-123-15-12-2023-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)"><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:rgb(31,73,125)"><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:rgb(31,73,125)"><u></u> <u></u></span></p><div><div><div><div><div><p class="MsoNormal"><b><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">### SSAC Report on Urgent Requests in gTLD Registration Data Policy (SAC122)<u></u><u></u></span></b></p><p class="m_2838165630227609614MsoListParagraphCxSpFirst"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Focus is on handling of Urgent Requests in proposed gTLD registration data policy <u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Urgent Requests refer to imminent threats to life, injury, infrastructure or child exploitation<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Proposed policy requires response to Urgent Requests in 24 hours generally<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">SSAC contends proposed policy for Urgent Requests is not fit for purpose<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Definition and required response times are incompatible <u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Questions if need and rationale for separate Urgent Request process is fully justified<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Existing ICANN policy and industry practices offer useful precedents <u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Proposed extensions allow responses up to 7 days, not reflecting urgency<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Lack of concrete data on frequency and handling of such requests currently<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle"><u></u><span lang="EN-GB" style="font-family:Symbol"><span>·<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Risks reputation of ICANN multistakeholder model effectiveness <u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle" style="margin-left:72pt"><u></u><span lang="EN-GB"><span>-<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Provides 3 recommendations <u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle" style="margin-left:108pt"><u></u><span lang="EN-GB" style="font-family:Wingdings"><span>§<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Add structure to ensure Urgent Requests handled expediently <u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpMiddle" style="margin-left:108pt"><u></u><span lang="EN-GB" style="font-family:Wingdings"><span>§<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Tighten response time requirements to be fit for purpose<u></u><u></u></span></p><p class="m_2838165630227609614MsoListParagraphCxSpLast" style="margin-left:108pt"><u></u><span lang="EN-GB" style="font-family:Wingdings"><span>§<span style="font:7pt "Times New Roman""> </span></span></span><u></u><span lang="EN-GB" style="font-family:"Franklin Gothic Book","sans-serif"">Gather data on Urgent Requests for future policy making<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">Link to the report: </span><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif""><a href="https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-122-12-12-2023-en.pdf" target="_blank"><span lang="EN-US">https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-122-12-12-2023-en.pdf</span></a> </span><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif""><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif""><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">Have a nice evening!<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">Best,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11pt;font-family:"Franklin Gothic Book","sans-serif"">M.<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 class="m_2838165630227609614MsoPlainText">______________________________<u></u><u></u></p><p class="m_2838165630227609614MsoPlainText">Ing. Mag. Matthias M. Hudobnik<u></u><u></u></p><p class="m_2838165630227609614MsoPlainText">FIP • CIPP/E • CIPT • DPO • CIS LA<u></u><u></u></p><p class="m_2838165630227609614MsoPlainText"><a href="mailto:matthias@hudobnik.at" target="_blank">matthias@hudobnik.at</a><u></u><u></u></p><p class="m_2838165630227609614MsoPlainText"><a href="http://www.hudobnik.at" target="_blank">http://www.hudobnik.at</a><u></u><u></u></p><p class="m_2838165630227609614MsoPlainText">@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>- - - - - - - - - - - - - - - - - - - - - - - - - - -<br> Dr. Alejandro Pisanty<br>Facultad de Química UNAM<br>Av. Universidad 3000, 04510 Mexico DF Mexico<br>+525541444475<br>Blog: <a href="http://pisanty.blogspot.com" target="_blank">http://pisanty.blogspot.com</a><br>LinkedIn: <a href="http://www.linkedin.com/in/pisanty" target="_blank">http://www.linkedin.com/in/pisanty</a><br>Unete al grupo UNAM en LinkedIn, <a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614" target="_blank">http://www.linkedin.com/e/gis/22285/4A106C0C8614</a><br>Twitter: <a href="http://twitter.com/apisanty" target="_blank">http://twitter.com/apisanty</a><br>---->> Unete a ISOC Mexico, <a href="http://www.isoc.org" target="_blank">http://www.isoc.org</a><br>. . . . . . . . . . . . . . . .</div></div></div>