From 735c09ea6d9406057341e6ec5bf4d52a19290efe Mon Sep 17 00:00:00 2001 From: Dmitri Tikhonov Date: Sat, 7 Jul 2018 22:06:45 -0400 Subject: [PATCH] Talk about HTTP/2 using HPACK in present tense --- draft-ietf-quic-qpack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-qpack.md b/draft-ietf-quic-qpack.md index 7c451830e0..c64887f1c9 100644 --- a/draft-ietf-quic-qpack.md +++ b/draft-ietf-quic-qpack.md @@ -84,7 +84,7 @@ code and issues list for this draft can be found at # Introduction The QUIC transport protocol was designed from the outset to support HTTP -semantics, and its design subsumes many of the features of HTTP/2. HTTP/2 used +semantics, and its design subsumes many of the features of HTTP/2. HTTP/2 uses HPACK ({{!RFC7541}}) for header compression, but QUIC's stream multiplexing comes into some conflict with HPACK. A key goal of the design of QUIC is to improve stream multiplexing relative to HTTP/2 by reducing head-of-line