Transport Layer Security (TLS) Resumption across Server Names
draft-vvv-tls-cross-sni-resumption-00
| Document | Type |
Replaced Internet-Draft
(tls WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Victor Vasiliev | ||
| Last updated | 2020-12-12 (Latest revision 2020-07-12) | ||
| Replaced by | draft-ietf-tls-cross-sni-resumption | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-tls-cross-sni-resumption | |
| Consensus boilerplate | Unknown | ||
| 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 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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)