DNS over HTTPS (DoH) Considerations for Operator Networks
draft-doh-reid-operator-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Andy Fidler , Bert Hubert , Jason Livingood , Jim Reid , Nicolai Leymann | ||
| Last updated | 2020-03-13 (Latest revision 2019-09-10) | ||
| Replaces | draft-reid-doh-operator | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
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
Bert Hubert
Jason Livingood
Jim Reid
Nicolai Leymann
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)