Using HTTPS for Privacy Between DNS Stub and Recursive Resolvers
draft-hoffman-dprive-dns-tls-https-00

Document Type Expired Internet-Draft (individual)
Last updated 2015-04-25 (latest revision 2014-10-22)
Replaces draft-hoffman-dprive-dns-tls-https-latest
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-dprive-dns-tls-https-00.txt

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 easily wrap DNS queries in HTTP requests and interpret DNS responses in the HTTP respones; the HTTP here is always run under TLS on port 443. Discussion of this draft should take place in the DPRIVE WG.

Authors

Paul Hoffman (paul.hoffman@vpnc.org)

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