Secure/Multipurpose Internet Mail Extensions (S/ MIME) Version 3.2 Certificate Handling
draft-schaad-lamps-rfc5750-bis-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jim Schaad, Blake C. Ramsdell , Sean Turner | ||
| Last updated | 2016-07-22 | ||
| Replaced by | draft-ietf-lamps-rfc5750-bis | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-lamps-rfc5750-bis | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) v3.2 agents. S/MIME provides a method to send and receive secure MIME messages, and certificates are an integral part of S/MIME agent processing. S/MIME agents validate certificates as described in RFC 5280, the Internet X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME agents must meet the certificate processing requirements in this document as well as those in RFC 5280. This document obsoletes RFC 3850.
Authors
Jim Schaad
Blake C. Ramsdell
Sean Turner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)