Re: [DNSOP] RFC 6781 and double signature KSK rollover

Marcos Sanz <sanz@denic.de> Tue, 25 October 2016 13:15 UTC

Return-Path: <sanz@denic.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5331293F2 for <dnsop@ietfa.amsl.com>; Tue, 25 Oct 2016 06:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.631
X-Spam-Level:
X-Spam-Status: No, score=-4.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fN37DWp7de-B for <dnsop@ietfa.amsl.com>; Tue, 25 Oct 2016 06:15:49 -0700 (PDT)
Received: from office.denic.de (office.denic.de [81.91.160.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4755129461 for <dnsop@ietf.org>; Tue, 25 Oct 2016 06:15:49 -0700 (PDT)
Received: from office.denic.de (mailout-6.osl.denic.de [10.122.34.32]) by office.denic.de (Postfix) with ESMTP id 2042D1FB89 for <dnsop@ietf.org>; Tue, 25 Oct 2016 15:15:41 +0200 (CEST)
Received: from notes1.fra2.osl.denic.de (notes1.fra2.osl.denic.de [10.122.50.48]) by office.denic.de with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) id 1bz1Zs-0003FO-Ui; Tue, 25 Oct 2016 15:15:40 +0200
In-Reply-To: <d8285e11-9d99-227d-e0cd-0210abdf431a@pletterpet.nl>
References: <OF5B3B3222.83E22422-ONC1258056.00536355-C1258056.0056B9D8@notes.denic.de> <d8285e11-9d99-227d-e0cd-0210abdf431a@pletterpet.nl>
To: Matthijs Mekking <matthijs@pletterpet.nl>
MIME-Version: 1.0
X-KeepSent: E34929BE:2E0C8D50-C1258057:00488BB5; type=4; name=$KeepSent
X-Mailer: IBM Notes Release 9.0.1FP5 Octobe4, 2013
From: Marcos Sanz <sanz@denic.de>
Message-ID: <OFE34929BE.2E0C8D50-ONC1258057.00488BB5-C1258057.0048D848@notes.denic.de>
Date: Tue, 25 Oct 2016 15:15:39 +0200
X-MIMETrack: Serialize by Router on notes/Denic at 25.10.2016 15:15:40, Serialize complete at 25.10.2016 15:15:40
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/OR8ea5O7-w_WNOx4UvCoJQGbR14>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] RFC 6781 and double signature KSK rollover
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 25 Oct 2016 13:15:51 -0000

Matthijs,

> > my attention has been brought to the KSK rollover double-signature 
style
> > described in 6781 and what I think is a mistake/oblivion there. 
Section
> > 4.1.2 states

[...]

> You are right: DS_K_2 may only be provided to the parent *after* the TTL 

> of DNSKEY_K_1 has passed. RFC 7583 has more accurate timings for 
> rollovers. The corresponding timeline is described in section 3.3.1.

thanks for the pointer. RFC 7583 does it right.

That begs for the question: how to deal with the wrong information 
propagated in 6781? Submit errata? Label it "Updated by 7583"?

Best,
Marcos