Transport Layer Security (TLS) False Start
draft-ieft-tls-falsestart-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Adam Langley , Nagendra Modadugu , Bodo Moeller | ||
| Last updated | 2015-11-07 (latest revision 2015-05-06) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ieft-tls-falsestart-00.txt
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
(agl@google.com)
Nagendra Modadugu
(Nagendra@cs.stanford.edu)
Bodo Moeller
(bmoeller@acm.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)