IETF Logo Mail Archive

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

Paul Wouters <paul@xelerance.com> Tue, 25 January 2011 18:28 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AE2B3A6853; Tue, 25 Jan 2011 10:28:16 -0800 (PST)
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 514473A6853 for <dnsext@core3.amsl.com>; Tue, 25 Jan 2011 10:28:15 -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 jUmfX1utSCe8 for <dnsext@core3.amsl.com>; Tue, 25 Jan 2011 10:28:14 -0800 (PST)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id 80B743A6403 for <dnsext@ietf.org>; Tue, 25 Jan 2011 10:28:14 -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 19361BF8B; Tue, 25 Jan 2011 13:31:12 -0500 (EST)
Date: Tue, 25 Jan 2011 13:31:11 -0500
From: Paul Wouters <paul@xelerance.com>
To: Stephan Lagerholm <stephan.lagerholm@secure64.com>
In-Reply-To: <DD056A31A84CFC4AB501BD56D1E14BBB96B061@exchange.secure64.com>
Message-ID: <alpine.LFD.1.10.1101251330150.30991@newtla.xelerance.com>
References: <alpine.LFD.1.10.1101251250040.30991@newtla.xelerance.com> <DD056A31A84CFC4AB501BD56D1E14BBB96B061@exchange.secure64.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Cc: dnsext List <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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On Tue, 25 Jan 2011, Stephan Lagerholm wrote:

> See: draft-wijngaards-dnsop-trust-history-02
>
> Abstract:
> When DNS validators have trusted keys, but have been offline for a
> longer period, key rollover will fail and they are stuck with stale
> trust anchors.  History service allows validators to query for older
> DNSKEY RRsets and pick up the rollover trail where they left off.

Ok, so the next question is, can and will the root implement this? Because
that's really the main key that needs this.

Paul
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext

v2.23.0 | Report a Bug | By Email