Using Secure DNS to Associate Certificates with Domain Names For TLS
draft-ietf-dane-protocol-16

The information below is for an old version of the document
Document Type Active Internet-Draft (dane WG)
Authors Jakob Schlyter  , Paul Hoffman 
Last updated 2012-02-08 (latest revision 2012-02-04)
Stream Internent Engineering Task Force (IETF)
Formats pdf htmlized (tools) 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)
Network Working Group                                         P. Hoffman
Internet-Draft                                            VPN Consortium
Intended status: Standards Track                             J. Schlyter
Expires: August 11, 2012                                        Kirei AB
                                                        February 8, 2012

  Using Secure DNS to Associate Certificates with Domain Names For TLS
                      draft-ietf-dane-protocol-16

Abstract

   TLS and DTLS use PKIX certificates for authenticating the server.
   Users want their applications to verify that the certificate provided
   by the TLS server is in fact associated with the domain name they
   expect.  TLSA provides bindings of keys to domains that are asserted
   not by external entities, but by the entities that operate the DNS.
   This document describes how to use secure DNS to associate the TLS
   server's certificate with the intended domain name.

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 August 11, 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 August 11, 2012                [Page 1]
Internet-Draft        DNS Cert Association for TLS         February 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 August 11, 2012                [Page 2]
Internet-Draft        DNS Cert Association for TLS         February 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Certificate Associations . . . . . . . . . . . . . . . . .  4
     1.2.  Securing Certificate Associations  . . . . . . . . . . . .  5
     1.3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  The TLSA Resource Record . . . . . . . . . . . . . . . . . . .  5
     2.1.  TLSA RDATA Wire Format . . . . . . . . . . . . . . . . . .  6
       2.1.1.  The Certificate Usage Field  . . . . . . . . . . . . .  6
       2.1.2.  The Selector Field . . . . . . . . . . . . . . . . . .  7
       2.1.3.  The Matching Type Field  . . . . . . . . . . . . . . .  7
       2.1.4.  The Certificate Association Data Field . . . . . . . .  7
     2.2.  TLSA RR Presentation Format  . . . . . . . . . . . . . . .  7
     2.3.  TLSA RR Examples . . . . . . . . . . . . . . . . . . . . .  8
   3.  Domain Names for TLS Certificate Associations  . . . . . . . .  8
   4.  Semantics and Features of TLSA Certificate Usages  . . . . . .  9
     4.1.  Pass PKIX Validation and Chain Through CA  . . . . . . . .  9
     4.2.  Pass PKIX Validation and Match End Entity Certificate  . .  9
     4.3.  Pass PKIX Validation and Use Trust Anchor  . . . . . . . .  9
     4.4.  Match Certificate  . . . . . . . . . . . . . . . . . . . .  9
   5.  Use of TLS Certificate Associations in TLS . . . . . . . . . . 10
   6.  TLSA and DANE Use Cases and Requirements . . . . . . . . . . . 11
   7.  Mandatory-to-Implement Algorithms  . . . . . . . . . . . . . . 13
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
     8.1.  TLSA RRtype  . . . . . . . . . . . . . . . . . . . . . . . 13
     8.2.  TLSA Usages  . . . . . . . . . . . . . . . . . . . . . . . 14
     8.3.  TLSA Selectors . . . . . . . . . . . . . . . . . . . . . . 14
     8.4.  TLSA Matching Types  . . . . . . . . . . . . . . . . . . . 14
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 16
     11.2. Informative References . . . . . . . . . . . . . . . . . . 17
Show full document text