DNS-over-TLS for insecure delegations
draft-bretelle-dprive-dot-for-insecure-delegations-00

Document Type Active Internet-Draft (individual)
Last updated 2018-09-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Working Group                                        M. Bretelle
Internet-Draft                                                  Facebook
Intended status: Standards Track                      September 27, 2018
Expires: March 31, 2019

                 DNS-over-TLS for insecure delegations
         draft-bretelle-dprive-dot-for-insecure-delegations-00

Abstract

   This document describes an alternate mechanism to DANE ([RFC6698]) in
   order to authenticate a DNS-over-TLS (DoT [RFC7858]) authoritative
   server by not making DNSSEC a hard requirement, making DoT server
   authentication available for insecure delegations.

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 March 31, 2019.

Copyright Notice

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

Bretelle                 Expires March 31, 2019                 [Page 1]
Internet-Draft        dot-for-insecure-delegations        September 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Authenticating an insecure delegation . . . . . . . . . . . .   3
     3.1.  Public Key Infranstructure (PKIX) . . . . . . . . . . . .   3
     3.2.  Simple Public-Key Infrastructure (SPKI) . . . . . . . . .   3
     3.3.  Authenticating from the parent  . . . . . . . . . . . . .   4
       3.3.1.  Example . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  DSPKI Resource Record . . . . . . . . . . . . . . . . . . . .   5
     4.1.  DSPKI RDATA Format  . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   This document describes an alternate mechanism to [RFC6698] as
   described in [I-D.bortzmeyer-dprive-resolver-to-auth] Section 2
   extending the authentication of DoT [RFC7858] to insecure delegations
   and therefore enabling the onboarding of DoT authoritative servers
   without the requirement for the authorities to support DNSSEC
   ([RFC4033], [RFC4034], and [RFC4035]).  To do so, this document
   introduce the Delegation SPKI (DSPKI) resource record, its purpose,
   usage and format.

2.  Terminology

   A server that supports DNS-over-TLS is called a "DoT server" to
   differentiate it from a "DNS Server" (one that provides DNS service
   over any other protocol), likewise, a client that supports this
   protocol is called a "DoT client"

   A secure delegation ([RFC4956] Section 2) is a signed name containing
   a delegation (NS RRset), and a signed DS RRset, signifying a
   delegation to a signed zone.

   An insecure delegation ([RFC4956] Section 2) is a signed name
   containing a delegation (NS RRset), but lacking a DS RRset,
   signifying a delegation to an unsigned subzone.

   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.

Bretelle                 Expires March 31, 2019                 [Page 2]
Internet-Draft        dot-for-insecure-delegations        September 2018

3.  Authenticating an insecure delegation

   To authenticate a DoT server of a secure delegation, it is possible
   to use the TLSA resource record [RFC6698] of the nameserver as
Show full document text