<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
Phil Katz has got to be rolling in his grave!
<div><br>
</div>
<div id="ms-outlook-mobile-signature" dir="auto"><b>Jonathan Zuck</b>
<div dir="auto"><i>Director</i>, Future of Work Project</div>
<div dir="auto">Innovators Network Foundation</div>
<div dir="auto">www.InnovatorsNetwork.org</div>
<div dir="auto"><br>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> NA-Discuss <na-discuss-bounces@atlarge-lists.icann.org> on behalf of Evan Leibovitch via NA-Discuss <na-discuss@atlarge-lists.icann.org><br>
<b>Sent:</b> Saturday, May 27, 2023 4:18:34 PM<br>
<b>To:</b> NARALO Discussion List <na-discuss@atlarge-lists.icann.org><br>
<b>Subject:</b> [NA-Discuss] Protecting the public interest: dot-zip</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
While my hopes that ALAC will champion this are dim, and ICANN itself is even less likely to act, I draw your attention to a policy goof that is already causing public harm and is likely to cause far more.</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
Now anyone can buy a dot-zip second-level domain, ie evan.zip or naralo.zip<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
As anyone who works with computers should know, long before dot-zip was a domain it was a very popular computer-file extension to denote something that contained a file (or collection of files) in compressed form. Such a collection could easily contain malicious
data or code.<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
Is anyone seeing the problem? People could be sent "attachments" that are really URLs and URLs that are really attachments. The potential for end-user confusion and harm is immense.<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
Here are two videos that explain the situation well:<br>
<a href="https://www.youtube.com/watch?v=GCVJsz7EODA">https://www.youtube.com/watch?v=GCVJsz7EODA</a><br>
<a href="https://www.youtube.com/watch?v=V82lHNsSPww">https://www.youtube.com/watch?v=V82lHNsSPww</a></div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
<br>
</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
Is anyone in domain-world looking at this?</div>
<div class="x_gmail_default" style="font-family:tahoma,sans-serif; color:#0b5394">
<br>
</div>
<div>
<div dir="ltr" class="x_gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div style="text-align:center">
<div style="text-align:left">Evan Leibovitch, <span style="font-size:12.8px">Toronto Canada</span></div>
<div style="text-align:left"><span style="font-size:12.8px">@evanleibovitch / </span>
<span style="font-size:12.8px">@el56</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>