DNS Resolver Information Self-publication
draft-sah-resolver-information-02

Document Type Active Internet-Draft (individual)
Last updated 2019-06-27
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda dnsop at IETF-105
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            P. Sood
Internet-Draft                                                    Google
Intended status: Standards Track                               R. Arends
Expires: December 29, 2019                                    P. Hoffman
                                                                   ICANN
                                                           June 27, 2019

               DNS Resolver Information Self-publication
                   draft-sah-resolver-information-02

Abstract

   This document describes methods for DNS resolvers to self-publish
   information about themselves, such as whether they perform DNSSEC
   validation or are available over transports other than what is
   defined in RFC 1035.  The information is returned as a JSON object.
   The names in this object are defined in an IANA registry that allows
   for light-weight registration.  Applications and operating systems
   can use the methods defined here to get the information from
   resolvers in order to make choices about how to send future queries
   to those resolvers.

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 December 29, 2019.

Copyright Notice

   Copyright (c) 2019 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

Sood, et al.            Expires December 29, 2019               [Page 1]
Internet-Draft            Resolver Information                 June 2019

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Retrieving Resolver Information by DNS  . . . . . . . . . . .   3
   3.  Retrieving Resolver Information by Well-Known URI . . . . . .   4
   4.  Contents of the Returned I-JSON Object  . . . . . . . . . . .   5
     4.1.  The "inventory" name  . . . . . . . . . . . . . . . . . .   6
     4.2.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  RESINFO RRtype  . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Registry for DNS Resolver Information . . . . . . . . . .   6
     5.3.  resolver-info Well-known URI  . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Historically, DNS stub resolvers typically communicated with the
   recursive resolvers in their configuration without needing to know
   anything about the features of the recursive resolvers.  More
   recently, recursive resolvers have different features that may cause
   stub resolvers to make choices about which configured resolver from
   its configuration to use, and also how to communicate with the
   recursive resolver (such as over different transports).  Thus stub
   resolvers need a way to get information from recursive resolvers
   about features that might affect the communication.

   This document specifies methods for stub resolvers to ask recursive
   resolvers for such information.  In short, a new RRtype is defined
   for stub resolvers to query using the DNS, and a new well-known URI
   is defined for stub resolvers to query using HTTP over TLS.

   The response from either method is the same: a JSON object.  The JSON
   object MUST use the I-JSON message format defined in [RFC7493].  Note
Show full document text