ObsoletedPROPOSED STANDARDIETF stream

RFC 5077: Transport Layer Security (TLS) Session Resumption without Server-Side State

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8446, RFC 9846.

Current document in this lineage: RFC 6066 — Transport Layer Security (TLS) Extensions: Extension Definitions; RFC 9846 — The Transport Layer Security (TLS) Protocol Version 1.3

In plain English — editorial summary, not part of the RFC

This document describes a mechanism that enables the Transport Layer Security (TLS) server to resume sessions and avoid keeping per-client session state. The TLS server encapsulates the session state into a ticket and forwards it to the client. The client can subsequently resume a session using the obtained ticket. This document obsoletes RFC 4507. [STANDARDS-TRACK]

Document record

Document ID: RFC5077
Published: January 2008
Authors: J. Salowey; H. Zhou; P. Eronen; H. Tschofenig
Status: PROPOSED STANDARD
Stream: IETF
Area: —
Pages: 20
Also known as: —

Obsoletes:: RFC 4507
Obsoleted by:: RFC 8446, RFC 9846
Updated by:: RFC 8447

Standards lineage

This document is one revision in a chain of 15 RFCs, each formally replacing the one before it.

Read the full history of The Transport Layer Security (TLS) Protocol Version 1.3 →

Referenced by

3 later RFCs formally update or obsolete part of this document.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on 23 August 2026. RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?