IETF Logo Mail Archive

Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dnsop-nxdomain-cut-00.txt]

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 13 November 2015 19:48 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E8BD1B2B58 for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 11:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 SC9aTYy1P0Ap for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 11:48:08 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 097FD1B2B55 for <dnsop@ietf.org>; Fri, 13 Nov 2015 11:48:08 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 85E5B3BBB9; Fri, 13 Nov 2015 20:48:06 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id 04DCC1907E4; Fri, 13 Nov 2015 20:46:15 +0100 (CET)
Date: Fri, 13 Nov 2015 20:46:15 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20151113194615.GA32106@sources.org>
References: <20151106082238.GA2307@nic.fr> <A62EC834-C954-446C-9F7A-AB6D1F955C7F@verisign.com> <20151112081514.GA16017@laperouse.bortzmeyer.org> <75FCA3C3-A9F3-4C85-BB45-27DD927210E1@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <75FCA3C3-A9F3-4C85-BB45-27DD927210E1@vpnc.org>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 8.2
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/x1mULrNAXihjeYR_f1fmEwRB20A>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>, "Wessels, Duane" <dwessels@verisign.com>
Subject: Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dnsop-nxdomain-cut-00.txt]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 13 Nov 2015 19:48:09 -0000

On Thu, Nov 12, 2015 at 09:54:42AM -0800,
 Paul Hoffman <paul.hoffman@vpnc.org> wrote 
 a message of 43 lines which said:

> If the NXDOMAIN response is not signed, it allows an attacker to
> block resolution of a name that was good, yes?

I do not see why it's new: without DNSSEC, a resolver can be poisoned,
"NXDOMAIN cut" or not. It is the case today.

[The only new thing is the possibility to deny existence of not just a
name but an entire subtree. Again, the solution is to use DNSSEC.]

v2.23.0 | Report a Bug | By Email