Using Early Data in HTTP
draft-thomson-http-replay-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Martin Thomson , Mark Nottingham , Willy Tarreau | ||
| Last updated | 2017-08-09 | ||
| Replaced by | draft-ietf-httpbis-replay | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-replay | |
| 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 explains the risks of using early data for HTTP and describes techniques for reducing them. In particular, it defines a mechanism that enables clients to communicate with servers about early data, to assure correct operation.
Authors
Martin Thomson
Mark Nottingham
Willy Tarreau
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)