Re: [DNSOP] DNSOP Call for Adoption draft-vixie-dns-rpz

"John Levine" <johnl@taugh.com> Thu, 22 December 2016 15:32 UTC

Return-Path: <johnl@taugh.com>
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 3DED712955C for <dnsop@ietfa.amsl.com>; Thu, 22 Dec 2016 07:32:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 vxDMGGtelEHj for <dnsop@ietfa.amsl.com>; Thu, 22 Dec 2016 07:32:36 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADB98127A91 for <dnsop@ietf.org>; Thu, 22 Dec 2016 07:32:35 -0800 (PST)
Received: (qmail 43212 invoked from network); 22 Dec 2016 15:32:40 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 22 Dec 2016 15:32:40 -0000
Date: 22 Dec 2016 15:32:12 -0000
Message-ID: <20161222153212.4649.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <f6207950-0fc4-2b06-ecac-df8f267527fd@blipp.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/nb99UdbTnNwK2TCCgrkbRr23aLI>
Subject: Re: [DNSOP] DNSOP Call for Adoption draft-vixie-dns-rpz
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 15:32:37 -0000

>Even shorter, RPZ might be a good tool, but definitely not something
>that the IETF should promote in any way without a big enough warning
>sign that there are dragons lying around.

Assuming we published such a warning, can you tell us whose behavior
that warning might change, how the behavior would change, and why?

I have to say I'm baffled at arguments that boil down to "someone
might do something bad with this, so we'll pretend it doesn't exist."
By that standard, we wouldn't have published DNS, TCP, or IP.

R's,
John

PS: I am reminded of the era of US prohibition when bottles of grape
juice and packets of yeast were sold with with a label WARNING: DO NOT
ADD YEAST TO JUICE AND PUT IN A WARM PLACE FOR SEVERAL DAYS BECAUSE AN
ALCOHOLIC BEVERAGE WILL RESULT.