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

Paul Wouters <paul@xelerance.com> Mon, 31 January 2011 19:12 UTC

Return-Path: <paul@xelerance.com>
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 CDCA93A6965 for <dnsext@core3.amsl.com>; Mon, 31 Jan 2011 11:12:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.575
X-Spam-Level:
X-Spam-Status: No, score=-2.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 VHm4fKkePPrD for <dnsext@core3.amsl.com>; Mon, 31 Jan 2011 11:12:32 -0800 (PST)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id E1B1E3A6C21 for <dnsext@ietf.org>; Mon, 31 Jan 2011 11:12:31 -0800 (PST)
Received: from tla.xelerance.com (tla.xelerance.com [193.110.157.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by newtla.xelerance.com (Postfix) with ESMTP id 93B10C4FE; Mon, 31 Jan 2011 14:15:45 -0500 (EST)
Date: Mon, 31 Jan 2011 14:15:45 -0500
From: Paul Wouters <paul@xelerance.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
In-Reply-To: <AANLkTinOtx88vK3mz-w=uw1CnsKwm=c-nTDOsj=5JAPY@mail.gmail.com>
Message-ID: <alpine.LFD.1.10.1101311413340.22764@newtla.xelerance.com>
References: <alpine.LFD.1.10.1101251250040.30991@newtla.xelerance.com> <17A80F45-52CB-43F6-BD4A-3488821F6933@hopcount.ca> <3A1DEE95-8C8E-4C89-97EB-6D8F799ADE25@virtualized.org> <583A62B0-0DBF-469A-AF8A-B81DEDD1E7E2@dotat.at> <86B1D38A-C274-4335-B30E-3C5C0DF05C38@hopcount.ca> <4D45DE93.9090508@vpnc.org> <AANLkTinbjRebooyqWMpZ2oTudruoDSGqgaXXr35WPYVH@mail.gmail.com> <AANLkTikiqe2K4S-dNsyQZ-xp71J4bM11SsahwpxfDKCX@mail.gmail.com> <4C747F08-A9E8-46E6-AE76-0A999A16D276@hopcount.ca> <AANLkTinOtx88vK3mz-w=uw1CnsKwm=c-nTDOsj=5JAPY@mail.gmail.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: dnsext@ietf.org, Paul Hoffman <paul.hoffman@vpnc.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: Mon, 31 Jan 2011 19:12:32 -0000

On Mon, 31 Jan 2011, Brian Dickson wrote:

> Having read it, it appears that any new RZ KSK is pre-published and
> signed by the old KSK for about 50 days only.
>
> After that point in time, an old trust anchor would no longer be able
> to automagically validate the new KSK (5011 method).
>
> So, it appears that an automagic bootstrap method would have to rely
> on something other than the RZ KSK (or specifically its trust
> anchor/public key).
>
> The simplest bootstrap method would be to have a series of BSK
> (bootstrap keys), created on a periodic basis (every N years), and

I think the simplest method is the TALINK one described in Wouter's
draft. Keep the historic 5011 information in a special zone (and ignore
the expired RRSIGs in them)

I don't think we realistically can change the current root key management.

Paul