Some -15 text nits
David Shaw <dshaw@jabberwocky.com> Wed, 30 November 2005 16:34 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhUug-0003qi-LB for openpgp-archive@megatron.ietf.org; Wed, 30 Nov 2005 11:34:34 -0500
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07548 for <openpgp-archive@lists.ietf.org>; Wed, 30 Nov 2005 11:33:48 -0500 (EST)
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 jAUGE4BN012150; Wed, 30 Nov 2005 08:14:04 -0800 (PST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id jAUGE4Gw012149; Wed, 30 Nov 2005 08:14:04 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from foobar.cs.jhu.edu (foobar.cs.jhu.edu [128.220.13.173]) by above.proper.com (8.12.11/8.12.9) with ESMTP id jAUGE3TK012140 for <ietf-openpgp@imc.org>; Wed, 30 Nov 2005 08:14:03 -0800 (PST) (envelope-from dshaw@jabberwocky.com)
Received: from walrus.hsd1.ma.comcast.net (walrus.hsd1.ma.comcast.net [24.60.132.70]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id jAUGE2S07014 for <ietf-openpgp@imc.org>; Wed, 30 Nov 2005 11:14:02 -0500
Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.12.8/8.12.8) with ESMTP id jAUGDwX6022624 for <ietf-openpgp@imc.org>; Wed, 30 Nov 2005 11:13:58 -0500
Received: from grover.jabberwocky.com (grover.jabberwocky.com [127.0.0.1]) by grover.jabberwocky.com (8.13.1/8.13.1) with ESMTP id jAUGDu8i023265 for <ietf-openpgp@imc.org>; Wed, 30 Nov 2005 11:13:56 -0500
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id jAUGDuiQ023264 for ietf-openpgp@imc.org; Wed, 30 Nov 2005 11:13:56 -0500
Date: Wed, 30 Nov 2005 11:13:56 -0500
From: David Shaw <dshaw@jabberwocky.com>
To: ietf-openpgp@imc.org
Subject: Some -15 text nits
Message-ID: <20051130161356.GB23127@jabberwocky.com>
Mail-Followup-To: ietf-openpgp@imc.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc
User-Agent: Mutt/1.5.11
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>
These are just some fiddly language nits for -15. Nothing terribly controversial I hope. ****** The "IANA Considerations" section in the beginning of the draft contains this: Instead requests to define new tag values (say for new encryption algorithms for example) should be forwarded to the IESG Security Area Directors for consideration or forwarding to the appropriate IETF Working Group for consideration. "forwarded... or forwarding" doesn't parse very well. I suggest: Instead, requests to define new tag values (say for new encryption algorithms) should be forwarded to the IESG Security Area Directors or the appropriate IETF Working Group for consideration. ****** Section 3.7.1. String-to-key (S2K) specifier types, refers to S2K value 2 as "illegal". Everywhere else in the document, such do-not-use values are referred to as "reserved". ****** Section 3.7.2.1. Secret key encryption says "For compatibility, when an S2K specifier is used, the special value 255 is stored in the position where the hash algorithm octet would have been in the old data structure.". I suggest changing that to read "... the special value 255 or 254 ..." since 254 is a legal value there, as the table immediately after that paragraph makes clear. ****** Section 3.7.2.1. Secret key encryption, and section 5.3. Symmetric-Key Encrypted Session Key Packets refer to "passphrase" as "pass phrase". This is inconsistent with the rest of the document which always uses "passphrase". ****** Section 4.2.2.4. Partial Body Lengths has a paragraph that begins "It might also be encoded..." That doesn't make sense since there is no "it" that the sentence refers to. I believe that paragaph belongs in the following section (4.2.3. Packet Length Examples), as the "it" in question refers to the example "packet with length 100000" from 4.2.3. ****** In section 5.2.1. Signature Types, the signature class 0x18 description says "This signature is calculated directly on the subkey itself, not on any User ID or other packets", but in fact 0x18 signatures are calculated on the primary key plus subkey. Similarly, the 0x19 description says "This signature is calculated directly on the primary key itself, and not on any User ID or other packets", but in reality it is calculated exactly the same way as 0x18 is (primary+subkey). To be sure, 5.2.4 gets this right, and 5.2.1 defers to 5.2.4, but it would still be nice to not give two different answers for this. ****** 5.2.2. Version 3 Signature Packet Format says "The hash h is PKCS-1 padded exactly the same way as for the above described RSA signatures". This doesn't really make sense as there is no description of RSA signatures above. David
- Some -15 text nits David Shaw
- Re: Some -15 text nits Jon Callas
- Re: Some -15 text nits "Hal Finney"
- Re: Some -15 text nits David Shaw