Re: [DNSOP] I-D Action: draft-ietf-dnsop-maintain-ds-04.txt

Paul Wouters <paul@nohats.ca> Tue, 10 January 2017 17:53 UTC

Return-Path: <paul@nohats.ca>
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 92D53129541 for <dnsop@ietfa.amsl.com>; Tue, 10 Jan 2017 09:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.199
X-Spam-Level:
X-Spam-Status: No, score=-5.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 Yr_7X7LcwkHM for <dnsop@ietfa.amsl.com>; Tue, 10 Jan 2017 09:53:40 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 5100A12941D for <dnsop@ietf.org>; Tue, 10 Jan 2017 09:53:39 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3tyflL64BZz3Nq; Tue, 10 Jan 2017 18:53:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1484070814; bh=lEVU6BJlZKd8ZcyiVNbY6HJ8ws5c2/5e6ABu6R6zy6A=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=uN59fbHsE7uy4M8BgUe1v+0vVatsNCw0uPhMAOb0oH15weHFBfX5nXB8DuMmEkyKx QEaQYTSMsUZVdKots5viWoBy92o4vd6lh9wLZx38n+B2j5CUUHtpsXSRmMHJ3demfW 1xNiZiwVKOcmzej2BRLV0RgXOQYYGSjQoyFatHDk=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id D--ipb8EJ_Yo; Tue, 10 Jan 2017 18:53:33 +0100 (CET)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 10 Jan 2017 18:53:33 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 456316ED5B1; Tue, 10 Jan 2017 12:53:30 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca 456316ED5B1
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 340B040D7281; Tue, 10 Jan 2017 12:53:30 -0500 (EST)
Date: Tue, 10 Jan 2017 12:53:30 -0500
From: Paul Wouters <paul@nohats.ca>
To: Matthijs Mekking <matthijs@pletterpet.nl>, Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <04c6766e-87fe-9355-f651-633df6fe961e@pletterpet.nl>
Message-ID: <alpine.LRH.2.20.1701101247080.4762@bofh.nohats.ca>
References: <147792810754.32434.7815626160706350019.idtracker@ietfa.amsl.com> <f3c5f93a-c1ae-8cff-2782-6352669f4920@pletterpet.nl> <11dd4e3d-3620-a478-cee5-6be4f9b9a141@pletterpet.nl> <alpine.LRH.2.20.1701101141250.4762@bofh.nohats.ca> <04c6766e-87fe-9355-f651-633df6fe961e@pletterpet.nl>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ESOFJ9PMIRsG9Z58I9YH9A2OVMs>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-maintain-ds-04.txt
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, 10 Jan 2017 17:53:41 -0000

On Tue, 10 Jan 2017, Matthijs Mekking wrote:

>> I personally think the simplification of using all zero's is good. If
>> someone accidentally changes the wrong number in the DS record when
>> changing parameters, it will prevent a mistaken delete request. While,
>> the zone might still fail, at least it won't be forced to go through a
>> period of insecure while the parental DS gets repopulated.
>
> I am fine with using all zero's. I just don't think the change in
> resource record format is a good idea, dropping the last RDATA field
> from the CDS record.

Ohh, I think Matthijs actually found a bug:

The CDS RDATA is identical to the DS RDATA format, which is
according to RFC 4034:

                         1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |           Key Tag             |  Algorithm    |  Digest Type  |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    /                                                               /
    /                            Digest                             /
    /                                                               /
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


The draft states:

 	The keying material payload is represented by a single 0.

So the CDS delete entry currently specified as:

    CDS 0 0 0

Should in fact be:

    CDS 0 0 0 0


And similarly, the CDNSKEY is currently specified as:

    CDNSKEY 0 3 0

and should be:

    CDNSKEY 0 3 0 0


Olafur, do you agree? Should we push a new draft version with this fix?

Paul