IETF Logo Mail Archive

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

Matthijs Mekking <matthijs@pletterpet.nl> Tue, 25 October 2016 15:17 UTC

Return-Path: <matthijs@pletterpet.nl>
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 82C951296BA for <dnsop@ietfa.amsl.com>; Tue, 25 Oct 2016 08:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 HDaWT3ZfVUAl for <dnsop@ietfa.amsl.com>; Tue, 25 Oct 2016 08:17:26 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (open.nlnetlabs.nl [185.49.140.10]) (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 7A9761296C7 for <dnsop@ietf.org>; Tue, 25 Oct 2016 08:17:25 -0700 (PDT)
Received: from [172.19.130.214] (vpn-11-mht.dyndns.com [216.146.45.34]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 24604B6B3 for <dnsop@ietf.org>; Tue, 25 Oct 2016 17:17:17 +0200 (CEST)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=none header.from=pletterpet.nl
To: dnsop@ietf.org
References: <OF5B3B3222.83E22422-ONC1258056.00536355-C1258056.0056B9D8@notes.denic.de> <d8285e11-9d99-227d-e0cd-0210abdf431a@pletterpet.nl> <OFE34929BE.2E0C8D50-ONC1258057.00488BB5-C1258057.0048D848@notes.denic.de>
From: Matthijs Mekking <matthijs@pletterpet.nl>
Message-ID: <85941abd-d589-309e-6947-20376c7666e0@pletterpet.nl>
Date: Tue, 25 Oct 2016 17:17:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <OFE34929BE.2E0C8D50-ONC1258057.00488BB5-C1258057.0048D848@notes.denic.de>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ypGEH97uY_FmrvwgMU6kSN1L6pg>
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 15:17:30 -0000


On 25-10-16 15:15, Marcos Sanz wrote:
> 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"?

I think an errata is appropriate.

Best regards,
   Matthijs


>
> Best,
> Marcos
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

v2.23.0 | Report a Bug | By Email