Header Compression for HTTP over QUIC
draft-krasic-quic-qcram-04
| Document | Type |
Replaced Internet-Draft
(quic WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Charles 'Buck' Krasic | ||
| Last updated | 2018-02-13 (Latest revision 2018-01-23) | ||
| Replaced by | draft-ietf-quic-qcram | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-quic-qcram | |
| Consensus boilerplate | Yes | ||
| 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
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)