Re: Section 5.2.3 of latest draft: bis14.

Ben Laurie <ben@algroup.co.uk> Mon, 15 August 2005 14:37 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4g5V-00016Q-40 for openpgp-archive@megatron.ietf.org; Mon, 15 Aug 2005 10:37:17 -0400
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06646 for <openpgp-archive@lists.ietf.org>; Mon, 15 Aug 2005 10:37:14 -0400 (EDT)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j7FEG89G073221; Mon, 15 Aug 2005 07:16:08 -0700 (PDT) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j7FEG8tD073220; Mon, 15 Aug 2005 07:16:08 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from mail.links.org (mail.links.org [217.155.92.109]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j7FEG6gF073195 for <ietf-openpgp@imc.org>; Mon, 15 Aug 2005 07:16:07 -0700 (PDT) (envelope-from ben@algroup.co.uk)
Received: from [193.133.15.218] (localhost [127.0.0.1]) by mail.links.org (Postfix) with ESMTP id 2159D33C1A; Mon, 15 Aug 2005 15:16:05 +0100 (BST)
Message-ID: <4300A3A6.4020409@algroup.co.uk>
Date: Mon, 15 Aug 2005 15:16:06 +0100
From: Ben Laurie <ben@algroup.co.uk>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Hal Finney <hal@finney.org>
CC: ietf-openpgp@imc.org, lpb@ece.cmu.edu
Subject: Re: Section 5.2.3 of latest draft: bis14.
References: <20050715234725.0293757E8C@finney.org>
In-Reply-To: <20050715234725.0293757E8C@finney.org>
X-Enigmail-Version: 0.89.6.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>
Content-Transfer-Encoding: 7bit

Hal Finney wrote:
> Levi Broderick writes:
> 
>>I noticed that the following bullet is missing from the latest draft.
>>It used to appear between 'One-octet hash algorithm' and 'Hashed
>>subpacket data set' in section 5.2.3.
>>
>>      - Two-octet scalar octet count for following hashed subpacket
>>        data. Note that this is the length in octets of all of the hashed
>>        subpackets; a pointer incremented by this number will skip over
>>        the hashed subpackets.
> 
> 
> This is definitely an error and needs to be fixed.

I believe the idea was to eliminate this and the following instance for 
unhashed subpacket data sets, since the count is defined there.

> A couple of other relatively minor points relating to this section.
> 
> We now use the term "data set" for the hashed and unhashed subpackets:
> 
>       - Hashed subpacket data set. (zero or more subpackets)
> 
>       - Two-octet scalar octet count for the following unhashed
>         subpacket data. Note that this is the length in octets of all of
>         the unhashed subpackets; a pointer incremented by this number
>         will skip over the unhashed subpackets.
> 
>       - Unhashed subpacket data set. (zero or more subpackets)
> 
> "Data set" is defined in the next section, 5.2.3.1:
> 
>     A subpacket data set consists of zero or more signature subpackets,
>     preceded by a two-octet scalar count of the length in octets of all
>     the subpackets; a pointer incremented by this number will skip over
>     the subpacket data set.
> 
> This definition could be interpreted to mean that the data set includes
> the two-octet scalar count.  In fact, in the layout in 5.2.3 the data
> set does not include the scalar count.  5.2.3.1 could be reworded to say
> "A subpacket data set consists of zero or more signature subpackets,
> AND IS preceded by a two-octet scalar count..."

There's no penalty for clarity, right? So why not add "Note that the 
count is the number of bytes to skip after the count itself has been 
read", for instance.

Cheers,

Ben.

-- 
http://www.apache-ssl.org/ben.html       http://www.thebunker.net/

"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff