Using Secure DNS to Associate Certificates with Domain Names For TLS
draft-hoffman-keys-linkage-from-dns-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Paul E. Hoffman , Jakob Schlyter , Warren "Ace" Kumari , Adam Langley | ||
Last updated | 2010-10-04 | ||
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
TLS and DTLS use certificates for authenticating the server. Users want their applications to verify that the certificate provided by the TLS server is in fact associated with the domain name they expect. Instead of trusting a certificate authority to have made this association correctly, the user might instead trust the authoritative DNS server for the domain name to make that association. This document describes how to use secure DNS to associate the TLS server's certificate with the the intended domain name.
Authors
Paul E. Hoffman
Jakob Schlyter
Warren "Ace" Kumari
Adam Langley
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)