Re: [dnsext] historal root keys for upgrade path?

Florian Weimer <fweimer@bfk.de> Fri, 28 January 2011 08:18 UTC

Return-Path: <fweimer@bfk.de>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB8E828C0ED for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 00:18:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.158
X-Spam-Level:
X-Spam-Status: No, score=-2.158 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 aW8cY6LyEatt for <dnsext@core3.amsl.com>; Fri, 28 Jan 2011 00:18:22 -0800 (PST)
Received: from mx01.bfk.de (mx01.bfk.de [193.227.124.2]) by core3.amsl.com (Postfix) with ESMTP id 6FB563A6BF6 for <dnsext@ietf.org>; Fri, 28 Jan 2011 00:18:22 -0800 (PST)
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1Pija8-0006Bv-Kn; Fri, 28 Jan 2011 08:21:24 +0000
Received: by bfk.de with local id 1Pija8-0003rQ-Hl; Fri, 28 Jan 2011 08:21:24 +0000
To: Joe Abley <jabley@hopcount.ca>
References: <alpine.LFD.1.10.1101251250040.30991@newtla.xelerance.com> <4D3F233C.7000900@vpnc.org> <CAB4A416-148B-435E-A1BB-78035A1D539D@kirei.se> <alpine.LFD.1.10.1101271036560.19497@newtla.xelerance.com> <10A3D861-EC02-49FF-BBD1-44843378C9CB@icsi.berkeley.edu> <2BC28AF0-9132-4FFD-9FA6-FCEC29A1D471@hopcount.ca>
From: Florian Weimer <fweimer@bfk.de>
Date: Fri, 28 Jan 2011 08:21:24 +0000
In-Reply-To: <2BC28AF0-9132-4FFD-9FA6-FCEC29A1D471@hopcount.ca> (Joe Abley's message of "Thu\, 27 Jan 2011 13\:28\:26 -0500")
Message-ID: <82aailmoaj.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>, dnsext@ietf.org
Subject: Re: [dnsext] historal root keys for upgrade path?
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2011 08:18:23 -0000

* Joe Abley:

> On 2011-01-27, at 11:07, Nicholas Weaver wrote:
>
>> Lets face it, 98% of the root key rollovers are going to be benign, on that once-a-year schedule.
>
> There is no established schedule for rolling the root zone's
> KSK. All we have said to date is that we don't expect to do it any
> time soon, because it's not clear that support for automated
> handling of such an event is well-deployed in clients.

This was exactly my impression, too.  But when Nicholas brought up the
once-a-year schedule, I started looking for policy statements because
a yearly key rollover is rather scary.

The closest I could come up with is this statement:

| 6.5.  Key signing key roll-over
| 
|    Each RZ KSK will be scheduled to be rolled over through a key
|    ceremony as required, or after 5 years of operation.

<https://www.iana.org/dnssec/icann-dps.txt>

This is how I came up with the year 2014 so I didn't pull it out of
the air completely.  Of course, I welcome if you want to make it 2011
instead of 2014.

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99