DNS Resolver Discovery Protocol (DRDP)
draft-mglt-add-rdp-isp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Daniel Migault | ||
| Last updated | 2021-01-29 (Latest revision 2020-07-28) | ||
| 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 DNS Resolving service Discovery Protocol (DRDP) enables to discover resolving services available and eventually upgrade to an encrypted resolving service. DRDP requires a resolving domain or a pointer to a list of resolving domains. Currently ISP or CPEs do not advertise resolving domain or pointers to resolving domains which does not make possible for a DNS client to discover potential resolving services - such as encrypted DNS for example - made available by the ISP. Instead, ISPs or CPE advertise via DHCP the IP address of the host with a IA Address Option [RFC3315] and the IP addresses of the resolver provided by the ISP with Recursive Name Server option [RFC3646]. This document describes a procedure for a DNS client to derive resolving domains from the legacy configuration of the host. This is expected to ease the deployment of encrypted DNS from ISP as it will enable OS, applications to discover resolving service put in place by the ISP even though the CPE has not been upgraded.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)