Re: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-02.txt (fwd)

[Ángel <[e-mail]>]

Hello all

After reviewing these two drafts, I agree there are no substantial
changes in draft-ietf-openpgp-crypto-refresh-00.txt from rfc4880, and
consider draft-ietf-openpgp-crypto-refresh-02.txt good to iterate from.

Some specific comments are provided below.

Looking forward to seeing you all at the meeting.

- Ángel



crypto-refresh-00 nitpicks
=====

I would prefer to keep single quotes for values referring to single
bytes standing by themselves, as rfc4880 did. -00 changed them to
double quotes but using single quotes as in C seems better.

This happens in
* 5.9.  Literal Data Packet (Tag 11)
('b', 't', 'u', 'l', '1') vs ("b", "t", "u", "l", "1")

* 6.2.  Forming ASCII Armor with '-' and ':'
* 7.1.  Dash-Escaped Text with '-'

but does *not* apply to the characters in 8. Regular Expressions

Additionally, in 7.1 a single-quoted space (' ') was
converted to use backticks (` `), which seems like an
error when converting the document. It makes sense
in some markdown conversions, but not in the rfc results.

In appendix A, an extra space was inserted between "Philip R." 
and "Zimmermann" (Appendix C in -02)


crypto-refresh-01/02 nitpicks
=====
At 1. Introduction, change "RFC 5581 (Camellia cipher)" to "RFC 5581
(The Camellia Cipher in OpenPGP)" or "RFC 5581 (Camellia Cipher in
OpenPGP)", since just "Camellia cipher" could be confused with the
description itself of Camellia (rfc3713).
"ECC for OpenPGP" should perhaps be changed to "ECC in OpenPGP" which is the
preposition used in that rfc title.
Full name of RFC 6637 is "Elliptic Curve Cryptography (ECC) in OpenPGP" and
would be the proper one if we wanted to use the complete names of the rfc,
albeit I don't think that would matter either way.


I would prefer to see the new section "ECC Curve OID" as 9.5 instead of 9.2