… RFC 3280 [ RFC3280 ]. The S/MIME Capabilities attribute, defined in RFC 3851 [ RFC3851 ], is defined to indicate cryptographic capabilities of the sender of a signed S/MIME message. This information can be used by the recipient in subsequent S/MIME secured exchanges to select ap…

… by RFC 3280 [RFC3280]. The S/MIME Capabilities attribute, defined in RFC 3851 [RFC3851], is defined to indicate cryptographic capabilities of the sender of a signed S/MIME message. This information can be used by the recipient in subsequent S/MIME secured exchanges to select app…

…RFC5750 ], and [ RFC5751 ]. [ SMIMEv3.2 ] refers to [ RFC2634 ], [ RFC3850 ], [ RFC3851 ], [ RFC3852 ], and [ RFC5035 ]. [ SMIMEv4 ] refers to [ RFC2634 ], [ RFC5035 ], [ RFC5652 ], [ RFC8550 ], and this document. 7.2 . Normative References [ CHARSETS ] IANA, "Character sets assi…

… RFC2634 ], and [ RFC5035 ]. [ SMIMv3.1 ] refers to [ RFC2634 ], [ RFC3850 ], [ RFC3851 ], [ RFC3852 ], and [ RFC5035 ]. Ramsdell & Turner Standards Track [Page 38] RFC 5751 S/MIME 3.2 Message Specification January 2010 7.2 . Normative References [ CERT32 ] Ramsdell, B. and S. Tu…

… example, message parts that are cryptographically 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…

…de SMTP-TLS [ RFC3207 ], SMTP-Auth [ RFC4954 ], OpenPGP RFC4880 ], and S/MIME [ RFC3851 ]. The core of the Internet Mail architecture does not impose any security requirements or functions on the end-to-end or hop-by-hop components. For example, it does not require participant au…

… example, message parts that are cryptographically 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…

…2/2045 -RFC1847 (multipart/signed) -RFC3798 (message/disposition-notification) -RFC3851 (application/pkcs7-signature) It should say: The AS3-MDN follows the MDN specification [6] except where noted in | this section. Refer to RFC 2045 for the format of MIME headers. | The format …

…2/2045 -RFC1847 (multipart/signed) -RFC3798 (message/disposition-notification) -RFC3851 (application/pkcs7-signature) It should say: The AS3-MDN follows the MDN specification [6] except where noted in | this section. Refer to RFC 2045 for the format of MIME headers. | The format …