…il System Status Subject From Date List [smime] Re: [Technical Errata Reported] RFC3852 (8781) [smime] Re: [Technical Errata Reported] RFC3852 (8781) Madison Church 2026-02-25 smime /arch/msg/smime/U4bAwVH8-aWbIlqj5E8bMAmZpto/ 3709325 2237072 [smime] Re: [Technical Errata Reporte…
…d [ 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 assigned by IANA"…
…nd [ 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. Turner, "Secure…
…ument, when it says: Section 15.1 contains the outdated Normative Reference: | [RFC3852] Housley, R., "Cryptographic Message Syntax (CMS)", | RFC 3852, July 2004. "[RFC3852]" is used in Sections 5.6, 9.1, 9.1.1, and 12. It should say: At the time of publication of RFC 5655, the r…
…ument, when it says: Section 15.1 contains the outdated Normative Reference: | [RFC3852] Housley, R., "Cryptographic Message Syntax (CMS)", | RFC 3852, July 2004. "[RFC3852]" is used in Sections 5.6, 9.1, 9.1.1, and 12. It should say: At the time of publication of RFC 5655, the r…