Re: [quicwg/base-drafts] Core terminology in QPACK (#3520)

ianswett <notifications@github.com> Sat, 21 March 2020 20:00 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C2E3A0925 for <quic-issues@ietfa.amsl.com>; Sat, 21 Mar 2020 13:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id If2_PdXpCyUf for <quic-issues@ietfa.amsl.com>; Sat, 21 Mar 2020 13:00:16 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 294003A0921 for <quic-issues@ietf.org>; Sat, 21 Mar 2020 13:00:15 -0700 (PDT)
Date: Sat, 21 Mar 2020 13:00:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1584820814; bh=nlLxoZTQoUq0wZ8wLX1eFXkR5B8zHn22sWFGVLyZCPo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1Fdrl7pG5XdvEmWWhgNb2+0TmjjBy1bV/OYaYsCSotD6cMLmw13GBfydd0lcxrk0D 9RmwmVDGlH7+eCl7UV1ah5B3R54sRbK6KKvxsbjOYl520ebOGKTOMSft6jWcewMBTh CXpaX7uXD34MtlfUrw61Kzr8s4sYLNlNTLT6bGxQ=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZ5BQ46I3V7YGFALZF4QJJU5EVBNHHCFHBAYE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3520/review/378946856@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3520@github.com>
References: <quicwg/base-drafts/pull/3520@github.com>
Subject: Re: [quicwg/base-drafts] Core terminology in QPACK (#3520)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e76724ebcb79_31e13f868e2cd96460841c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/0niVg9ysNU0Er5kIWcsNM0f3Jag>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Mar 2020 20:00:18 -0000

ianswett commented on this pull request.



> @@ -84,9 +84,10 @@ code and issues list for this draft can be found at
 
 The QUIC transport protocol {{QUIC-TRANSPORT}} is designed to support HTTP
 semantics, and its design subsumes many of the features of HTTP/2 {{?RFC7540}}.
-HTTP/2 uses HPACK {{!RFC7541}} for header compression.  If HPACK were used for
-HTTP/3 {{HTTP3}}, it would induce head-of-line blocking due to built-in
-assumptions of a total ordering across frames on all streams.
+HTTP/2 uses HPACK {{!RFC7541}} for compression of the header and trailer
+sections.  If HPACK were used for HTTP/3 {{HTTP3}}, it would induce head-of-line
+blocking due to built-in assumptions of a total ordering across frames on all

```suggestion
blocking for headers due to built-in assumptions of a total ordering across frames on all
```

> @@ -84,9 +84,10 @@ code and issues list for this draft can be found at
 
 The QUIC transport protocol {{QUIC-TRANSPORT}} is designed to support HTTP
 semantics, and its design subsumes many of the features of HTTP/2 {{?RFC7540}}.
-HTTP/2 uses HPACK {{!RFC7541}} for header compression.  If HPACK were used for
-HTTP/3 {{HTTP3}}, it would induce head-of-line blocking due to built-in
-assumptions of a total ordering across frames on all streams.
+HTTP/2 uses HPACK {{!RFC7541}} for compression of the header and trailer
+sections.  If HPACK were used for HTTP/3 {{HTTP3}}, it would induce head-of-line
+blocking due to built-in assumptions of a total ordering across frames on all

Or maybe better would be ", it would make headers head-of-line blocking due to..."

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3520#pullrequestreview-378946856