Re: [DNSOP] NSEC/NSEC3 for unsigned zones and aggressive use

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 20 July 2017 15:02 UTC

Return-Path: <bortzmeyer@nic.fr>
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 E5DBC131A56 for <dnsop@ietfa.amsl.com>; Thu, 20 Jul 2017 08:02:20 -0700 (PDT)
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 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 6AJ3gz--2UBc for <dnsop@ietfa.amsl.com>; Thu, 20 Jul 2017 08:02:07 -0700 (PDT)
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 A190E12EC46 for <dnsop@ietf.org>; Thu, 20 Jul 2017 08:02:07 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id C791E31CE6; Thu, 20 Jul 2017 17:02:04 +0200 (CEST)
Received: by godin (Postfix, from userid 1000) id DEDC9EC0B75; Thu, 20 Jul 2017 17:00:31 +0200 (CEST)
Date: Thu, 20 Jul 2017 17:00:31 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mukund Sivaraman <muks@isc.org>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, dnsop@ietf.org
Message-ID: <20170720150031.GA22702@laperouse.bortzmeyer.org>
References: <20170718094654.GA31988@jurassic> <6EE82876-6085-42FA-B2F1-850E9EAE6083@vpnc.org> <20170718125056.GA7982@jurassic>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170718125056.GA7982@jurassic>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ck5s6X3-Xt10_gjT1EOcNI5UtWM>
Subject: Re: [DNSOP] NSEC/NSEC3 for unsigned zones and aggressive use
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 20 Jul 2017 15:02:21 -0000

On Tue, Jul 18, 2017 at 06:20:56PM +0530,
 Mukund Sivaraman <muks@isc.org> wrote 
 a message of 27 lines which said:

> It is to put draft-ietf-dnsop-nsec-aggressiveuse to use with unsigned
> zones.

That's quite funny. During the development of RFC 8020
(draft-ietf-dnsop-nxdomain-cut), which addresses the same concern as
draft-ietf-dnsop-nsec-aggressiveuse, many people said that the feature
was dangerous, and we should mandate the use of DNSSEC. In the end, it
is not mandatory (see sections 2, 3rd para, and section 7 of RFC
8020).

draft-ietf-dnsop-nsec-aggressiveuse is more aggressive (because it can
now synthetizes answers) so it seems to me the same reasons should
apply?