S/MIME Version 3 Certificate Handling
RFC 2632, “S/MIME Version 3 Certificate Handling”, is a Proposed Standard document published in June 1999 by B. Ramsdell. It has been obsoleted by RFC 3850 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [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 2632 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 2631 Diffie-Hellman Key Agreement Method
- RFC 2633 S/MIME Version 3 Message Specification
- RFC 2630 Cryptographic Message Syntax
- RFC 2634 Enhanced Security Services for S/MIME
- RFC 2629 Writing I-Ds and RFCs using XML
- RFC 2635 DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings
- RFC 2628 Simple Cryptographic Program Interface
- RFC 2636 Wireless Device Configuration via ACAP