Werner Koch <wk(_at_)gnupg(_dot_)org> writes:
On Tue, 21 Mar 2017 00:14, mdb(_at_)juniper(_dot_)net said:
As an editorial remark, it would be nice if rfc4880bis were to use
a consistent representation for the secure hash algorithm families.
SHA1 is sometimes written as SHA1 and sometimes written as SHA-1.
Thanks for this suggestion which I pushed right now.
Thank you.
I have not yet looked at your other change requests, though.
Mostly I was trying to hit the SHA-1 to transition to SHA2-256.
I think TripleDES needs to go from a MUST to a SHOULD algorithm.
I think AES128 needs to be a MUST algoirthm.
I think that RIPEMD160 needs to be a SHOULD NOT algorithm.
I think that AES256 needs to be a SHOULD algorithm.
Except for this:
14.3.2. {13.3.2} Hash Algorithm Preferences
Since SHA256 is the MUST-implement hash algorithm, if it is not
I changed this from "SHA-1" to "SHA2-256".
Good.
Being consistent and clear is important.
-- Mark
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp