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:38 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 8E3C51B4292 for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 11:38:11 -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 wjwt9LXUy4Jm for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 11:38:09 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (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 46E231B4293 for <dnsop@ietf.org>; Fri, 13 Nov 2015 11:38:09 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 2F55A3BBB9; Fri, 13 Nov 2015 20:38:07 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id 9699A1907E4; Fri, 13 Nov 2015 20:33:57 +0100 (CET)
Date: Fri, 13 Nov 2015 20:33:57 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Wessels, Duane" <dwessels@verisign.com>
Message-ID: <20151113193357.GA29699@sources.org>
References: <20151106082238.GA2307@nic.fr> <A62EC834-C954-446C-9F7A-AB6D1F955C7F@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A62EC834-C954-446C-9F7A-AB6D1F955C7F@verisign.com>
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/8P8an3bN7Cxiad75NqG5lbsC-VU>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
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:38:11 -0000

On Wed, Nov 11, 2015 at 01:15:37AM +0000,
 Wessels, Duane <dwessels@verisign.com> wrote 
 a message of 107 lines which said:

> This updates RFC 2308 (Negative Caching of DNS Queries).  This would
> seem to be the key text from 2308 to update:

Yes, good catch, added to the online copy
<https://github.com/bortzmeyer/ietf-dnsop-nxdomain>

> I think its a little dangerous to say that an NXDOMAIN response
> SHOULD cause a cache to delete already cached "positive" data.
> Perhaps MAY is a better choice there.  Or SHOULD when DNSSEC
> validated, but MAY without.

Don't you think that the second paragraph of section 7 in -00 address
this concern? (My opinion is that this "attack" is nothing new and,
without DNSSEC, everything can be poisoned.)

v2.23.0 | Report a Bug | By Email