-----BEGIN PGP SIGNED MESSAGE-----
I've looked through bis05 and I think the wording on non-US-ASCII characters
in armor headers is still too vague.
1. It's not only the Comment field that is affected here. IIRC, GnuPG uses
non-us-ascii characters for the version header if localized, too.
2. An implementation allowing full UTF-8 in the Armor Headers indirectly
I'd really like to see that Armor Headers MUST (at least SHOULD) be
constrained to US-ASCII, except in clearsigning, where the full UTF-8 may be
used since the enclosed text is already UTF-8.
The other way round: If exporting keys with armor or creating an armored
detached signature, all armor headers MUST be constrained to US-ASCII.
AFAISI, this should suffice for the rfc3156 cases.
Marc Mutz <mutz(_at_)kde(_dot_)org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----