Centralized DNS over HTTPS (DoH) Implementation Issues and Risks
draft-livingood-doh-implementation-risks-issues-04

Document Type Expired Internet-Draft (individual)
Last updated 2020-03-19 (latest revision 2019-09-16)
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 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-livingood-doh-implementation-risks-issues-04.txt

Abstract

The DNS over HTTPS (DoH) protocol is specified in RFC8484. This document considers Centralized DoH deployment, which seems one likely way that DoH may be implemented, based on recent industry discussions and testing. This describes that implementation model, as well the potential associated risks and issues. The document also makes recommendations pertaining to the implementation of DoH, as well as recommendations for further study prior to widespread adoption.

Authors

Jason Livingood (Jason_Livingood@comcast.com)
Manos Antonakakis (manos@gatech.edu)
Bob Sleigh (bob.sleigh@bt.com)
Alister Winfield (alister.winfield@sky.uk)

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