[gnso-rds-pdp-wg] Dangers of public whois

[Greg Shatan]

Rob,

Thankfully, that's not what's being proposed (nor is it current practice).

Those of us who track down stolen, pirated, bootleg, or otherwise
infringing copyrighted materials on the web don't want to send anything to
or through ICANN.  They just need to find and contact the registrant and/or
the hosting provider and/or the registrar and/or the registry in order to
deal with them directly.  Since its inception, Whois has been instrumental
in doing so.

But nothing gets sent "to or through" ICANN. ICANN never sees infringing
content, is not aware of any infringing content, is not aware that any
particular copyright is being infringed, and is not aware that any possible
infringement is being investigated.

Greg


On Fri, Feb 24, 2017 at 4:45 PM Rob Golding <rob.golding at astutium.com>
wrote:

> From ICANN's LinkedIn Page ...
> =
> ICANN doesn’t control content on the Internet.
> It cannot stop spam
> and it doesn’t deal with access to the Internet.
> =
>
> Seems fairly clear to me that an allegation about copyright infringement
> on a webpage shouldn't be sent to or through icann (unless the entirety of
> the next Harry Potter book is a bit short and can fit inside the 63
> character limits of a domain name)
>
> Rob
>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg

-- 


*Greg Shatan *C: 917-816-6428
S: gsshatan
Phone-to-Skype: 646-845-9428
gregshatanipc at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170224/8fc73de8/attachment.html>