<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Indeed. And as Ross pointed it, I can't see the real benefits of
such a TLD but I do see the risks it brings!<br>
<pre class="moz-signature" cols="72">Louis Houle</pre>
<div class="moz-cite-prefix">Le 2023-05-28 à 20:12, Jonathan Zuck
via NA-Discuss a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:SJ0PR08MB7652FE37F45224DDF457BC4EB64A9@SJ0PR08MB7652.namprd08.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Certainly seems worthwhile to me and outweighs the value of having
a .zip domain
<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"><a class="moz-txt-link-abbreviated" href="http://www.InnovatorsNetwork.org">www.InnovatorsNetwork.org</a></div>
<div dir="auto"><br>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b> Evan
Leibovitch <a class="moz-txt-link-rfc2396E" href="mailto:evan@telly.org"><evan@telly.org></a><br>
<b>Sent:</b> Sunday, May 28, 2023 8:09:11 PM<br>
<b>To:</b> Jonathan Zuck <a class="moz-txt-link-rfc2396E" href="mailto:JZuck@innovatorsnetwork.org"><JZuck@innovatorsnetwork.org></a><br>
<b>Cc:</b> NARALO Discussion List
<a class="moz-txt-link-rfc2396E" href="mailto:na-discuss@atlarge-lists.icann.org"><na-discuss@atlarge-lists.icann.org></a><br>
<b>Subject:</b> Re: [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">
Very likely the name collision assessment came up clean --
against other domains.</div>
<div class="x_gmail_default"
style="font-family:tahoma,sans-serif; color:#0b5394">
But that's not the issue here.</div>
<div class="x_gmail_default"
style="font-family:tahoma,sans-serif; color:#0b5394">
Is there any requirement for applicants to do due diligence
regarding collisions with other common non-DNS computer uses
of the applied string?</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">
There are some precedents, notably dot-onion being
unavailable to reduce collision with the TOR network (which
is certainly out of ICANN's jurisdiction).<br>
</div>
<div class="x_gmail_default"
style="font-family:tahoma,sans-serif; color:#0b5394">
But I don't know if, for instance, there would be any
inherent ICANN-based opposition to anyone applying for, say,
dot-exe or dot-bat (which, like zip, is also a dictionary
word).</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">
Perhaps there is room to develop advice to have a mechanism
that measures evaluates conflict not just with other
domains, but also common computer uses that could if
implemented cause pubic confusion or harm.<br>
</div>
<div class="x_gmail_default"
style="font-family:tahoma,sans-serif; color:#0b5394">
There are a LOT of file extensions and not all need to be
protected, but surely the most common file extensions (and
perhaps also command-line utilities) need protections.</div>
<div class="x_gmail_default"
style="font-family:tahoma,sans-serif; color:#0b5394">
I see that dot-run is delegated, which could affect Linux
systems (which run a lot of the Internet's infrastructure).</div>
<div class="x_gmail_default"
style="font-family:tahoma,sans-serif; color:#0b5394">
So is dot-mov which is a popular Apple file extension for
videos.<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">
Anyway, I leave it with NARALO's ALAC reps to determine if
this issue is sufficiently end-user to care about and
investigate.<br>
</div>
<div class="x_gmail_default"
style="font-family:tahoma,sans-serif; color:#0b5394">
<br clear="all">
</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>
<br>
</div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Sun, May 28, 2023 at
7:35 PM Jonathan Zuck <<a
href="mailto:JZuck@innovatorsnetwork.org"
moz-do-not-send="true" class="moz-txt-link-freetext">JZuck@innovatorsnetwork.org</a>>
wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px
0.8ex; border-left:1px solid rgb(204,204,204);
padding-left:1ex">
<div>
<div dir="auto">I wonder what sort of risk assessment .ZIP
has for the name collision study.</div>
<div
id="x_m_864610406444416246ms-outlook-mobile-signature"
dir="auto">
<div><br>
</div>
<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"><a
href="http://www.InnovatorsNetwork.org"
target="_blank" moz-do-not-send="true">www.InnovatorsNetwork.org</a></div>
<div dir="auto"><br>
</div>
</div>
<hr style="display:inline-block; width:98%">
<div id="x_m_864610406444416246divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" face="Calibri, sans-serif"
color="#000000"><b>From:</b> NA-Discuss <<a
href="mailto:na-discuss-bounces@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">na-discuss-bounces@atlarge-lists.icann.org</a>>
on behalf of Evan Leibovitch via NA-Discuss <<a
href="mailto:na-discuss@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">na-discuss@atlarge-lists.icann.org</a>><br>
<b>Sent:</b> Saturday, May 27, 2023 4:18:34 PM<br>
<b>To:</b> NARALO Discussion List <<a
href="mailto:na-discuss@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">na-discuss@atlarge-lists.icann.org</a>><br>
<b>Subject:</b> [NA-Discuss] Protecting the public
interest: dot-zip</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)">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 style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)"><br>
</div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)">Now anyone can buy a dot-zip
second-level domain, ie evan.zip or naralo.zip<br>
</div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)"><br>
</div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)">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 style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)"><br>
</div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)">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 style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)"><br>
</div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)">Here are two videos that
explain the situation well:<br>
<a
href="https://www.youtube.com/watch?v=GCVJsz7EODA"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.youtube.com/watch?v=GCVJsz7EODA</a><br>
<a
href="https://www.youtube.com/watch?v=V82lHNsSPww"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.youtube.com/watch?v=V82lHNsSPww</a></div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)"><br>
</div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)">Is anyone in domain-world
looking at this?</div>
<div style="font-family:tahoma,sans-serif;
color:rgb(11,83,148)"><br>
</div>
<div>
<div dir="ltr">
<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>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">------
NA-Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NA-Discuss@atlarge-lists.icann.org">NA-Discuss@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/na-discuss">https://atlarge-lists.icann.org/mailman/listinfo/na-discuss</a>
Visit the NARALO online at <a class="moz-txt-link-freetext" href="http://www.naralo.org">http://www.naralo.org</a>
------
_______________________________________________
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 class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">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.</pre>
</blockquote>
<br>
</body>
</html>