Anonymous Tickets for TLS 1.3
draft-sullivan-tls-anonymous-tickets-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nick Sullivan , Christopher A. Wood | ||
| Last updated | 2019-09-12 (Latest revision 2019-03-11) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a mechanism that enables unlinkable session resumption for TLS 1.3 without server-side state. In contrast to existing ticket-based resumption in TLS 1.3, wherein servers construct and issue tickets to clients, this document specifies a mechanism by which clients request "anonymous tickets" from servers. When a session is resumed using an anonymous ticket, a server only learns that it previously engaged in a session with some client, rather than linking it to a specific client. Anonymous tickets are only useful for clients with idempotent early data to send.
Authors
Nick Sullivan
Christopher A. Wood
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)