RFC 7918: Transport Layer Security (TLS) False Start
In plain English — editorial summary, not part of the RFC
This document specifies an optional behavior of Transport Layer Security (TLS) client implementations, dubbed "False Start". It affects only protocol timing, not on-the-wire protocol data, and can be implemented unilaterally. A TLS False Start reduces handshake latency to one round trip.
Document record
- Document ID
- RFC7918
- Published
- August 2016
- Authors
- A. Langley; N. Modadugu; B. Moeller
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7919Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)Current
August 2016
- RFC 7924Transport Layer Security (TLS) Cached Information ExtensionCurrent
July 2016
- 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 7930Larger Packets for RADIUS over TCPCurrent
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 7833A RADIUS Attribute, Binding, Profiles, Name Identifier Format, and Confirmation Methods for the Security Assertion Markup Language (SAML)Current
May 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?