Token Binding for 0-RTT TLS 1.3 Connections
draft-ietf-tokbind-tls13-0rtt-02

Document Type Active Internet-Draft (tokbind WG)
Last updated 2017-06-28
Replaces draft-nharper-0-rtt-token-binding
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Token Binding Working Group                                    N. Harper
Internet-Draft                                               Google Inc.
Intended status: Standards Track                           June 28, 2017
Expires: December 30, 2017

              Token Binding for 0-RTT TLS 1.3 Connections
                    draft-ietf-tokbind-tls13-0rtt-02

Abstract

   This document describes how Token Binding can be used in the 0-RTT
   data of a TLS 1.3 connection.  This involves a new TLS extension to
   negotiate and indicate the use of Token Binding in 0-RTT data.  A
   TokenBindingMessage sent in 0-RTT data has different security
   properties than one sent after the TLS handshake has finished, which
   this document also describes.

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 December 30, 2017.

Copyright Notice

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

Harper                  Expires December 30, 2017               [Page 1]
Internet-Draft         Token Binding in 0-RTT data             June 2017

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  TokenBinding Signature Definition . . . . . . . . . . . . . .   3
     2.1.  Selecting Which Exporter Secret to Use  . . . . . . . . .   3
   3.  Negotiation . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Indicating Use of 0-RTT Token Binding . . . . . . . . . .   4
     3.2.  Token Binding Negotiation TLS Extension . . . . . . . . .   4
     3.3.  Client Processing Rules . . . . . . . . . . . . . . . . .   4
     3.4.  Server Processing Rules . . . . . . . . . . . . . . . . .   5
   4.  Implementation Considerations . . . . . . . . . . . . . . . .   6
     4.1.  Not Implementing Token Binding on 0-RTT Connections . . .   6
     4.2.  Adding Support for Token Binding on 0-RTT Connections . .   7
     4.3.  Implementation Challenges . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
     6.1.  Proof of Possession of Token Binding Key  . . . . . . . .   8
     6.2.  Exporter Replayability  . . . . . . . . . . . . . . . . .   8
     6.3.  Replay Mitigations  . . . . . . . . . . . . . . . . . . .   9
       6.3.1.  Server Mitigations  . . . . . . . . . . . . . . . . .   9
       6.3.2.  Client Mitigations  . . . . . . . . . . . . . . . . .  10
     6.4.  Early Data Ticket Age Window  . . . . . . . . . . . . . .  10
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Token Binding ([I-D.ietf-tokbind-protocol]) cryptographically binds
   security tokens (e.g.  HTTP cookies, OAuth tokens) to the TLS layer
   on which they are presented.  It does so by signing an [RFC5705]
   exporter value from the TLS connection.  TLS 1.3 introduces a new
   mode that allows a client to send application data on its first
   flight.  If this 0-RTT data contains a security token, then a client
   using Token Binding would want to prove possession of its Token
   Binding private key so that the server can verify the binding.  The
   [RFC5705]-style exporter provided by TLS 1.3 cannot be run until the
   handshake has finished.  TLS 1.3 also provides an exporter that can
Show full document text