TLS Out-of-Band Public Key Validation
draft-ietf-tls-oob-pubkey-01

The information below is for an old version of the document
Document Type Active Internet-Draft (tls WG)
Last updated 2012-01-20 (latest revision 2012-01-07)
Replaces draft-wouters-tls-oob-pubkey
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IETF                                                          P. Wouters
Internet-Draft                                       No Hats Corporation
Intended status: Standards Track                              J. Gilmore
Expires: July 10, 2012
                                                               S. Weiler
                                                            SPARTA, Inc.
                                                              T. Kivinen
                                                               AuthenTec
                                                           H. Tschofenig
                                                  Nokia Siemens Networks
                                                        January 20, 2012

                 TLS Out-of-Band Public Key Validation
                    draft-ietf-tls-oob-pubkey-01.txt

Abstract

   This document specifies a new TLS certificate type for exchanging raw
   public keys in Transport Layer Security (TLS) and Datagram Transport
   Layer Security (DTLS) for use with out-of-band authentication.
   Currently, TLS authentication can only occur via PKIX or OpenPGP
   certificates.  By specifying a minimum resource for raw public key
   exchange, implementations can use alternative authentication methods.

   One such method is using DANE Resource Records secured by DNSSEC,
   Another use case is to provide authentication functionality when used
   with devices in a constrained environment that use whitelists and
   blacklists, as is the case with sensors and other embedded devices
   that are constrained by memory, computational, and communication
   limitations where the usage of PKIX is not feasible.

   The new certificate type specified can also be used to reduce the
   latency of a TLS client that is already in possession of a validated
   public key of the TLS server before it starts a (non-resumed) TLS
   handshake.

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

Wouters, et al.           Expires July 10, 2012                 [Page 1]
Internet-Draft        TLS OOB Public Key Validation         January 2012

   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 10, 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
   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.

Wouters, et al.           Expires July 10, 2012                 [Page 2]
Internet-Draft        TLS OOB Public Key Validation         January 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Motivation . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.2.  Applicability  . . . . . . . . . . . . . . . . . . . . . .  5
     1.3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Changes to the Handshake Message Contents  . . . . . . . . . .  5
     2.1.  Client Hello . . . . . . . . . . . . . . . . . . . . . . .  6
     2.2.  Server Hello . . . . . . . . . . . . . . . . . . . . . . .  7
     2.3.  Certificate Request  . . . . . . . . . . . . . . . . . . .  7
     2.4.  Other Handshake Messages . . . . . . . . . . . . . . . . .  8
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
   5.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . .  8
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  9
Show full document text