[CPWG] Google pushes .zip and .mov domains onto the Internet, and the Internet pushes back

Khaled Koubaa khaled.koubaa at gmail.com
Tue May 30 19:25:15 UTC 2023


I noticed that your first goal focuses on the future round of gTLDs, and
the second focuses on the .zip. Does this mean we shouldn't look at the
existing TLDs?
I said the focus should not be the .zip to avoid the risk of omitting the
other extension-TLDs - the risk associated with them - and not to diminish
the risk associated with .zip

Khaled

On Tue, May 30, 2023 at 7:41 PM Bill Jouris via CPWG <cpwg at icann.org> wrote:

> "The focus should not be on the ".zip" but on reducing the risk for end
> users. The solution could be at the browser level and the DNS level. "
>
> I disagree.  I think we should pursue two goals simultaneously:
>
> 1) modify the process for vetting new proposed gTLDs, so problems like
> this get stopped.  Maybe it's a new review.  Maybe it's just putting people
> on the review panel who are familiar enough with the online world to spot
> these sorts of issues immediately.
>
> 2) deal with .ZIP specifically.  I think the potential harm here is
> substantial enough that ICANN should explore rescinding it's approval.  At
> absolute minimum, the gTLD holder should be notified a) that we see an
> obvious risk here, and b) that by continuing to register .ZIP domains they
> are assuming any and all legal risks -- that is, any victims of DNS Abuse
> can sue them and have ICANN's explicit support (in addition to being able
> to cite the notification at trial).  In short, by registering a .ZIP domain
> they are complicit, and legally accessories before the fact.
>
> Bill Jouris
>
> Sent from Yahoo Mail on Android
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
>
> On Tue, May 30, 2023 at 5:49 AM, Khaled Koubaa via CPWG
> <cpwg at icann.org> wrote:
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> 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 (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). 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.
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> 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 (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/cpwg/attachments/20230530/5027bb17/attachment-0001.html>


More information about the CPWG mailing list