RFC 2632

"S/MIME Version 3 Certificate Handling", June 1999

Canonical URL:

http://www.rfc-editor.org/rfc/rfc2632.txt
This document is also available in this non-normative format: TXT.PDF.

Status:

PROPOSED STANDARD

Obsoleted by:

RFC 3850

Author:

B. Ramsdell, Ed.

Stream:

IETF

Source:

smime (sec)

Please refer here for any errata for this document. To submit a new errata report, go to the main errata page.

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 Stream, see RFC 4844.