HPACKQPACK

HPACKQPACK is a term used in some discussions to denote a unified or hybrid header compression approach intended to support both HTTP/2's HPACK and HTTP/3's QPACK. As of now, it is not an official standard, and the phrase typically appears in speculative or research contexts rather than formal specifications.

Background: HPACK, defined in RFC 7541, compresses HTTP header fields using a static and a dynamic header table and relies on synchronized state between encoder and decoder, with Huffman coding for strings. QPACK, defined in RFC 9204, is designed for HTTP/3 over QUIC and addresses head-of-line blocking by decoupling encoder and decoder state updates through a control stream, allowing updates to be applied asynchronously.

Design and goals: HPACKQPACK would aim to merge these ideas, offering a dynamic header table with both synchronized and asynchronous update mechanisms that can operate across HTTP/2 and HTTP/3. It might support in-band indexing like HPACK for stable headers and non-blocking updates like QPACK for dynamic headers, potentially including a negotiation mechanism to enable or select features depending on the transport.

Challenges: Interoperability with existing deployments, increased implementation and testing complexity, and potential security concerns such as compression-related attacks. Ensuring robust state synchronization across multiplexed streams and maintaining backward compatibility with established HTTP/2 and HTTP/3 practices are significant considerations.

Status: There is no widely adopted standard named HPACKQPACK; it remains a conceptual or experimental notion found in technical discussions or research proposals.

See also: HPACK, QPACK, HTTP/2, HTTP/3.

---