Re: [lamps] Barry Leiba's No Objection on draft-ietf-lamps-cms-hash-sig-09: (with COMMENT)

Russ Housley <housley@vigilsec.com> Mon, 16 September 2019 21:50 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71FB71201CE for <spasm@ietfa.amsl.com>; Mon, 16 Sep 2019 14:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 JoGg-mJGz4Qu for <spasm@ietfa.amsl.com>; Mon, 16 Sep 2019 14:50:07 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45F8512011D for <spasm@ietf.org>; Mon, 16 Sep 2019 14:50:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A8D55300B0C for <spasm@ietf.org>; Mon, 16 Sep 2019 17:50:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id FEvCcfGMNIJT for <spasm@ietf.org>; Mon, 16 Sep 2019 17:50:04 -0400 (EDT)
Received: from [5.5.33.49] (unknown [204.194.23.17]) by mail.smeinc.net (Postfix) with ESMTPSA id B6AA6300577; Mon, 16 Sep 2019 17:50:03 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CALaySJKDXvmSa0XwETDvsA9zHOdgdomc-hQo-xHK=A6zw-PhyA@mail.gmail.com>
Date: Mon, 16 Sep 2019 17:50:04 -0400
Cc: IESG <iesg@ietf.org>, Tim Hollebeek <tim.hollebeek@digicert.com>, LAMPS WG <spasm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEC64601-4439-4891-9F23-496467008AE3@vigilsec.com>
References: <156824031769.13397.11560883765399298866.idtracker@ietfa.amsl.com> <0D4923CE-0775-411D-8B38-B7C0121ECC5F@vigilsec.com> <CALaySJKDXvmSa0XwETDvsA9zHOdgdomc-hQo-xHK=A6zw-PhyA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/n0ut6-Q7f1WjVTCc37AlIblVsEo>
Subject: Re: [lamps] Barry Leiba's No Objection on draft-ietf-lamps-cms-hash-sig-09: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 21:50:12 -0000


> On Sep 16, 2019, at 5:46 PM, Barry Leiba <barryleiba@computer.org> wrote:
> 
> Thanks for the reply, Russ.  Just on the one thing that remains open;
> on the rest, all is good:
> 
>>> — Section 2.2 —
>>> 
>>>  The second parameter is
>>>  the number of bytes output by the hash function, m, which is the
>>>  amount of data associated with each node in the tree.
>>> 
>>> It’s a small thing, but I think the “m” is misplaced where it is, and suggest
>>> “…the number of bytes, m, output by the hash function….”
>> 
>> How about:
>> 
>>   The second parameter is
>>   the number of bytes output by the hash function, m, and it is the
>>   amount of data associated with each node in the tree.
> 
> It retains the fault that "m" is not the hash function, and "by the
> hash function, m," makes it look like it is.  I still think you're
> better off moving "m" to one of these positions:
> 
> "The second parameter, m, is the number of bytes output by the hash function"
> "The second parameter is the number of bytes, m, output by the hash function"
> 
> But I'll grant that I'm being picky about the wording, and that it's
> not likely to be confusing in practice.  So if you think it's best
> with the "m" where you have it, we're done here, and thanks for
> considering my suggestions and accepting most of them.

I guess I missed your point on the first reading.

How about:

   The second parameter, m,
   is the number of bytes output by the hash function, and it is the
   amount of data associated with each node in the tree.

Russ