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

sthaug@nethelp.no Mon, 19 December 2016 11:18 UTC

Return-Path: <sthaug@nethelp.no>
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 62EA712954D for <dnsop@ietfa.amsl.com>; Mon, 19 Dec 2016 03:18:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1, SPF_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 qlLS2YC1Fo-g for <dnsop@ietfa.amsl.com>; Mon, 19 Dec 2016 03:18:44 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by ietfa.amsl.com (Postfix) with ESMTP id 67860129417 for <dnsop@ietf.org>; Mon, 19 Dec 2016 03:18:44 -0800 (PST)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 05ED0E6065; Mon, 19 Dec 2016 12:18:43 +0100 (CET)
Date: Mon, 19 Dec 2016 12:18:42 +0100
Message-Id: <20161219.121842.71115940.sthaug@nethelp.no>
To: ac@main.me
From: sthaug@nethelp.no
In-Reply-To: <20161219102758.21AB31294BC@ietfa.amsl.com>
References: <20161219095038.55A171295A9@ietfa.amsl.com> <20161219095931.GB25654@server.ds9a.nl> <20161219102758.21AB31294BC@ietfa.amsl.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/y7Np3ibAwUV-2CAXcS6KKW3huYc>
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: Mon, 19 Dec 2016 11:18:46 -0000

> To be clear and to boil it down: This draft publishes a method to supply
> different answers to different users and to hide the truth of those lies to 
> the same users.

So do for instance BIND views.

> Unless a registry, court or resource owner authorizes this, it is
> lying, cheating, "fraudy" and definately deceptive. (like a cockroach
> when exposed to light)

This is, ultimately, always a local decision.

In "my" network I have at times returned incorrect answers to queries
for <random>.domain - in order to mitigate the effects of "water
torture" attacks. Yes, this is definitely lying. The alternative is
to do nothing, and let the attack on the authoritative name servers
continue. I'm afraid your characterization above isn't going to change
this.

> I think that if people knew what we were talking about and
> truly understood the issues, there would be an uprising.

I think most people have little or no idea what DNS is about. However,
if they truly understood the issues, they would probably also understand
the need for RPZ.

Steinar Haug, AS2116