DANE TLSA implementation and operational guidance
draft-ietf-dane-ops-02

The information below is for an old version of the document
Document Type Active Internet-Draft (dane WG)
Last updated 2014-01-15
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: Best Current Practice                       W. Hardaker
Expires: July 19, 2014                                           Parsons
                                                        January 15, 2014

           DANE TLSA implementation and operational guidance
                         draft-ietf-dane-ops-02

Abstract

   This memo provides guidance to server operators to help ensure that
   clients will be able to authenticate a server's certificate chain via
   published TLSA records.  Guidance is also provided to clients for
   selecting reliable TLSA record parameters and using them for server
   authentication.  Finally, guidance is given to protocol designers who
   wish to make use of TLSA records when securing protocols using a
   combination of TLS and TLSA.

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 July 19, 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

Dukhovni & Hardaker       Expires July 19, 2014                 [Page 1]
Internet-Draft               DANE operations                January 2014

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  DANE TLSA record overview . . . . . . . . . . . . . . . . . .   4
     2.1.  Example TLSA record . . . . . . . . . . . . . . . . . . .   5
   3.  General DANE Guidelines . . . . . . . . . . . . . . . . . . .   5
     3.1.  TLS Requirements  . . . . . . . . . . . . . . . . . . . .   6
     3.2.  DANE DNS Record Size Guidelines . . . . . . . . . . . . .   6
     3.3.  Certificate Name Check Conventions  . . . . . . . . . . .   7
     3.4.  Service Provider and TLSA Publisher Synchronization . . .   8
     3.5.  TLSA Base Domain and CNAMEs . . . . . . . . . . . . . . .  10
     3.6.  Interaction with Certificate Transparency . . . . . . . .  10
     3.7.  Design Considerations for Protocols Using DANE  . . . . .  11
     3.8.  TLSA Records and Trust Anchor Digests . . . . . . . . . .  12
     3.9.  Trust anchor public keys  . . . . . . . . . . . . . . . .  13
   4.  Certificate Usage Specific DANE Guidelines  . . . . . . . . .  14
     4.1.  Certificate Usage DANE-EE(3) Guidelines . . . . . . . . .  14
     4.2.  Certificate Usage DANE-TA(2) Guidelines . . . . . . . . .  14
     4.3.  Certificate Usage PKIX-EE(1) Guidelines . . . . . . . . .  15
     4.4.  Certificate Usage PKIX-TA(0) Guidelines . . . . . . . . .  15
   5.  Note on DNSSEC security . . . . . . . . . . . . . . . . . . .  16
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   Section 2 of [RFC6698] specifies a new "TLSA" DNS resource record
   which associates with a TLS transport endpoint the 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 CA PKI.

   [RFC6698] defines 24 combinations of TLSA record parameters.
   Additional complexity arises when the TLS transport endpoint is
   obtained indirectly via SRV, MX and CNAME records or other mechanisms
   that map an abstract service domain to a concrete server domain.
Show full document text