Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 36
- Abstract
- This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 2633. [STANDARDS-TRACK]
- Publication Date
- 2004-07-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3851- Link
- https://doi.org/10.17487/RFC3851
- Author(s)
- Blake C. Ramsdell
- Keyword(s)
- MIME, Encryption
Latest version of IETF RFC 3851
Document Versions — IETF RFC 3851
-
▶ IETF RFC 3851 (2004-07-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- NIST FIPS 180-2 [Withdrawn]
- Character sets assigned by IANA. See http://www.iana.org/assignments/character-sets EXTERNAL
- IETF RFC 1750 [Superseded*]
- IETF RFC 1847 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2047 [Active*]
- IETF RFC 2048 [Superseded*]
- IETF RFC 2049 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2183 [Active*]
- IETF RFC 2311 [Active*]
- IETF RFC 2315 [Active*]
- IETF RFC 2634 [Active*]
- IETF RFC 2785 [Active*]
- IETF RFC 3218 [Active*]
- IETF RFC 3274 [Active*]
- IETF RFC 3370 [Active*]
- IETF RFC 3565 [Active*]
- IETF RFC 3850 [Superseded*]
- IETF RFC 3852 [Superseded*]
- T-REC-X.208.1988 — CCITT/ISO88d EXTERNAL
- T-REC-X.209.1988 — 5 EXTERNAL
- T-REC-X.509.1988 — 4 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3851.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3851, Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification. Available at https://doi.org/10.17487/RFC3851
Snippet:
IETF RFC 3851, Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification. Available at https://doi.org/10.17487/RFC3851
HTML (ISO 690 compliant)
Preview:
IETF RFC 3851, Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification. Available at https://doi.org/10.17487/RFC3851
Snippet:
<span class="citation"><cite>IETF RFC 3851</cite>, Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification. Available at <a href="https://doi.org/10.17487/RFC3851" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3851</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3851, Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
doi: 10.17487/RFC3851
url: https://doi.org/10.17487/RFC3851
doi: 10.17487/RFC3851
url: https://doi.org/10.17487/RFC3851
Snippet:
<li> <cite id="bib-rfc3851">IETF RFC 3851</cite>, Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification <span class="doi">10.17487/RFC3851</span> </li>
Referenced By
- IETF RFC 3850 [Superseded*]
- IETF RFC 3852 [Superseded*]
- IETF RFC 3859 [Active*]
- IETF RFC 3860 [Active*]
- IETF RFC 3863 [Active*]
- IETF RFC 3891 [Active*]
- IETF RFC 3903 [Active*]
- IETF RFC 3923 [Active*]
- IETF RFC 3926 [Superseded*]
- IETF RFC 4010 [Active*]
- IETF RFC 4119 [Active*]
- IETF RFC 4227 [Active*]
- IETF RFC 4262 [Active*]
- IETF RFC 4354 [Active*]
- IETF RFC 4408 [Superseded*]
- IETF RFC 4412 [Active*]
- IETF RFC 4567 [Active*]
- IETF RFC 4568 [Active*]
- IETF RFC 4572 [Superseded*]
- IETF RFC 4823 [Active*]
- IETF RFC 4870 [Superseded*]
- IETF RFC 4871 [Superseded*]
- IETF RFC 4949 [Active*]
- IETF RFC 4952 [Superseded*]
- IETF RFC 4954 [Active*]
- IETF RFC 4975 [Active*]
- IETF RFC 4976 [Active*]
- IETF RFC 5321 [Active*]
- IETF RFC 5364 [Active*]
- IETF RFC 5405 [Superseded*]
- IETF RFC 5598 [Active*]
- IETF RFC 5652 [Active*]
- IETF RFC 5751 [Superseded*]