Adaptive DNS Discovery Requirements
draft-pauly-add-requirements-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tommy Pauly , Eric Kinnear , Christopher A. Wood , Patrick McManus , Tommy Jensen | ||
| Last updated | 2020-08-21 | ||
| Replaced by | draft-box-add-requirements | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-box-add-requirements | |
| 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
This document describes several use cases for discovering DNS resolvers that support encrypted transports, and discusses how solutions for these use cases can be designed to use common mechanisms. It also considers the requirements for privacy and security when designing resolver discovery mechanisms.
Authors
Tommy Pauly
Eric Kinnear
Christopher A. Wood
Patrick McManus
Tommy Jensen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)