Re: [DNSOP] RFC 2845bis draft

Martin Hoffmann <martin@opennetlabs.com> Mon, 25 March 2019 17:08 UTC

Return-Path: <martin@opennetlabs.com>
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 4952F1204E3 for <dnsop@ietfa.amsl.com>; Mon, 25 Mar 2019 10:08:55 -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 1xJ04nHb8xeh for <dnsop@ietfa.amsl.com>; Mon, 25 Mar 2019 10:08:53 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (dicht.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 EE0761204E0 for <dnsop@ietf.org>; Mon, 25 Mar 2019 10:08:52 -0700 (PDT)
Received: from glaurung.nlnetlabs.nl (unknown [IPv6:2a04:b900:0:1:a2c5:89ff:feb5:e311]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 2B73112D7D; Mon, 25 Mar 2019 18:08:30 +0100 (CET)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=none (p=none dis=none) header.from=opennetlabs.com
Authentication-Results: dicht.nlnetlabs.nl; spf=none smtp.mailfrom=martin@opennetlabs.com
Date: Mon, 25 Mar 2019 18:08:29 +0100
From: Martin Hoffmann <martin@opennetlabs.com>
To: "Peter J. Philipp" <pjp@centroid.eu>
Cc: dnsop@ietf.org
Message-ID: <20190325180829.00b1cc1d@glaurung.nlnetlabs.nl>
In-Reply-To: <8c4249e4-8deb-c653-83d1-b97fd4d80786@centroid.eu>
References: <8c4249e4-8deb-c653-83d1-b97fd4d80786@centroid.eu>
Organization: Open Netlabs
X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Kt1vqtc36y0-jI4yeJAjjapvEcY>
Subject: Re: [DNSOP] RFC 2845bis draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 25 Mar 2019 17:08:55 -0000

Peter J. Philipp wrote:
> 
> I'm in contact with the original RFC 2845 authors for clarifications
> on what is meant in section 4.4 for the meaning of "Prior MAC
> (running)". In the bis draft this is in section 6.4 and seems
> unchanged.  I'm having a hard time understanding this as an
> implementor, this is an area that needs clarification I believe.

Actually, looking at this now, the definition of the digest components
in this section is even more unclear:

|      Prior Digest (running)
|      DNS Messages (any unsigned messages since the last TSIG)
|      TSIG Timers (current message)

I am probably overthinking this, but the second item can be read as if
it only contains the messages sent unsigned so far and does _not_
include the message currently being processed. This seems a bit
unlikely, but then, there must be a reason why it says "any unsigned
message" and not simply "any message".

I guess I’ll find out what is exactly meant when I am going to test my
implementation. But either way, this could perhaps be more clear?

Kind regards,
Martin