DNS Server Selection: DNS Server Information with Assertion Token
draft-reddy-add-server-policy-selection-08

Document Type Active Internet-Draft (individual)
Authors Tirumaleswar Reddy.K  , Dan Wing  , Michael Richardson  , Mohamed Boucadair 
Last updated 2021-03-29
Replaces draft-reddy-dprive-dprive-privacy-policy
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 WG                                                          T. Reddy
Internet-Draft                                                    McAfee
Intended status: Standards Track                                 D. Wing
Expires: September 30, 2021                                       Citrix
                                                           M. Richardson
                                                Sandelman Software Works
                                                            M. Boucadair
                                                                  Orange
                                                          March 29, 2021

   DNS Server Selection: DNS Server Information with Assertion Token
               draft-reddy-add-server-policy-selection-08

Abstract

   The document defines a mechanism that is meant to communicate DNS
   resolver information to DNS clients for use as a criteria for server
   selection decisions.  Such an information that is cryptographically
   signed to attest its authenticity is used for the selection of DNS
   resolvers.  Typically, evaluating the resolver information and the
   signatory, DNS clients with minimal or no human intervention can
   select the DNS servers for resolving domain names.

   This assertion is useful for encrypted DNS (e.g., DNS-over-TLS, DNS-
   over-HTTPS, or DNS-over-QUIC) servers that are either public
   resolvers or discovered in a local network.

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 September 30, 2021.

Reddy, et al.          Expires September 30, 2021               [Page 1]
Internet-Draft    DNS Server Info with Assertion Token        March 2021

Copyright Notice

   Copyright (c) 2021 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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Resolver Assertion Token (REAT): Overview . . . . . . . . . .   4
   4.  REAT Header . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  'typ' (Type) Header Parameter . . . . . . . . . . . . . .   6
     4.2.  'alg' (Algorithm) Header Parameter  . . . . . . . . . . .   6
     4.3.  'x5u' (X.509 URL) Header Parameter  . . . . . . . . . . .   6
     4.4.  An Example of REAT Header . . . . . . . . . . . . . . . .   7
   5.  REAT Payload  . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  JWT Defined Claims  . . . . . . . . . . . . . . . . . . .   7
       5.1.1.  'iat' - Issued At Claim . . . . . . . . . . . . . . .   7
       5.1.2.  'exp' - Expiration Time Claim . . . . . . . . . . . .   7
     5.2.  REAT Specific Claims  . . . . . . . . . . . . . . . . . .   8
       5.2.1.  DNS Server Identity Claims  . . . . . . . . . . . . .   8
       5.2.2.  'resinfo' (Resolver Information) Claim  . . . . . . .   8
       5.2.3.  An Example  . . . . . . . . . . . . . . . . . . . . .   9
   6.  REAT Signature  . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Extending REAT  . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Deterministic JSON Serialization  . . . . . . . . . . . . . .  10
     8.1.  Example REAT Deterministic JSON Form  . . . . . . . . . .  11
   9.  Using RESINFO Responses . . . . . . . . . . . . . . . . . . .  11
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  12
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     11.1.  Media Type Registration  . . . . . . . . . . . . . . . .  12
       11.1.1.  Media Type Registry Contents Additions Requested . .  12
     11.2.  JSON Web Token Claims Registration . . . . . . . . . . .  13
       11.2.1.  Registry Contents Additions Requested  . . . . . . .  13
Show full document text