RFC 2632

S/MIME Version 3 Certificate Handling, June 1999

Canonical URL:
https://www.rfc-editor.org/rfc/rfc2632.txt
File formats:
Plain TextPDF
Status:
PROPOSED STANDARD
Obsoleted by:
RFC 3850
Author:
B. Ramsdell, Ed.
Stream:
IETF
Source:
smime (sec)

Cite this RFC: TXT  |  XML

DOI:  http://dx.doi.org/10.17487/RFC2632

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×