RFC 7924: Transport Layer Security (TLS) Cached Information Extension
In plain English — editorial summary, not part of the RFC
Transport Layer Security (TLS) handshakes often include fairly static information, such as the server certificate and a list of trusted certification authorities (CAs). This information can be of considerable size, particularly if the server certificate is bundled with a complete certificate chain (i.e., the certificates of intermediate CAs up to the root CA). This document defines an extension that allows a TLS client to inform a server of cached information, thereby enabling the server to omit already available information.
Document record
- Document ID
- RFC7924
- Published
- July 2016
- Authors
- S. Santesson; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7925Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of ThingsCurrent
July 2016
- RFC 7929DNS-Based Authentication of Named Entities (DANE) Bindings for OpenPGPCurrent
August 2016
- RFC 7919Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)Current
August 2016
- RFC 7930Larger Packets for RADIUS over TCPCurrent
August 2016
- RFC 7918Transport Layer Security (TLS) False StartCurrent
August 2016
- RFC 7905ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS)Updated
June 2016
- RFC 7970The Incident Object Description Exchange Format Version 2Current
November 2016
- RFC 8009AES Encryption with HMAC-SHA2 for Kerberos 5Current
October 2016
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 . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?