[quicwg/base-drafts] Mention unidirectional Stream Types 2 and 3 (QPACK) in -http (#3071)

Peter Wu <notifications@github.com> Sun, 29 September 2019 15:59 UTC

Date: Sun, 29 Sep 2019 08:59:10 -0700
From: Peter Wu <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK54ZZALK2TEWP7HTJV3TYKV5EVBNHHB3TDKFM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3071@github.com>
Subject: [quicwg/base-drafts] Mention unidirectional Stream Types 2 and 3 (QPACK) in -http (#3071)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d90d4ce2b68f_20873f9b020cd960679935"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HJsKVMUC9ZS-RwLlN41T98OKbtY>

The Stream Types registry (https://tools.ietf.org/html/draft-ietf-quic-http-23#section-11.6) currently lists two types only (0 - control, 1 - push).

While working on a dissector for the base HTTP/3 protocol, I ran across 2 and 3. It turns out these are defined in the QPACK document (https://tools.ietf.org/html/draft-ietf-quic-qpack-10#section-8.2) with 2 - QPACK Encoder Stream, 3 - QPACK Decoder Stream.

Since QPACK has already been referenced multiple times from the -http document, what about mentioning (or registering) the two codepoints in the -http document and reference to the -qpack document for the definition?

-- 
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/issues/3071

[quicwg/base-drafts] Mention unidirectional Strea… Peter Wu
Re: [quicwg/base-drafts] Mention unidirectional S… Mike Bishop
Re: [quicwg/base-drafts] Mention unidirectional S… Mike Bishop