DNS over HTTPS (DoH) Considerations for Operator Networks

Document Type Replaced Internet-Draft (individual)
Authors Andy Fidler  , Bert Hubert  , Jason Livingood  , Jim Reid  , Nicolai Leymann 
Last updated 2019-09-10 (latest revision 2019-03-09)
Replaces draft-reid-operator-doh
Replaced by draft-doh-reid-operator
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-doh-reid-operator
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


The introduction of DNS over HTTPS (DoH), defined in RFC8484, presents a number of challenges to network operators. These are described in this document. The objective is to document the problem space and make suggestions that could help inform network operators on how to take account of DoH deployment. This document also identifies topics that may require further analysis.


Andy Fidler (andrew.fidler@bt.com)
Bert Hubert (bert.hubert@open-xchange.com)
Jason Livingood (Jason_Livingood@comcast.com)
Jim Reid (jim@rfc1035.com)
Nicolai Leymann (n.leymann@telekom.de)

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