Secure/Multipurpose Internet Mail Extensions Version 3.1 Certificate Handling
RFC 3850, “Secure/Multipurpose Internet Mail Extensions Version 3.1 Certificate Handling”, is a Proposed Standard document published in July 2004 by B. Ramsdell. It obsoletes RFC 2632. It has been obsoleted by RFC 5750 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3850 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3849 IPv6 Address Prefix Reserved for Documentation
- RFC 3851 Secure/Multipurpose Internet Mail Extensions Version 3.1 Message Specification
- RFC 3848 ESMTP and LMTP Transmission Types Registration
- RFC 3852 Cryptographic Message Syntax
- RFC 3847 Restart Signaling for Intermediate System to Intermediate System
- RFC 3853 S/MIME Advanced Encryption Standard Requirement for the Session Initiation Protocol
- RFC 3846 Mobile IPv4 Extension for Carrying Network Access Identifiers
- RFC 3854 Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions