Using Secure DNS to Associate Certificates with Domain Names For S/MIME
draft-hoffman-dane-smime-04
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-02-20 (latest revision 2012-09-08) | ||
| Replaced by | RFC 8162 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dane-smime | |
| 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-hoffman-dane-smime-04.txt
https://www.ietf.org/archive/id/draft-hoffman-dane-smime-04.txt
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 Hoffman
(paul.hoffman@vpnc.org)
Jakob Schlyter
(jakob@kirei.se)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)