Re: [DNSOP] Key sizes was Re: I-D Action:draft-ietf-dnsop-rfc4641bis-01.txt

Joe Abley <jabley@hopcount.ca> Fri, 24 April 2009 23:52 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 578053A696E for <dnsop@core3.amsl.com>; Fri, 24 Apr 2009 16:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tM6tlfujjaHz for <dnsop@core3.amsl.com>; Fri, 24 Apr 2009 16:52:13 -0700 (PDT)
Received: from monster.hopcount.ca (monster.hopcount.ca [199.212.90.4]) by core3.amsl.com (Postfix) with ESMTP id 78F5A3A6876 for <dnsop@ietf.org>; Fri, 24 Apr 2009 16:52:13 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=monster; d=hopcount.ca; h=Received:Cc:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer; b=Z1GFC14xcERbSzy7HkqI2X3gDrXPG1vXeOtH+M/sdt8yCkvmMSfSRmpKz0YqSysdQ7vP+mrWyUJovXtkkdf9DNFo1JrstfNyciLt4wCEatSBS4/VZ1LvgnjgySeTvQaN;
Received: from [199.212.90.13] (helo=calamari.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1LxVCx-000Cdl-QN; Fri, 24 Apr 2009 23:53:28 +0000
Message-Id: <14F6B497-51D8-4719-B3C2-814A7D20940D@hopcount.ca>
From: Joe Abley <jabley@hopcount.ca>
To: Paul Wouters <paul@xelerance.com>
In-Reply-To: <alpine.LFD.1.10.0904241514300.28588@newtla.xelerance.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 24 Apr 2009 19:53:27 -0400
References: <49EDA81E.2000600@ca.afilias.info> <p06240807c613a658a056@[10.20.30.163]> <49EE276C.5070706@ca.afilias.info> <p06240814c613f23a6960@[10.20.30.163]> <49EEF042.3070109@ca.afilias.info> <alpine.LFD.1.10.0904221147060.7510@newtla.xelerance.com> <49EFA9C3.6090903@ca.afilias.info> <alpine.LFD.1.10.0904231142590.7788@newtla.xelerance.com> <alpine.LFD.1.10.0904241052270.26808@newtla.xelerance.com> <p06240813c61798e7e391@[10.20.30.158]> <20090424174722.GA30229@isc.org> <alpine.LFD.1.10.0904241514300.28588@newtla.xelerance.com>
X-Mailer: Apple Mail (2.930.3)
Cc: dnsop@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, Evan Hunt <Evan_Hunt@isc.org>, Shane Kerr <shane@ca.afilias.info>
Subject: Re: [DNSOP] Key sizes was Re: I-D Action:draft-ietf-dnsop-rfc4641bis-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 24 Apr 2009 23:52:14 -0000

On 24 Apr 2009, at 16:03, Paul Wouters wrote:

> I don't see a cryptographic reason for Paul Hoffman's "I'd like the  
> keys to
> be of equal size". Unless you'd argue that the KSK could easilly  
> also be
> 1024bit, and that the additional 11 months of validity of the KSK is
> negligable compared to the time now upto 3 years from now, to break  
> a 1024
> bit RSA key.

What benefit is there of keeping the KSK small (e.g. 1024 bits)  
instead of just choosing the maximum that your signing software  
permits (e.g. 4096 bits, I think, with dnssec-signzone)?

EDNS0 is a prerequisite for DNSSEC, if memory serves, so it's  
presumably not TCP fallback we're worried about with larger DNSKEY  
RDATA. A 4096 bit key only represents 384 more bytes of RDATA in a  
DNSKEY resource record on the wire than a 1024 bit key, and 384 bytes  
doesn't sound (naively, no science) like it's going to break the bank.

Is the root concern the computational expense of dealing with larger  
keys in a validator? Or something else? Whatever the root concern is,  
what are the boundaries?

It seems fruitless to debate whether 1024 bits is sufficient if  
there's no real cost to just choosing (say) 4096 bits and avoiding the  
discussion.


Joe