DNS over Foo Discovery Mechanism
draft-mglt-dprive-add-dofoo-discovery-00

Document Type Active Internet-Draft (individual)
Last updated 2020-01-23
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
dnsop                                                         D. Migault
Internet-Draft                                                  Ericsson
Intended status: Informational                          January 23, 2020
Expires: July 26, 2020

                    DNS over Foo Discovery Mechanism
                draft-mglt-dprive-add-dofoo-discovery-00

Abstract

   This document describes a mechanism that enables a DNS client to
   discover other DNS alternatives such as DoT or DoH for one specific
   domain.  This document also extends this discovery mechanism to an
   Internet wide of open resolvers search - though this is expected to
   be described further in a separate document.  While search are always
   initiated by the DNS client, this document also indicates how a
   resolver MAY indicate a DNS client its preference for using
   alternative flavors of transport layer.

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 July 26, 2020.

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

Migault                   Expires July 26, 2020                 [Page 1]
Internet-Draft          DoFoo Discovery Mechanism           January 2020

   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.  Discovery mechanism associated to one domain  . . . . . . . .   2
     3.1.  Infering domain from resolvers IP address . . . . . . . .   5
   4.  Resolver advertising other service sub type . . . . . . . . .   5
   5.  Migration to service sub types  . . . . . . . . . . . . . . .   6
   6.  Service discovery over the Internet . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
     7.1.  Use of protected channel is RECOMMENDED . . . . . . . . .   7
     7.2.  DNSSEC is RECOMMENDED . . . . . . . . . . . . . . . . . .   8
     7.3.  TLSA is RECOMMENDED . . . . . . . . . . . . . . . . . . .   8
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   10. Appendix  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

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 BCP 14
   [RFC2119] [RFC8174] when, and only when, they appear in all capitals,
   as shown here.

2.  Introduction

3.  Discovery mechanism associated to one domain

   The discovery mechanism is intended to enable a DNS client to
   discover what are the resolvers options available as well as how to
   further use these resolvers.

   The procedure is based on service discovery [RFC8145] and the overall
   procedure consists in finding various instances of the service
   "rdns".  The resolution service is designated as "rdns" and differs
   from the service "domain" defined by IANA.  The motivation for
   creating a new service is that "domain" is associated to port 53 as
   well as TCP and UDP and designates both the authoritative as well as
   the resoling service.  On the other hand the service "rdns" is
   expected to be limited to the DNS resolution service that can have
   various transport flavors including using different ports.

Migault                   Expires July 26, 2020                 [Page 2]
Internet-Draft          DoFoo Discovery Mechanism           January 2020

   In this document, the service "rdns" is associated to a domain such
Show full document text