DNS over HTTPS (DoH) Considerations for Operator Networks
draft-reid-operator-doh-00

Document Type Replaced Internet-Draft (individual)
Last updated 2019-03-09
Replaced by draft-reid-doh-operator
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 Replaced by draft-reid-doh-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
https://www.ietf.org/archive/id/draft-reid-operator-doh-00.txt

Abstract

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.

Authors

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.)