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

Mukund Sivaraman <muks@isc.org> Tue, 18 July 2017 12:51 UTC

Return-Path: <muks@isc.org>
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 C872012EC46 for <dnsop@ietfa.amsl.com>; Tue, 18 Jul 2017 05:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.265
X-Spam-Level:
X-Spam-Status: No, score=0.265 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SORBS_WEB=1.5, SPF_SOFTFAIL=0.665] autolearn=no 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 r4tyFhGmOe1h for <dnsop@ietfa.amsl.com>; Tue, 18 Jul 2017 05:51:01 -0700 (PDT)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 07B0B129B10 for <dnsop@ietf.org>; Tue, 18 Jul 2017 05:51:01 -0700 (PDT)
Received: from jurassic (unknown [115.118.30.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id 7349656A04AF; Tue, 18 Jul 2017 12:50:58 +0000 (GMT)
Date: Tue, 18 Jul 2017 18:20:56 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: dnsop@ietf.org
Message-ID: <20170718125056.GA7982@jurassic>
References: <20170718094654.GA31988@jurassic> <6EE82876-6085-42FA-B2F1-850E9EAE6083@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6EE82876-6085-42FA-B2F1-850E9EAE6083@vpnc.org>
User-Agent: Mutt/1.8.3 (2017-05-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/miUQyE_CVrzzLlUVcEj1FBLJSa0>
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: Tue, 18 Jul 2017 12:51:02 -0000

Hi Paul

On Tue, Jul 18, 2017 at 02:35:31PM +0200, Paul Hoffman wrote:
> On 18 Jul 2017, at 11:46, Mukund Sivaraman wrote:
> 
> > Will you give some thought and reply with your opinion on NSEC/NSEC3 for
> > unsigned zones requiring the DNS COOKIE option in transmission, that can
> > be used with draft-ietf-dnsop-nsec-aggressiveuse?
> 
> Of what value is the result? Is it worth the hassle for the zone admin?

It is to put draft-ietf-dnsop-nsec-aggressiveuse to use with unsigned
zones. A zone admin would not have to do anything operationally except
enable/disable the feature.

Dealing with water torture and some other attacks have had several
band-aid approaches that don't always work well in practice. The most
promising (and what feels correct) is
draft-ietf-dnsop-nsec-aggressiveuse, but it doesn't work for unsigned
zones.

		Mukund