UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IETF RFC 5750

Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling

active, Most Current
Buy Now
Organization: IETF
Publication Date: 1 January 2010
Status: active
Page Count: 21
scope:

Introduction

S/MIME (Secure/Multipurpose Internet Mail Extensions) v3.2, 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 verify 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].

This specification is compatible with the Cryptographic Message Syntax (CMS) RFC 5652 [CMS] in that it uses the data types defined by CMS. It also inherits all the varieties of architectures for certificate-based key management supported by CMS.

Document History

IETF RFC 5750
January 1, 2010
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling
Introduction S/MIME (Secure/Multipurpose Internet Mail Extensions) v3.2, described in [SMIME-MSG], provides a method to send and receive secure MIME messages. Before using a public key to provide...

References

Advertisement