Transport Layer Security (TLS) False Start
draft-bmoeller-tls-falsestart-01
Document | Type |
Replaced Internet-Draft
(tls WG)
Expired & archived
|
|
---|---|---|---|
Authors | Adam Langley , Nagendra Modadugu , Bodo Moeller | ||
Last updated | 2015-10-14 (Latest revision 2014-11-10) | ||
Replaced by | draft-ietf-tls-falsestart | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-tls-falsestart | |
Consensus boilerplate | Unknown | ||
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
This document specifies an optional behavior of TLS implementations, dubbed False Start. It affects only protocol timing, not on-the-wire protocol data, and can be implemented unilaterally. The TLS False Start feature leads to a latency reduction of one round trip for certain handshakes.
Authors
Adam Langley
Nagendra Modadugu
Bodo Moeller
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)