RPZ & content control

[McTim]

Milton,

On Thu, Apr 13, 2017 at 11:08 AM, Mueller, Milton L <milton at gatech.edu> wrote:
>
>
>> -----Original Message-----
>>
>> Great you're following this. I think the design of a system can have some
>> properties that makes is harder or easier to infringe on rights.
>
> I don't. Rights are not technical protocols, they are legal, political and societal constructs. A technical protocol tells you how to block a domain; it is very difficult , probably impossible, for a protocol to dictate _why_ you block a domain.
>
>> To make the
>> analogy to spam: when I receive spam in my spamfolder, I can still read it.
>> Spam that is blocked, I cannot read.
>
> That's an analogy. But RPZ is not a spam filter. As McTim pointed out, the whole purpose of RPZ is to block domains, not to set them aside


To be more pedantic, I would say that the point of RPZ is to allow you
to drop packets BEFORE they hit your recursive server.  This allows
the server operator to define what is "crufty".

Shane is much more of a Vixie-crat, so he can be more descriptive if needed.

-- 
Cheers,

McTim
"A name indicates what we seek. An address indicates where it is. A
route indicates how we get there."  Jon Postel