Should ISP block child pornography?

Fri Dec 7 14:57:17 UTC 2018

I block stuff all the time (like ROKSO's DROP list). The only issue with 
blocking domains of CPE is I imagine those domains change all the time 
as they get shutdown, if you block the IP (from domain lookup) its 
likely that IP maybe be legitimate in the future.

It should be stopped it at the DNS level, but even that has workarounds. 
I would think CPE is a violation of terms of "most" registrars.

-John

On 12/7/18 1:06 AM, Lotia, Pratik M wrote:
>
> Hello all, was curious to know the community’s opinion on whether an 
> ISP should block domains hosting CPE (child pornography exploitation) 
> content? Interpol has a ‘worst-of’ list which contains such domains 
> and it wants ISPs to block it.
>
> On one side we want the ISP to not do any kind of censorship or 
> inspection of customer traffic (customers are paying for pipes – not 
> for filtered pipes), on the other side morals/ethics come into play. 
> Keep in mind that if an ISP is blocking it would mean that it is also 
> logging the information (source IP) and law agencies might be wanting 
> access to it.
>
> Wondering if any operator is actively doing it or has ever considered 
> doing it?
>
> Thanks.
>
> With Gratitude,
>
> **
>
> *Pratik Lotia*
>
> “Information is not knowledge.”
>
> The contents of this e-mail message and
> any attachments are intended solely for the
> addressee(s) and may contain confidential
> and/or legally privileged information. If you
> are not the intended recipient of this message
> or if this message has been addressed to you
> in error, please immediately alert the sender
> by reply e-mail and then delete this message
> and any attachments. If you are not the
> intended recipient, you are notified that
> any use, dissemination, distribution, copying,
> or storage of this message or any attachment
> is strictly prohibited. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20181207/2138603c/attachment.html>