MIME is fine for PGP over email, but do keep in mind that PGP is not
strictly used in email and using MIME is not necessarily helpful and is
possibly needlessly complicated in some of the other use cases (just
encrypting personal files and data at rest, for example).
And if we are going to start talking about "PGP/MIME", then I think
revising RFC-3156 should be part of the discussion at some point. As it is
stands today, it is impossible to craft a proper "PGP/MIME" message unless
your mail client directly supports 3156. It requires special SMTP headers
that are usually set by the mail client and over which the user has no
control (and don't get me started on that extra "version 1" MIME
section...).
-Wyllys
On Thu, Mar 19, 2015 at 7:14 PM Phillip Hallam-Baker
<phill(_at_)hallambaker(_dot_)com>
wrote:
As a branding issue, I would pick the name PGP/MIME for the working group
and make the focus decrufting legacy bits of PGP and making a MIME based
scheme the new common denominator for framing.
If there was also a clearly defined strategy for interop with S/MIME
credentials then such a specification could be positioned as the future
upgrade path for OpenPGP and S/MIME.
Since an S/MIME credential can be turned into a fingerprint pretty easily
and the fingerprints are what people actually use in practice to exchange
OpenPGP mail. This is not exactly a major problem.
(Yes I know that there is a PGP/MIME mode at the moment. but that isn't
the point).
Think of it as embrace and extend...
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp