Header Compression for HTTP over QUIC

Document Type Replaced Internet-Draft (quic WG)
Authors Charles Krasic  , Mike Bishop  , Alan Frindell 
Last updated 2018-02-20
Replaces draft-krasic-quic-qcram
Replaced by draft-ietf-quic-qpack
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text xml htmlized pdfized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-quic-qpack
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Charles Krasic (ckrasic@google.com)
Mike Bishop (mbishop@evequefou.be)
Alan Frindell (afrind@fb.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)