Transport Layer Security (TLS) Resumption across Server Names
draft-ietf-tls-cross-sni-resumption-01
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Victor Vasiliev | ||
| Last updated | 2021-11-14 (Latest revision 2021-05-13) | ||
| Replaces | draft-vvv-tls-cross-sni-resumption | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Waiting for WG Chair Go-Ahead | |
| Document shepherd | Christopher A. Wood | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | caw@heapingbits.net |
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.)