Re: [DNSOP] Comments regarding the NSEC5

Jan Včelák <jan.vcelak@nic.cz> Thu, 12 March 2015 10:36 UTC

Return-Path: <jan.vcelak@nic.cz>
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 C66091A914C for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 03:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.361
X-Spam-Level:
X-Spam-Status: No, score=-0.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 d_3xU0-08QZu for <dnsop@ietfa.amsl.com>; Thu, 12 Mar 2015 03:36:23 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E05AE1A9144 for <dnsop@ietf.org>; Thu, 12 Mar 2015 03:36:22 -0700 (PDT)
Received: from pc-cznic4.localnet (unknown [IPv6:2001:67c:1220:80c:2a92:4aff:feca:f18d]) by mail.nic.cz (Postfix) with ESMTPSA id BAC0213F74A; Thu, 12 Mar 2015 11:36:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1426156580; bh=LMzqwv0VXYEcP8b0QVqCo0XthUHJSs/vj7GpEUeqCs0=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=Va6YbK3RX+ai5yN/DzZfyIJcrXe4ZsR+GTPgc9fl4YpsPCWsOcyvz7GgUdMIAznfn fsVNcjOHH7xKQ5tehgJvA0cxZ4k/epgP3lTq6jnet0Q9DPx50gq7LK0lk4UiPVl+l1 hdQSlCYuipUF1G2MzUEcWP0LrMfaqvl2kDT4I5j8=
From: Jan Včelák <jan.vcelak@nic.cz>
To: Florian Weimer <fweimer@redhat.com>
Date: Thu, 12 Mar 2015 11:36:20 +0100
Message-ID: <5418135.fhyjAyNSf0@pc-cznic4>
Organization: CZ.NIC Labs
User-Agent: KMail/4.14.4 (Linux/4.0.0-0.rc2.git0.1.fc22.x86_64; KDE/4.14.6; x86_64; ; )
In-Reply-To: <55016B09.8080106@redhat.com>
References: <55002098.5060709@redhat.com> <3070134.2yIek5FY2o@pc-cznic4> <55016B09.8080106@redhat.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Virus-Scanned: clamav-milter 0.98.6 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/UHbFolYigt-okDbiA03da0ikJhs>
Cc: dnsop@ietf.org, Nicholas Weaver <nweaver@icsi.berkeley.edu>
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: Thu, 12 Mar 2015 10:36:23 -0000

On Thursday, March 12, 2015 11:31:37 AM Florian Weimer wrote:
> On 03/12/2015 11:15 AM, Jan Včelák wrote:
> > On Wednesday, March 11, 2015 09:52:55 AM 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!
> > 
> > This would not work. Anyone holding the NSEC-only private key could fake
> > denying answers for the zone. So if your zone is slaved by a less-trusted
> > party, they could still manipulate your zone. This is not possible with
> > NSEC5.
> They can still respond with SERVFAIL instead of supplying a signed
> answer, achieving roughly the same result.
> 
> A better argument would be support for opt out, where signatures from
> the online key could introduce unauthorized positive answers.  It's
> still not a very strong argument, admittedly.  The DNS software itself
> is likely signed by a key which is kept online (more or less).  Online
> keys are less threatening than they used to be, and we aren't even
> talking about long-term keys baked into software, but short/medium-term
> keys which are easily replaced.
> 
> And does anyone actually use opt out with NSEC3?

Yes, .com for example. My impression was that Opt-Out was the selling point of 
NSEC3, not the domain name hashing.