Transport Layer Security (TLS) Resumption across Server Names
draft-vvv-tls-cross-sni-resumption-00
| Document | Type | Replaced Internet-Draft (tls WG) | |
|---|---|---|---|
| Author | Victor Vasiliev | ||
| Last updated | 2020-12-12 (latest revision 2020-07-12) | ||
| Replaced by | draft-ietf-tls-cross-sni-resumption | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-tls-cross-sni-resumption | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-vvv-tls-cross-sni-resumption-00.txt
https://www.ietf.org/archive/id/draft-vvv-tls-cross-sni-resumption-00.txt
Abstract
This document specifies a way for the parties in the Transport Layer Security (TLS) protocol to indicate that an individual session ticket can be used to perform resumption even if the Server Name of the new connection does not match the Server Name of the original.
Authors
Victor Vasiliev (vasilvv@google.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)