Using Early Data in HTTP
draft-thomson-http-replay-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2017-08-09 | ||
| Replaced by | draft-ietf-httpbis-replay | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-replay | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-thomson-http-replay-01.txt
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
(martin.thomson@gmail.com)
Mark Nottingham
(mnot@mnot.net)
Willy Tarreau
(willy@haproxy.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)