Skip to main content

Using TLS and ALPN for Privacy Between DNS Stub and Recursive Resolvers
draft-hoffman-dprive-dns-tls-alpn-latest-00

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Paul E. Hoffman
Last updated 2014-10-28 (Latest revision 2014-10-22)
Replaced by draft-hoffman-dprive-dns-tls-alpn
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-hoffman-dprive-dns-tls-alpn
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

DNS queries and responses can contain information that reveals important information about the person who caused the queries, and it would be better if eavesdroppers were unable to see DNS traffic. This document describes how to use TLS for encrypting DNS traffic between a system acting as a DNS stub resolver and a system acting as a DNS recursive resolver. It defines how to transport DNS queries and responses under TLS on port 443 using ALPN. Discussion of this draft should take place in the DPRIVE WG.

Authors

Paul E. Hoffman

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)