Using Secure DNS to Associate Certificates with Domain Names For S/MIME
draft-hoffman-dane-smime-04
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul E. Hoffman , Jakob Schlyter | ||
| Last updated | 2013-02-20 (Latest revision 2012-09-08) | ||
| Replaced by | draft-ietf-dane-smime | ||
| 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-dane-smime | |
| 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 describes how to use secure DNS to associate an S/MIME user's certificate with the intended domain name, similar to the way that DANE (RFC 6698) does for TLS.
Authors
Paul E. Hoffman
Jakob Schlyter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)