Skip to main content

TLS Ticket Request Message
draft-rashok-tls-ticket-request-msg-01

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Raja Ashok V K
Last updated 2020-10-15 (Latest revision 2020-04-13)
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

TLS session ticket provides a stateless mechanism for server to resume connection with client. As per TLS 1.3 [RFC8446], server always sends arbitary number of session ticket after handshake. This document introduces a new message which is TicketRequest message, it can be send by client after handshake at any point of connection lifetime to retrieve new session ticket. The proposed mechanism in this document is only for TLS 1.3 and DTLS 1.3 and future versions.

Authors

Raja Ashok V K

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)