IETF Logo Mail Archive

Re: [DNSOP] KSK rollover

"George Barwood" <george.barwood@blueyonder.co.uk> Sat, 22 May 2010 08:51 UTC

Return-Path: <george.barwood@blueyonder.co.uk>
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 083DE3A6C23 for <dnsop@core3.amsl.com>; Sat, 22 May 2010 01:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.594
X-Spam-Level: ****
X-Spam-Status: No, score=4.594 tagged_above=-999 required=5 tests=[AWL=1.399, BAYES_50=0.001, HELO_EQ_BLUEYON=1.4, MIME_BASE64_BLANKS=0.041, MIME_BASE64_TEXT=1.753]
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 XJPEklMk0-Lp for <dnsop@core3.amsl.com>; Sat, 22 May 2010 01:51:01 -0700 (PDT)
Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by core3.amsl.com (Postfix) with ESMTP id 32BEE3A6C26 for <dnsop@ietf.org>; Sat, 22 May 2010 01:51:00 -0700 (PDT)
Received: from [172.23.170.142] (helo=anti-virus02-09) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1OFkQ1-00046u-6K for dnsop@ietf.org; Sat, 22 May 2010 09:50:53 +0100
Received: from [92.238.99.235] (helo=GeorgeLaptop) by asmtp-out6.blueyonder.co.uk with esmtpa (Exim 4.52) id 1OFkQ0-0001Kl-IT for dnsop@ietf.org; Sat, 22 May 2010 09:50:52 +0100
Message-ID: <B4E2D5F87D9348B283F2C018841535BC@local>
From: George Barwood <george.barwood@blueyonder.co.uk>
To: dnsop@ietf.org
References: <A865F793EED745D2B5F15A33F9467EEA@local>
Date: Sat, 22 May 2010 09:50:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Subject: Re: [DNSOP] KSK rollover
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: Sat, 22 May 2010 08:51:02 -0000

Well, I have uploaded a draft :

http://www.ietf.org/id/draft-barwood-dnsop-ds-publish-00.txt

Comments and/or indications of support are of course welome, on or off list.

George

----- Original Message ----- 
From: "George Barwood" <george.barwood@blueyonder.co.uk>
To: <dnsop@ietf.org>
Sent: Thursday, May 13, 2010 8:56 AM
Subject: [DNSOP] KSK rollover


>I have been thinking about KSK rollover in my DNSSEC implementation, and it seems
> that there is currently no  specification for KSK rollover within the DNSSEC protocol.
> 
> There is this expired requirements draft
> 
> http://tools.ietf.org/wg/dnsop/draft-ietf-dnsop-key-rollover-requirements/
> 
> but that's all I found.
> 
> Have I missed something? It seems to me that this is a rather vital component if
> DNSSEC is to be widely deployed.
> 
> Are there any plans to revive and/or implement these requirements?
> 
> George Barwood
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email