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

The information below is for an old version of the document
Document Type Active Internet-Draft (dane WG)
Last updated 2013-10-21
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: April 24, 2014                                          Parsons
                                                        October 21, 2013

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

Abstract

   This memo provides operational 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
   how to use them for server authentication.  Finally, guidance is
   given to protocol designers who wish to make use of TLSA records when
   securing protocols using a TLS and TLSA combination.

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 April 24, 2014.

Copyright Notice

   Copyright (c) 2013 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 April 24, 2014                 [Page 1]
Internet-Draft               DANE operations                October 2013

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

1.  Introduction

   The Domain Name System Security Extensions (DNSSEC) add data origin
   authentication and data integrity to the Domain Name System.  DNSSEC
   is defined in [RFC4033], [RFC4034] and [RFC4035].

   In the context of this memo, channel security is assumed to be
   provided by TLS or DTLS.  The Transport Layer Security (TLS) and
   Datagram Transport Layer Security (DTLS) protocols provide secured
   TCP and UDP communication over the Internet Protocol.  By convention,
Show full document text