DNS Resolver Discovery Protocol (DRDP)
draft-mglt-add-rdp-isp-00

Document Type Active Internet-Draft (individual)
Author Daniel Migault 
Last updated 2020-07-28
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
add                                                           D. Migault
Internet-Draft                                                  Ericsson
Intended status: Informational                             July 28, 2020
Expires: January 29, 2021

                 DNS Resolver Discovery Protocol (DRDP)
                       draft-mglt-add-rdp-isp-00

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.

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

Migault                 Expires January 29, 2021                [Page 1]
Internet-Draft                    DRDP                         July 2020

   This Internet-Draft will expire on January 29, 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.  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.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  IP to Pointers  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  RD Pointer from Interface Address (IA)  . . . . . . . . .   5
     3.2.  RD Pointer from Resolver IP address . . . . . . . . . . .   5
     3.3.  Cross Verification  . . . . . . . . . . . . . . . . . . .   6
     3.4.  Configuration expected by the network operator  . . . . .   6
   4.  Security Consideration  . . . . . . . . . . . . . . . . . . .   6
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Introduction

   This document describes how a DNS client can discover resolving
   services made available by a network operator.  The procedure
   requires minimal changes from the network operator and results in the
   encryption of a significant portion of the DNS traffic.  The
   limitation relies on the CPE being upgraded to support encrypted DNS
   to resolve local scope names.

Migault                 Expires January 29, 2021                [Page 2]
Internet-Draft                    DRDP                         July 2020

   The considered architecture that is currently deployed is represented
   below.

   In most architecture, the CPE co-hosts an authoritative server for
   the local zones (such as .home.arpa or .local) that are not
   represented in the global DNS architecture.  The CPE in most common
Show full document text