TLS Ticket Requests
draft-ietf-tls-ticketrequests-04
|
| Document |
Type |
|
Active Internet-Draft (tls WG)
|
|
Last updated |
|
2019-11-21
(latest revision 2019-11-04)
|
|
Replaces |
|
draft-wood-tls-ticketrequests
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
|
Additional URLs |
|
|
| Stream |
WG state
|
|
WG Document
Revised I-D Needed - Issue raised by WG
|
|
Document shepherd |
|
Sean Turner
|
|
Shepherd write-up |
|
Show
(last changed 2019-11-04)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Sean Turner <sean@sn3rd.com>
|
Network Working Group T. Pauly
Internet-Draft Apple Inc.
Intended status: Standards Track D. Schinazi
Expires: May 7, 2020 Google LLC
C. Wood
Apple Inc.
November 04, 2019
TLS Ticket Requests
draft-ietf-tls-ticketrequests-04
Abstract
TLS session tickets enable stateless connection resumption for
clients without server-side, per-client state. Servers vend an
arbitrary number of session tickets to clients, at their discretion,
upon connection establishment. Clients store and use tickets when
resuming future connections. This document describes a mechanism by
which clients can specify the desired number of tickets needed for
future connections. This extension aims to provide a means for
servers to determine the number of tickets to generate in order to
reduce ticket waste, while simultaneously priming clients for future
connection attempts.
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 https://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 7, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Pauly, et al. Expires May 7, 2020 [Page 1]
Internet-Draft TLS Ticket Requests November 2019
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://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 . . . . . . . . . . . . . . . . . . 3
2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Ticket Requests . . . . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
As per [RFC5077], and as described in [RFC8446], TLS servers vend
clients an arbitrary number of session tickets at their own
discretion in NewSessionTicket messages. There are two limitations
with this design. First, servers choose some (often hard-coded)
number of tickets vended per connection. Second, clients do not have
a way of expressing their desired number of tickets, which can impact
future connection establishment. For example, clients can open
multiple TLS connections to the same server for HTTP, or race TLS
connections across different network interfaces. The latter is
especially useful in transport systems that implement Happy Eyeballs
[RFC8305]. Since clients control connection concurrency and
resumption, a standard mechanism for requesting more than one ticket
is desirable.
This document specifies a new TLS extension - "ticket_request" - that
can be used by clients to express their desired number of session
tickets. Servers can use this extension as a hint of the number of
NewSessionTicket messages to vend. This extension is only applicable
to TLS 1.3 [RFC8446], DTLS 1.3 [I-D.ietf-tls-dtls13], and future
versions thereof.
Pauly, et al. Expires May 7, 2020 [Page 2]
Internet-Draft TLS Ticket Requests November 2019
Show full document text