S/MIME Version 3.1 Certificate Handling
draft-ramsdell-rfc2632bis-00

Document Type Expired Internet-Draft (individual)
Author Blake Ramsdell 
Last updated 2001-07-13
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ramsdell-rfc2632bis-00.txt

Abstract

S/MIME (Secure/Multipurpose Internet Mail Extensions), described in [SMIME-MSG], 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 [KEYM]. S/MIME agents MUST meet the certificate processing requirements documented in this document in addition to those stated in [KEYM].

Authors

Blake Ramsdell (blake@sendmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)