RFC 3855: Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400
In plain English — editorial summary, not part of the RFC
This document describes protocol options for conveying objects that have been protected using the Cryptographic Message Syntax (CMS) and Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1 over an X.400 message transfer system. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3855
- Published
- July 2004
- Authors
- P. Hoffman; C. Bonatti
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3854Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)Current
July 2004
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
- RFC 3851Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message SpecificationObsoleted
July 2004
- RFC 2634Enhanced Security Services for S/MIMEUpdated
June 1999
- RFC 3870application/rdf+xml Media Type RegistrationCurrent
September 2004
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 3745MIME Type Registrations for JPEG 2000 (ISO/IEC 15444)Current
April 2004
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?