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

Ted Lemon <mellon@fugue.com> Wed, 21 December 2016 15:50 UTC

Return-Path: <mellon@fugue.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 6310D129474 for <dnsop@ietfa.amsl.com>; Wed, 21 Dec 2016 07:50:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 TNKWfsjKjgyd for <dnsop@ietfa.amsl.com>; Wed, 21 Dec 2016 07:50:06 -0800 (PST)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20A871293F0 for <dnsop@ietf.org>; Wed, 21 Dec 2016 07:50:06 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id q68so85770353qki.1 for <dnsop@ietf.org>; Wed, 21 Dec 2016 07:50:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=w+aIi31mgV0nA2n5+XtPFwuBfDWdW053+AYbu+l+fH8=; b=PgT5O2pRGyj5dUowMRc7VuNjPlIytMOW1XlFgwkP/qHW7wsSjs0a+HSr54CuIJRhQq 3DRDgErHIragTlfsNKsoQSB6F5yBlw+PZNJXftfZz0qWeYc1oPB21oNbpxDCU97Pj65F PCZqbe0ELUpwKqRO4xm1tL1I1qoPbSu4tAnoD+eTeJ3ztVfct5UWmEYUwhqxuhK298/R Hby3V+wuZpk4uBuW41nsJNpblvh/Jb8Ns527sVVXAcTyaAqJGsfALJkL8i1q+bMfSitq zoON5VWLSr9b+K+RLr8rANZSjEQV/jub261x0fR3tcPTI2QghVcEHmQYrsWNllQcAv2P pvJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=w+aIi31mgV0nA2n5+XtPFwuBfDWdW053+AYbu+l+fH8=; b=FvLufmfXAXVJQ7FSZV3NhyRG4UKq8TuYWqEiElypn6JT8AlZgLu3ZGVHBwihLU5N7r fXLlzXpd9iMjqlwLzr4jT9C9CJqsx640X+a8BgYHhZF3bh1Oh8PmTKQ+6wZjOGjDL6Lx Ly5/k2XBYP/8zha02R6+7XpxoQ8fznD3fM+LJjkyWKw8UFmJO+pl+L30kGnBpLWC46FU CcxcrD9IPzLjC5VNohcFfzMIaxgc7uWvKC3ALaywh8QS3KW2UHgs2SMi/ioMNhMszCZU ALUqd4iPUMieFuYwzVKlVt9kfyY6pCvGV0NpNyaJBlsxw1ExXpkkQXrtrmBJfcdxe1Zd WnhA==
X-Gm-Message-State: AIkVDXL78lGLfu2vyX0O4R4EhphM3lV31dSdjWGEZv7Q85s5jWflvgFxQK9idrjI+UQ8fQ==
X-Received: by 10.55.40.85 with SMTP id o82mr5196920qkh.148.1482335405186; Wed, 21 Dec 2016 07:50:05 -0800 (PST)
Received: from [192.168.1.131] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id z7sm15781934qkz.7.2016.12.21.07.50.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Dec 2016 07:50:04 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <A407FBB2-96A8-4624-AFF8-0E2C46E2A357@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_076C6ECA-5AC5-4587-A6AB-F04B86ED9440"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 21 Dec 2016 10:50:02 -0500
In-Reply-To: <cf2f8970-10a4-15f7-6e96-7490fa983c02@bellis.me.uk>
To: Ray Bellis <ray@bellis.me.uk>
References: <20161218224231.GB16301@odin.ulthar.us> <201612191535.uBJFZh7w091898@calcite.rhyolite.com> <CACfw2hhFLdFgspse7-L8UxCLCCu_g=GYEybOWVZ5xPkMu0YduQ@mail.gmail.com> <CACfw2hg_8nT_b6Syc1-wk_O92mzW0Zo0wX5xgMp5uhhu0Vom9A@mail.gmail.com> <987B1C64-B85D-4316-8DE8-27D4A4AB8F9A@fugue.com> <cf2f8970-10a4-15f7-6e96-7490fa983c02@bellis.me.uk>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Si5zMvntTb0OXSNSCjnDtvY2Sz4>
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: Wed, 21 Dec 2016 15:50:07 -0000

On Dec 21, 2016, at 10:41 AM, Ray Bellis <ray@bellis.me.uk> wrote:
> RPZ is primarily used to protect end-users from visiting sites
> associated with malware, either because the A / AAAA result of a lookup
> resolves to a particular address, or because the NS set used to resolve
> the query shares resolvers with ones used by malevolent actors.
> 
> Those malevolent actors are just as capable of using DNSSEC.

Yes, but we don’t care.   The DNS infrastructure will still block queries to their zones; the difference will be that now the end node can _tell_ that the infrastructure blocked the queries.

Of course, some things you can do without DNSSEC you can’t do with DNSSEC.   You can’t send the browser to a _different_ web server.   This breaks some usage models, and would certainly cause my employer some pain.   I think that a transparent way of signaling that a zone has been blocked and signaling why it was blocked is worth doing as well.   But independent of that, if RPZ spurs further deployment of DNSSEC, I would consider that a win.