<div dir="ltr"><div dir="ltr"><a href="https://circleid.com/posts/20230627-alleviating-the-risks-.zip-and-similar-domain-extensions-could-pose-via-dns-intelligence">https://circleid.com/posts/20230627-alleviating-the-risks-.zip-and-similar-domain-extensions-could-pose-via-dns-intelligence</a></div><div dir="ltr"><br></div><div dir="ltr">An interesting article on .zip and other similarly confusing gTLDs .(app, .cab, .cam, .mobi, .mov, .pub, .rip, and .win cited) from a DNS Abuse point of view.<br clear="all"><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><br><font color="#000000">Kind regards,</font><br><font color="#000000">Justine</font><br><b><br></b></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 31 May 2023 at 13:56, Greg Shatan [NARALO] <<a href="mailto:gregshatanalac@gmail.com">gregshatanalac@gmail.com</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 dir="ltr"><div style="font-family:verdana,sans-serif">There are not many ICANN-related issues that break through to the general consciousness and mainstream media. The attempted sale of .ORG was one such issue.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">.ZIP (specifically) is another such issue. I have seen it now mentioned on TV news. I have also seen a large global financial institution issue a warning about .zip to employees and vendors, even while noting the gTLD's existence is "above board."</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">It is true that .zip is not unique in the type of risk it might pose.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">However, I think it is fair to consider .zip a highly malignant variation on this type of risk, with some special features. "Zip files" are sent by email all day every day by general business and non-business users. Indeed, they exist to be sent by email. ".io files" do not fit the same profile (and .io is a ccTLD, which changes the analysis as well).</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">While this might be an opportunity to educate end-users about the existence of the larger problem, the .zip problem cannot be treated as merely one of many.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Greg</div><div style="font-family:verdana,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 30, 2023 at 9:21 PM Justine Chew via CPWG <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@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 dir="ltr">Maria, <br><br>Carlton is correct. In the 2012 round, there was a Top-Level Reserved Names List which contained strings that were not allowed, these were mainly associated with ICANN-related entities and functions as well as some "well-known technical words":<div><br></div><div>AFRINIC ALAC APNIC ARIN ASO CCNSO EXAMPLE GAC GNSO GTLD-SERVERS IAB IANA IANA-SERVERS ICANN IESG IETF<br>INTERNIC INVALID IRTF ISTF LACNIC LOCAL LOCALHOST NIC NRO RFC-EDITOR RIPE ROOT-SERVERS RSSAC SSAC TEST <br>TLD WHOIS WWW</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature"><div dir="ltr">For the next round, the ICANN Board has already approved a SubPro PDP recommendation to add PTI to the above list.<br><br><font color="#000000">Justine</font><br><b><br></b></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 31 May 2023 at 07:18, Carlton Samuels via CPWG <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@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 dir="ltr"><div style="font-family:tahoma,sans-serif">Hi Maria,</div><div style="font-family:tahoma,sans-serif">Not sure if forbidden is the right label here but in the old rules - this would be like the 2012 round of gTLD - each TLD had a list of reserved names, meaning those that could not be in the trade. If memory serves, those were listed in the RA.</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">At the top level, there are reserved strings that may not be delegated and those were listed. Well, almost all of them anyways; .internet itself was an outlier.</div><div style="font-family:tahoma,sans-serif"><br></div><div style="font-family:tahoma,sans-serif">Carlton</div><div style="font-family:tahoma,sans-serif;font-size:large"><br></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>==============================<br><i><font face="comic sans ms, sans-serif">Carlton A Samuels</font></i><br><font face="comic sans ms, sans-serif"><i>Mobile: 876-818-1799<br><font color="#33CC00">Strategy, Process, Governance, Assessment & Turnaround</font></i></font><br>=============================</div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 30 May 2023 at 17:53, Maria A via CPWG <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@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 dir="auto"><div>Hi everyone,<div dir="auto"><br></div><div dir="auto">Sorry my view might not be too informed - but what is even Google's rationale to pushing these?</div><div dir="auto"><br></div><div dir="auto">Also isn't there some sort of black list of forbidden domains? </div><div dir="auto"><br></div>Thank you, </div><div dir="auto">Maria<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, May 30, 2023, 11:09 PM Jonathan Zuck via CPWG <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@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 lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11pt">Chantelle,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Let’s find some time on the next CPWG call to discuss this situation. This might result in a discussion of advice or in a discussion of correspondence to the SSAC. Let’s get it on the agenda. Thanks.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Jonathan<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-bottom:12pt"><b><span style="font-size:12pt;color:black">From:
</span></b><span style="font-size:12pt;color:black">CPWG <<a href="mailto:cpwg-bounces@icann.org" rel="noreferrer" target="_blank">cpwg-bounces@icann.org</a>> on behalf of Bill Jouris via CPWG <<a href="mailto:cpwg@icann.org" rel="noreferrer" target="_blank">cpwg@icann.org</a>><br>
<b>Date: </b>Tuesday, May 30, 2023 at 4:26 PM<br>
<b>To: </b><a href="mailto:cpwg@icann.org" rel="noreferrer" target="_blank">cpwg@icann.org</a> <<a href="mailto:cpwg@icann.org" rel="noreferrer" target="_blank">cpwg@icann.org</a>><br>
<b>Subject: </b>Re: [CPWG] Google pushes .zip and .mov domains onto the Internet, and the Internet pushes back<u></u><u></u></span></p>
</div>
<div>
<div id="m_6641776995095320754m_-6886733794447399398m_-8320818553776624309m_2351267671745695786m_-8826341886458441301ydpfce2c7c3yiv9402732203">
<div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Helvetica Neue"">I apologize for misunderstanding your point. Indeed we should look at other existing gTLDs as well. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Helvetica Neue""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Helvetica Neue"">But .ZIP is something that we already know about, and thus can act on immediately. Plus, as we do so, we create a process for dealing with other problematic existing gTLDs as
we discover them. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Helvetica Neue""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="font-size:12pt;font-family:"Helvetica Neue"">Bill Jouris<u></u><u></u></span></p>
<div id="m_6641776995095320754m_-6886733794447399398m_-8320818553776624309m_2351267671745695786m_-8826341886458441301ydpfce2c7c3yiv9402732203ymail_android_signature">
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Helvetica Neue""><a href="https://mail.onelink.me/107872968?pid=nativeplacement&c=Global_Acquisition_YMktg_315_Internal_EmailSignature&af_sub1=Acquisition&af_sub2=Global_YMktg&af_sub3=&af_sub4=100000604&af_sub5=EmailSignature__Static_" rel="noreferrer" target="_blank">Sent
from Yahoo Mail on Android</a><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Helvetica Neue""><u></u> <u></u></span></p>
<blockquote style="margin-left:0in;margin-right:0in;margin-bottom:15pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:Roboto;color:rgb(109,0,246)">On Tue, May 30, 2023 at 12:25 PM, Khaled Koubaa via CPWG<u></u><u></u></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<div id="m_6641776995095320754m_-6886733794447399398m_-8320818553776624309m_2351267671745695786m_-8826341886458441301yiv9402732203yqtfd17574">
<div>
<p class="MsoNormal"><span style="font-size:11pt"><<a href="mailto:cpwg@icann.org" rel="noreferrer" target="_blank">cpwg@icann.org</a>> wrote:<u></u><u></u></span></p>
</div>
</div>
<div id="m_6641776995095320754m_-6886733794447399398m_-8320818553776624309m_2351267671745695786m_-8826341886458441301yiv9402732203yqtfd14198">
<div style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(109,0,246);padding:0in 0in 0in 15pt;margin-top:7.5pt">
<p class="MsoNormal"><span style="font-size:11pt">_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" rel="noreferrer" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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.
<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" rel="noreferrer" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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 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 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.</blockquote></div></div></div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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.</blockquote></div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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.</blockquote></div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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.</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><font face="BlinkMacSystemFont, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif" color="#0b5394"><b>Greg Shatan</b></font><div><font face="BlinkMacSystemFont, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif" color="#0b5394"><b>Chair, NARALO</b></font></div></div></div>
</blockquote></div></div>