DNS Resolving service Discovery Protocol (DRDP)
draft-mglt-add-rdp-03

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 Resolving service Discovery Protocol (DRDP)
                         draft-mglt-add-rdp-03

Abstract

   This document describes the DNS Resolver Discovery Protocol (DRDP)
   that enables a DNS client to discover various available local and
   global resolving service.  The discovery is primarily initiated by a
   DNS client, but a resolving service may also inform the DNS client
   other resolving services are available and eventually preferred.

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

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

Table of Contents

   1.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Pointer to a list of Resolving Domains  . . . . . . . . . . .   5
   6.  Discovery of Resolving Services . . . . . . . . . . . . . . .   6
   7.  TTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  SvcParamKey . . . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Resolver advertising other service sub type . . . . . . . . .   8
   10. Migration to service sub types  . . . . . . . . . . . . . . .   8
   11. Security Considerations . . . . . . . . . . . . . . . . . . .   8
     11.1.  Use of protected channel is RECOMMENDED  . . . . . . . .   8
     11.2.  DNSSEC is RECOMMENDED  . . . . . . . . . . . . . . . . .   9
     11.3.  TLSA is RECOMMENDED  . . . . . . . . . . . . . . . . . .  10
   12. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  10
   13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   15. Appendices  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     15.1.  DRDP Requirements  . . . . . . . . . . . . . . . . . . .  12
     15.2.  Discovery of specific service instance . . . . . . . . .  13
   16. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     16.1.  Normative References . . . . . . . . . . . . . . . . . .  14
     16.2.  Informative References . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

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

   A DNS client can proceed to DNS resolution using various resolving
   services.  These services can be local or global and can use a wide
   range of DNS transport protocols such as, for example, standard DNS
   [RFC1035], DNS over TLS [RFC7858] or DNS over HTTPS [RFC8484].  The
   local scope of these services may take various forms.  For example,
   it could be associated to a network perspective ( restricted to the
   network the DNS client is connected to ) or to an application
   perspective ( restricted to some domain names ).

   The purpose of the DNS Resolving service Discovery Protocol (DRDP) is
Show full document text