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

Shane Kerr <shane@ca.afilias.info> Wed, 22 April 2009 23:34 UTC

Return-Path: <shane@ca.afilias.info>
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 1374A3A69BD for <dnsop@core3.amsl.com>; Wed, 22 Apr 2009 16:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.58
X-Spam-Level:
X-Spam-Status: No, score=-5.58 tagged_above=-999 required=5 tests=[AWL=0.685, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 I6ugiNhV68MX for <dnsop@core3.amsl.com>; Wed, 22 Apr 2009 16:34:19 -0700 (PDT)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id 596F93A6979 for <dnsop@ietf.org>; Wed, 22 Apr 2009 16:34:19 -0700 (PDT)
Message-ID: <49EFA9C3.6090903@ca.afilias.info>
Date: Thu, 23 Apr 2009 01:35:31 +0200
From: Shane Kerr <shane@ca.afilias.info>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Paul Wouters <paul@xelerance.com>
References: <20090306141501.4BA2F3A6B4B@core3.amsl.com> <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>
In-Reply-To: <alpine.LFD.1.10.0904221147060.7510@newtla.xelerance.com>
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Authenticated: True
Cc: dnsop@ietf.org
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: Wed, 22 Apr 2009 23:34:20 -0000

Paul,

Paul Wouters wrote:
> On Wed, 22 Apr 2009, Shane Kerr wrote:
> 
>> I don't think this is a waste, really. I think if we recommend 1024 as
>> the text does, then we'll have to revisit it in 3 or 4 years.
> 
> Is this for ZSK or KSK? Because if you pick equal sizes, then both would be
> equally vulnerable to the same brute force attack, and often cycling a
> ZSK of
> equal size to the KSK key does not make much sense - the attackers would
> just ignore the ZSK and go for the KSK instead. So using a 2048 ZSK sort
> of implies using a larger KSK. Unless you keep the ZSK for 6 months or so.

Good point. I was only ever considering KSK key length.

I kind of assume everyone will use automated ZSK rolling, and that ZSK
will get rolled fairly frequently, so shorter keys make sense.

--
Shane