Updates to and Operational Guidance for the DANE Protocol
draft-ietf-dane-ops-04

The information below is for an old version of the document
Document Type Active Internet-Draft (dane WG)
Last updated 2014-06-23
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DANE                                                         V. Dukhovni
Internet-Draft                                              Unaffiliated
Intended status: Standards Track                             W. Hardaker
Expires: December 26, 2014                                       Parsons
                                                           June 24, 2014

       Updates to and Operational Guidance for the DANE Protocol
                         draft-ietf-dane-ops-04

Abstract

   This memo clarifies and updates the DANE TLSA protocol based on
   implementation experience since the publication of the original
   specification [RFC6698].  It also contains guidance for DANE
   implementers and operators.

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 http://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 26, 2014.

Copyright Notice

   Copyright (c) 2014 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
   (http://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.

Dukhovni & Hardaker     Expires December 26, 2014               [Page 1]
Internet-Draft               DANE operations                   June 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  DANE TLSA record overview . . . . . . . . . . . . . . . . . .   4
     2.1.  Example TLSA record . . . . . . . . . . . . . . . . . . .   6
   3.  TLS Requirements  . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Certificate-Usage-specific DANE updates and guidelines  . . .   6
     4.1.  Certificate Usage DANE-EE(3)  . . . . . . . . . . . . . .   6
     4.2.  Certificate Usage DANE-TA(2)  . . . . . . . . . . . . . .   8
     4.3.  Certificate Usage PKIX-EE(1)  . . . . . . . . . . . . . .  10
     4.4.  Certificate Usage PKIX-TA(0)  . . . . . . . . . . . . . .  11
   5.  Service Provider and TLSA Publisher Synchronization . . . . .  12
   6.  TLSA Base Domain and CNAMEs . . . . . . . . . . . . . . . . .  14
   7.  TLSA Publisher requirements . . . . . . . . . . . . . . . . .  15
   8.  Digest algorithm agility  . . . . . . . . . . . . . . . . . .  18
   9.  General DANE Guidelines . . . . . . . . . . . . . . . . . . .  19
     9.1.  DANE DNS Record Size Guidelines . . . . . . . . . . . . .  19
     9.2.  Certificate Name Check Conventions  . . . . . . . . . . .  20
     9.3.  Design Considerations for Protocols Using DANE  . . . . .  21
   10. Interaction with Certificate Transparency . . . . . . . . . .  22
   11. Note on DNSSEC security . . . . . . . . . . . . . . . . . . .  23
   12. Summary of updates to RFC6698 . . . . . . . . . . . . . . . .  23
   13. Security Considerations . . . . . . . . . . . . . . . . . . .  24
   14. IANA considerations . . . . . . . . . . . . . . . . . . . . .  25
   15. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  25
   16. References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     16.1.  Normative References . . . . . . . . . . . . . . . . . .  25
     16.2.  Informative References . . . . . . . . . . . . . . . . .  26
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  26

1.  Introduction

   [RFC6698] specifies a new DNS resource record "TLSA" which associates
   with a TLS transport endpoint corresponding trusted leaf or issuing
   authority certificates or public keys.  DNSSEC-validated DANE TLSA
   records can be used to augment or replace the trust model of the
   existing public Certification Authority (CA) Public Key
   Infrastructure (PKI).

   [RFC6698] defines three TLSA record fields with respectively 4, 2 and
   3 specified values that yield 24 distinct combinations of TLSA record
   types.  So many options can lead to implementation and operational
   complexity.  This memo will recommend best-practice choices to
Show full document text