Header Compression for HTTP over QUIC
draft-krasic-quic-qcram-04
| Document | Type | Replaced Internet-Draft (quic WG) | |
|---|---|---|---|
| Last updated | 2018-02-13 (latest revision 2018-01-23) | ||
| Replaced by | draft-ietf-quic-qcram | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-quic-qcram | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-krasic-quic-qcram-04.txt
Abstract
The design of the core QUIC transport subsumes many HTTP/2 features, prominent among them stream multiplexing. A key advantage of the QUIC transport is stream multiplexing free of head-of-line (HoL) blocking between streams. In HTTP/2, multiplexed streams can suffer HoL blocking due to TCP. If HTTP/2's HPACK is used for header compression, HTTP/QUIC is still vulnerable to HoL blocking, because of HPACK's assumption of in-order delivery. This draft defines QCRAM, a variation of HPACK and mechanisms in the HTTP/QUIC mapping that allow the flexibility to avoid header-compression-induced HoL blocking.
Authors
Charles Krasic (ckrasic@google.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)