IETF Logo Mail Archive

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

Joe Abley <jabley@hopcount.ca> Thu, 27 January 2011 18:25 UTC

Return-Path: <jabley@hopcount.ca>
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 9847A3A67ED for <dnsext@core3.amsl.com>; Thu, 27 Jan 2011 10:25:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level:
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DWqxpipZHIqd for <dnsext@core3.amsl.com>; Thu, 27 Jan 2011 10:25:36 -0800 (PST)
Received: from monster.hopcount.ca (monster.hopcount.ca [216.235.14.38]) by core3.amsl.com (Postfix) with ESMTP id CEF163A67BD for <dnsext@ietf.org>; Thu, 27 Jan 2011 10:25:36 -0800 (PST)
Received: from [199.212.90.21] (helo=dh21.r2.owls.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1PiWeE-0002Jw-KJ; Thu, 27 Jan 2011 18:32:55 +0000
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <10A3D861-EC02-49FF-BBD1-44843378C9CB@icsi.berkeley.edu>
Date: Thu, 27 Jan 2011 13:28:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BC28AF0-9132-4FFD-9FA6-FCEC29A1D471@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>
To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
X-Mailer: Apple Mail (2.1082)
X-SA-Exim-Connect-IP: 199.212.90.21
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: 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: Thu, 27 Jan 2011 18:25:37 -0000

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.


Joe

v2.23.0 | Report a Bug | By Email