…eady handles the signatures on such a message correctly. This document updates [RFC3156] by providing an additional mechanism for producing and consuming OpenPGP-signed MIME email. This document also updates [RFC8551] by providing an additional mechanism for producing and consumi…

…o submit a key to the mail provider MUST comply to the PGP/MIME specification ([RFC3156], section 7), which states that the Content-Type must be "application/pgp-keys", there are no required or optional parameters, and the body part contains the ASCII-armored transferable Public …

…plication/pem-certificate-chain RFC8555 pgp-encrypted application/pgp-encrypted RFC3156 pgp-keys application/pgp-keys RFC3156 pgp-signature application/pgp-signature RFC3156 pidf-diff+xml application/pidf-diff+xml RFC5262 pidf+xml application/pidf+xml RFC3863 pkcs10 application/p…

…plication/pem-certificate-chain RFC8555 pgp-encrypted application/pgp-encrypted RFC3156 pgp-keys application/pgp-keys RFC3156 pgp-signature application/pgp-signature RFC3156 pidf-diff+xml application/pidf-diff+xml RFC5262 pidf+xml application/pidf+xml RFC3863 pkcs10 application/p…

…plication/pem-certificate-chain RFC8555 pgp-encrypted application/pgp-encrypted RFC3156 pgp-keys application/pgp-keys RFC3156 pgp-signature application/pgp-signature RFC3156 pidf-diff+xml application/pidf-diff+xml RFC5262 pidf+xml application/pidf+xml RFC3863 pkcs10 application/p…

…plication/pem-certificate-chain RFC8555 pgp-encrypted application/pgp-encrypted RFC3156 pgp-keys application/pgp-keys RFC3156 pgp-signature application/pgp-signature RFC3156 pidf-diff+xml application/pidf-diff+xml RFC5262 pidf+xml application/pidf+xml RFC3863 pkcs10 application/p…

…plication/pem-certificate-chain RFC8555 pgp-encrypted application/pgp-encrypted RFC3156 pgp-keys application/pgp-keys RFC3156 pgp-signature application/pgp-signature RFC3156 pidf-diff+xml application/pidf-diff+xml RFC5262 pidf+xml application/pidf+xml RFC3863 pkcs10 application/p…

…plication/pem-certificate-chain RFC8555 pgp-encrypted application/pgp-encrypted RFC3156 pgp-keys application/pgp-keys RFC3156 pgp-signature application/pgp-signature RFC3156 pidf-diff+xml application/pidf-diff+xml RFC5262 pidf+xml application/pidf+xml RFC3863 pkcs10 application/p…

…aphically signed, using e.g., S/MIME [ RFC5751 ] or Pretty Good Privacy (PGP) [ RFC3156 ], cannot be upgraded from the RFC 2047 form to normal UTF-8 characters without breaking the signature. Similarly, message parts that are encrypted may contain, when decrypted, header fields t…

…aphically signed, using e.g., S/MIME [ RFC3851 ] or Pretty Good Privacy (PGP) [ RFC3156 ], cannot be upgraded from the RFC 2047 form to normal UTF-8 characters without breaking the signature. Similarly, message parts that are encrypted may contain, when decrypted, header fields t…

…orted in PKIX (Public Key Infrastructure using X.509) [ RFC5280 ] and OpenPGP [ RFC3156 ], but there may be user-interface issues associated with the introduction of UTF-8 into addresses in this context. 5 . IANA Considerations IANA has updated the registration of the message/glo…

…aphically signed, using e.g., S/MIME [ RFC5751 ] or Pretty Good Privacy (PGP) [ RFC3156 ], cannot be upgraded from the RFC 2047 form to normal UTF-8 characters without breaking the signature. Similarly, message parts that are encrypted may contain, when decrypted, header fields t…

…pported in PKIX (Public Key Infrastructure using X.509) [ RFC5280 ] and OpenPGP RFC3156 ], but there may be user-interface issues associated with the introduction of UTF-8 into addresses in this context. . IANA Considerations IANA has updated the registration of the message/globa…

…aphically signed, using e.g., S/MIME [ RFC3851 ] or Pretty Good Privacy (PGP) [ RFC3156 ], cannot be upgraded from the RFC 2047 form to normal UTF-8 characters without breaking the signature. Similarly, message parts that are encrypted may contain, when decrypted, header fields t…