Transport Layer Security (TLS) False Start
draft-bmoeller-tls-falsestart-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Adam Langley , Nagendra Modadugu , Bodo Moeller | ||
Last updated | 2010-06-02 | ||
Replaced by | draft-ietf-tls-falsestart, RFC 7918 | ||
RFC stream | (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
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.)