[quicwg/base-drafts] Indicate which frames go on which stream types (#2351)

Mike Bishop <notifications@github.com> Fri, 18 January 2019 21:28 UTC

Date: Fri, 18 Jan 2019 13:28:44 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab993e461002fefa3395bd6c5fd94904aed8c8d30992cf00000001185a070c92a169ce17e52e1b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2351@github.com>
Subject: [quicwg/base-drafts] Indicate which frames go on which stream types (#2351)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c42450cb1f1b_33773f8bc90d45b4747f5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/kre1icHeKQS6n_OcJQ1aqnseoIg>

While each frame's description indicates the stream type(s) on which it is allowed, there isn't one unified place to indicate which frames are expected on which streams.  QPACK subdivides the instruction space per stream, which has the nice property that you _can't_ put something on the wrong stream.  While that's overkill for H3 (too dramatic a departure from H2, multiple IANA registries, etc.), having a table to indicate which frames are permitted on which streams would be helpful.

-- 
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/2351

Re: [quicwg/base-drafts] Indicate which frames go… Mike Bishop
[quicwg/base-drafts] Indicate which frames go on … Mike Bishop
Re: [quicwg/base-drafts] Indicate which frames go… Lucas Pardue
Re: [quicwg/base-drafts] Indicate which frames go… Mike Bishop
Re: [quicwg/base-drafts] Indicate which frames go… Lucas Pardue