Adaptive DNS Resolver Discovery
draft-pauly-add-resolver-discovery-01
Network Working Group T. Pauly
Internet-Draft E. Kinnear
Intended status: Standards Track Apple Inc.
Expires: 14 January 2021 C.A. Wood
Cloudflare
P. McManus
Fastly
T. Jensen
Microsoft
13 July 2020
Adaptive DNS Resolver Discovery
draft-pauly-add-resolver-discovery-01
Abstract
This document defines a method for dynamically discovering resolvers
that support encrypted transports, and introduces the concept of
designating a resolver to be used for a subset of client queries
based on domain. This method is intended to work both for locally-
hosted resolvers and resolvers accessible over the broader Internet.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 14 January 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Pauly, et al. Expires 14 January 2021 [Page 1]
Internet-Draft ADNS Discovery July 2020
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Specification of Requirements . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Designated Resolvers . . . . . . . . . . . . . . . . . . . . 3
3.1. Designating with Service Binding DNS Records . . . . . . 4
3.2. Additional Designation with PvD JSON . . . . . . . . . . 5
3.3. Confirmation of Designation with Zone Apex PvD . . . . . 6
3.4. Confirmation of Designation with TLS Certificates . . . . 8
4. Explicit Discovery of Local Resolvers . . . . . . . . . . . . 9
5. Discovery of DoH Capabilities for Direct Resolvers . . . . . 9
6. Server Deployment Considerations . . . . . . . . . . . . . . 10
6.1. Single Content Provider . . . . . . . . . . . . . . . . . 10
6.2. Multiple Content Providers . . . . . . . . . . . . . . . 10
6.3. Avoid Narrow Deployments . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9.1. DoH Template PvD Key . . . . . . . . . . . . . . . . . . 12
9.2. Trusted Names PvD Key . . . . . . . . . . . . . . . . . . 12
9.3. DoH URI Template DNS Service Parameter . . . . . . . . . 13
9.4. Special Use Domain Name "resolver.arpa" . . . . . . . . . 13
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
11.1. Normative References . . . . . . . . . . . . . . . . . . 13
11.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Rationale for using SVCB records . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
When clients need to resolve names into addresses in order to
establish networking connections, they traditionally use by default
the DNS resolver that is provisioned by the local network along with
their IP address [RFC2132] [RFC8106]. Alternatively, they can use a
Show full document text