Re: [DNSOP] Comments regarding the NSEC5

Paul Wouters <paul@nohats.ca> Wed, 11 March 2015 18:19 UTC

Return-Path: <paul@nohats.ca>
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 2451E1A1BAE for <dnsop@ietfa.amsl.com>; Wed, 11 Mar 2015 11:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] 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 sVQKGduNEyTA for <dnsop@ietfa.amsl.com>; Wed, 11 Mar 2015 11:19:00 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 678FE1A1AE6 for <dnsop@ietf.org>; Wed, 11 Mar 2015 11:19:00 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3l2M4H6zjFz6F; Wed, 11 Mar 2015 19:18:55 +0100 (CET)
Authentication-Results: mx.nohats.ca; dkim=pass reason="1024-bit key; unprotected key" header.d=nohats.ca header.i=@nohats.ca header.b=IFjskc6h; dkim-adsp=pass
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id rWqIXXiRy7r4; Wed, 11 Mar 2015 19:18:54 +0100 (CET)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 11 Mar 2015 19:18:54 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 07160803E0; Wed, 11 Mar 2015 14:18:53 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1426097934; bh=2qblHkplG8AEP2nKoBBX/GCtgJ7WsZ4BEpIzvldlurg=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=IFjskc6hq7+WqGAzPSwB+mnO+KmM1FfH9vLqdcpyVemzAf5r8oTUs7Goo0rJi4qpq zE3q9pP6mAjZPfgGuKdvnI9b8MLtnou7brwE4soB0fKDsX3sC68LkxA8djFJXhXr1m +jeV/MPiftGzytKzpb+7JD3J3iyYpGvZ25O2Phek=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id t2BIIrCI018594; Wed, 11 Mar 2015 14:18:53 -0400
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Wed, 11 Mar 2015 14:18:52 -0400
From: Paul Wouters <paul@nohats.ca>
To: Nicholas Weaver <nweaver@icsi.berkeley.edu>
In-Reply-To: <17FB96B6-B44C-4C9B-A68E-112C5EAE0CA3@icsi.berkeley.edu>
Message-ID: <alpine.LFD.2.10.1503111417400.23339@bofh.nohats.ca>
References: <55002098.5060709@redhat.com> <55006AF8.4090500@nic.cz> <55006D98.7000300@redhat.com> <55006FC7.1030206@nic.cz> <17FB96B6-B44C-4C9B-A68E-112C5EAE0CA3@icsi.berkeley.edu>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/R7FosL8OI6GCaB6gcsNbTkIrAJw>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Comments regarding the NSEC5
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: <http://www.ietf.org/mail-archive/web/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, 11 Mar 2015 18:19:02 -0000

On Wed, 11 Mar 2015, Nicholas Weaver wrote:

> Why not just do something simpler?  The only thing NSEC5 really differs in a way that counts is not in the NSEC record but really just the DNSKEY handling, having a separate key used for signing the NSEC* records.
>
> So why define NSEC5 at all.
>
>
> Instead, just specify a separate flag for the DNSKEY record, "NSEC-only", sign the NSEC3 dynamically, bada bing, bada boom, done!
>
>
> For old resolvers, they just ignore the flag and treat it like any other DNSKEY record, and since the valid names are signed with the other key, while the NSEC* are signed with this key, it works just fine.
>
> For upgraded resolvers, they follow the convention and only will accept RRSIGs for NSEC/NSEC3 with that DNSKEY record.
>
> And then on the authority side, you just dynamically generate and sign the NSEC3 record that says H(name)-1 to H(name)+1 has no valid record and sign that with the NSEC-only key.
>
>
>
> This way, you gain the protection against enumeration and the limited damage on key compromise property when validated by upgraded resolvers, and you still get the protection against enumeration when the resolver isn't upgraded, and you don't need to upgrade the resolver in order for this to be deployed.

I agree. Guess we would find out how much of a DDOS this dynamic signing
will be though :P

Paul