TLS Ticket Requests
draft-wood-tls-ticketrequests-00

Document Type Active Internet-Draft (individual)
Last updated 2018-04-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            C. Wood
Internet-Draft                                                  T. Pauly
Intended status: Informational                               D. Schinazi
Expires: October 14, 2018                                     Apple Inc.
                                                          April 12, 2018

                          TLS Ticket Requests
                  draft-wood-tls-ticketrequests-00

Abstract

   TLS session tickets enable stateless connection resumption for
   clients without server-side per-client state.  Servers vend session
   tickets to clients, at their discretion, upon connection
   establishment.  Clients store and use tickets when resuming future
   connections.  Moreover, clients should use tickets at most once for
   session resumption, especially if such keying material protects early
   application data.  Single-use tickets bound the number of parallel
   connections a client may initiate by the number of tickets received
   from a given server.  To address this limitation, this document
   describes a mechanism by which clients may request tickets as needed
   during a connection.

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 14, 2018.

Copyright Notice

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

Wood, et al.            Expires October 14, 2018                [Page 1]
Internet-Draft             TLS Ticket Requests                April 2018

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Ticket Requests . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Negotiation . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   As per [RFC5077], and as described in [I-D.ietf-tls-tls13], TLS
   servers send clients session tickets at their own discretion in
   NewSessionTicket messages.  Clients are in complete control of how
   many tickets they may use when establishing future and subsequent
   connections.  For example, clients may open multiple TLS connections
   to the same server for HTTP, or may race TLS connections across
   different network interfaces.  The latter is especially useful in
   transport systems that implement Happy Eyeballs [RFC8305].  Since
   connection concurrency and resumption is controlled by clients, a
   mechanism to request tickets on demand is desirable.

   This document specifies a new TLS post-handshake message -
   TicketRequest - that may be used to request tickets via
   NewSessionTicket messages in TLS 1.3.  Ticket requests may carry
   optional application-specific contexts to define the ways in which
   tickets may be used.  NewSessionTicket responses reciprocate this
   application context in an extension.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119] [RFC8174] when, and only when, they appear in all capitals,
   as shown here.

Wood, et al.            Expires October 14, 2018                [Page 2]
Internet-Draft             TLS Ticket Requests                April 2018
Show full document text