Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention unidirectional Stream Types 2 and 3 (QPACK) in -http #3071

Closed
Lekensteyn opened this issue Sep 29, 2019 · 1 comment · Fixed by #3081
Closed

Mention unidirectional Stream Types 2 and 3 (QPACK) in -http #3071

Lekensteyn opened this issue Sep 29, 2019 · 1 comment · Fixed by #3081
Labels

Comments

@Lekensteyn
Copy link
Contributor

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?

@mnot mnot added the -http label Oct 1, 2019
@MikeBishop
Copy link
Contributor

We can, and as QPACK is a required component of HTTP/3, you'd probably need to support QPACK for that to work. However, this is an extensible space and your dissector would need to tolerate other types it might not recognize, or that are added by future extensions. So the fact that there are definitions in other documents not mentioned by HTTP/3 is to be expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants