Transport Layer Security (TLS) False Start
draft-ietf-tls-falsestart-01

The information below is for an old version of the document
Document Type Active Internet-Draft (tls WG)
Last updated 2016-04-28 (latest revision 2015-11-02)
Replaces draft-bmoeller-tls-falsestart
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Sean Turner
Shepherd write-up Show (last changed 2016-03-21)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Needs a YES.
Responsible AD Stephen Farrell
Send notices to "Sean Turner" <sean@sn3rd.com>
IANA IANA review state IANA OK - No Actions Needed
TLS Working Group                                             A. Langley
Internet-Draft                                               N. Modadugu
Intended status: Experimental                                 B. Moeller
Expires: May 5, 2016                                              Google
                                                        November 2, 2015

               Transport Layer Security (TLS) False Start
                      draft-ietf-tls-falsestart-01

Abstract

   This document specifies an optional behavior of TLS client
   implementations, dubbed False Start.  It affects only protocol
   timing, not on-the-wire protocol data, and can be implemented
   unilaterally.  A TLS False Start reduces handshake latency to one
   round trip.

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 May 5, 2016.

Copyright Notice

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

Langley, et al.            Expires May 5, 2016                  [Page 1]
Internet-Draft               TLS False Start               November 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  False Start Compatibility . . . . . . . . . . . . . . . . . .   4
   4.  Client-side False Start . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
     5.1.  Symmetric Cipher  . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Protocol Version  . . . . . . . . . . . . . . . . . . . .   7
     5.3.  Key Exchange and Client Certificate Type  . . . . . . . .   7
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  Implementation Notes . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  Introduction

   A full handshake in TLS protocol versions up to TLS 1.2 [RFC5246]
   requires two full protocol rounds (four flights) before the handshake
   is complete and the protocol parties may begin to send application
   data.  Thus, using TLS can add a latency penalty of two network
   round-trip times for application protocols in which the client sends
   data first, such as HTTP [RFC2616].

Langley, et al.            Expires May 5, 2016                  [Page 2]
Internet-Draft               TLS False Start               November 2015

      Client                                               Server

      ClientHello                  -------->
                                                      ServerHello
                                                     Certificate*
                                               ServerKeyExchange*
                                              CertificateRequest*
                                   <--------      ServerHelloDone
      Certificate*
      ClientKeyExchange
      CertificateVerify*
      [ChangeCipherSpec]
      Finished                     -------->
                                               [ChangeCipherSpec]
                                   <--------             Finished
      Application Data             <------->     Application Data
Show full document text