Using Secure DNS to Assert S/MIME Usage
draft-srose-smimelock-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Scott Rose | ||
| Last updated | 2014-03-27 (Latest revision 2013-09-23) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 draft defines and discusses the use of a new DNS resource record (RR) type to address S/MIME downgrade attacks. The SMIMELOCK RR allows a domain to convey general message security policy. Primarily, this RR allows the domain owner to advertise a policy that all legitimate messages from this domain will be signed by a verifiable certificate.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)