The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
draft-ietf-dane-protocol-20

The information below is for an old version of the document
Document Type Active Internet-Draft (dane WG)
Authors Paul Hoffman  , Jakob Schlyter 
Last updated 2012-05-10 (latest revision 2012-04-29)
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Warren Kumari
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Stephen Farrell
IESG note Warren Kumari (warren@kumari.net) is acting as the Document Shepherd.
Send notices to dane-chairs@tools.ietf.org, draft-ietf-dane-protocol@tools.ietf.org
Network Working Group                                         P. Hoffman
Internet-Draft                                            VPN Consortium
Intended status: Standards Track                             J. Schlyter
Expires: October 31, 2012                                       Kirei AB
                                                          April 29, 2012

 The DNS-Based Authentication of Named Entities (DANE) Transport Layer
                     Security (TLS) Protocol: TLSA
                      draft-ietf-dane-protocol-20

Abstract

   Encrypted communication on the Internet often uses Transport Level
   Security (TLS), which depends on third parties to certify the keys
   used.  This document improves on that situation by enabling the
   administrators of domain names to specify the keys used in that
   domain's TLS servers.  This requires matching improvements in TLS
   client software, but no change in TLS server software.

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 October 31, 2012.

Copyright Notice

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

Hoffman & Schlyter      Expires October 31, 2012                [Page 1]
Internet-Draft      DNS-Based Authentication for TLS          April 2012

   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.

Hoffman & Schlyter      Expires October 31, 2012                [Page 2]
Internet-Draft      DNS-Based Authentication for TLS          April 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Background and Motivation  . . . . . . . . . . . . . . . .  4
     1.2.  Securing the Association of a Domain Name with a
           Server's Certificate . . . . . . . . . . . . . . . . . . .  5
     1.3.  Method For Securing Certificate Associations . . . . . . .  6
     1.4.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  7
   2.  The TLSA Resource Record . . . . . . . . . . . . . . . . . . .  7
     2.1.  TLSA RDATA Wire Format . . . . . . . . . . . . . . . . . .  8
       2.1.1.  The Certificate Usage Field  . . . . . . . . . . . . .  8
       2.1.2.  The Selector Field . . . . . . . . . . . . . . . . . .  9
       2.1.3.  The Matching Type Field  . . . . . . . . . . . . . . . 10
       2.1.4.  The Certificate Association Data Field . . . . . . . . 10
     2.2.  TLSA RR Presentation Format  . . . . . . . . . . . . . . . 10
     2.3.  TLSA RR Examples . . . . . . . . . . . . . . . . . . . . . 11
   3.  Domain Names for TLSA Certificate Associations . . . . . . . . 11
   4.  Use of TLSA Records in TLS . . . . . . . . . . . . . . . . . . 12
     4.1.  Usable Certificate Associations  . . . . . . . . . . . . . 12
   5.  TLSA and DANE Use Cases and Requirements . . . . . . . . . . . 13
   6.  Mandatory-to-Implement Features  . . . . . . . . . . . . . . . 15
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 15
     7.1.  TLSA RRtype  . . . . . . . . . . . . . . . . . . . . . . . 16
     7.2.  TLSA Certificate Usages  . . . . . . . . . . . . . . . . . 16
     7.3.  TLSA Selectors . . . . . . . . . . . . . . . . . . . . . . 16
     7.4.  TLSA Matching Types  . . . . . . . . . . . . . . . . . . . 17
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
     8.1.  Comparing DANE to Public CAs . . . . . . . . . . . . . . . 18
     8.2.  DNS Caching  . . . . . . . . . . . . . . . . . . . . . . . 19
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 20
     10.2. Informative References . . . . . . . . . . . . . . . . . . 21
   Appendix A.  Operational Considerations for Deploying TLSA
Show full document text