RFC 3850
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling, July 2004
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoletes:
- RFC 2632
- Obsoleted by:
- RFC 5750
- Author:
- B. Ramsdell, Ed.
- Stream:
- IETF
- Source:
- smime (sec)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3850
Discuss this RFC: Send questions or comments to the mailing list smime@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3850
Abstract
This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) agents. S/MIME provides a method to send and receive secure MIME messages, and certificates are an integral part of S/MIME agent processing. S/MIME agents validate certificates as described in RFC 3280, the Internet X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME agents must meet the certificate processing requirements in this document as well as those in RFC 3280. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.