Re: [DNSOP] I-D Action: draft-vixie-dns-rpz-04.txt

Tony Finch <dot@dotat.at> Thu, 22 December 2016 11:18 UTC

Return-Path: <dot@dotat.at>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D22129543 for <dnsop@ietfa.amsl.com>; Thu, 22 Dec 2016 03:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g3kLV9e1mOmE for <dnsop@ietfa.amsl.com>; Thu, 22 Dec 2016 03:18:39 -0800 (PST)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [131.111.8.133]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA2C129534 for <dnsop@ietf.org>; Thu, 22 Dec 2016 03:18:39 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:39481) by ppsw-33.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1cK1OP-000uBi-ii (Exim 4.86_36-e07b163) (return-path <dot@dotat.at>); Thu, 22 Dec 2016 11:18:37 +0000
Date: Thu, 22 Dec 2016 11:18:37 +0000
From: Tony Finch <dot@dotat.at>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20161221211918.zpo23oxt5iduhv6y@nic.fr>
Message-ID: <alpine.DEB.2.11.1612221100040.7102@grey.csi.cam.ac.uk>
References: <20161219.101111.41661466.sthaug@nethelp.no> <20161219092509.0DBA5129452@ietfa.amsl.com> <20161219093846.GA25654@server.ds9a.nl> <20161221211918.zpo23oxt5iduhv6y@nic.fr>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/l3r9UwYW7kls6ucyhrXWpbWFj1w>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-vixie-dns-rpz-04.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2016 11:18:41 -0000

Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>
> No, blocking a communication is harsh but is not a lie. Returning HTTP
> code 451 (RFC 7725) is not a lie, the HTTP server clearly says "this
> is censored".
>
> In the case of the DNS, in the absence of a rcode equivalent to 451,
> modifying the answers of the authoritative name servers is a lie. But
> some are more or less serious lies: [snip]

I think it's wrong to look at this only from the point of view of protocol
signalling without taking into account the wider context.

For example, a web server can return a 451 response whose content conceals
from the end user that any censorship has occurred - the browser won't
make the HTTP status code clear. (For a non-malicious example, try
spotting the 404 on Wikipedia's "not found" page.)

In an RPZ deployment, if the substitute IP address is a hosts a web site
that explains the reason for the block, the admin is not trying to conceal
anything or mislead anyone, so it isn't a lie.

Protocol signalling can help, but it is a relatively trivial matter
compared to how the blocking technology is explained to the people who are
affected by it.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
Lundy, Fastnet: West backing southwest later, 5 or 6, increasing 7, perhaps
gale 8 later. Rough or very rough. Showers. Good.