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

Transport: Inclusion of multiple Stream Frames for the same Stream ID #610

Closed
gloinul opened this issue Jun 8, 2017 · 4 comments
Closed
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@gloinul
Copy link
Contributor

gloinul commented Jun 8, 2017

draft-ietf-quic-transport-03, Section 8.1 says:

Stream multiplexing is achieved by interleaving STREAM frames from
multiple streams into one or more QUIC packets. A single QUIC packet
MAY bundle STREAM frames from multiple streams.

The inclusion of multiple stream frames for the same frame is not clear in the above. Is it allowed or not?

@martinthomson
Copy link
Member

I'm not sure that I understand. Doesn't the final sentence answer your question?

@gloinul
Copy link
Contributor Author

gloinul commented Jun 8, 2017

No, there is a difference between one stream frame per stream ID aggregated in the same packet, and multiple stream frames for the same stream ID. The later is not clear that it is allowed with above formulation. But, I guess that based on what is in the Stream Frame you can have multiple stream frames for the same ID, so this is likely an editorial issue on the above text to make it explicit.

@martinthomson
Copy link
Member

Oh, now I understand. Well, that's suboptimal, but permissible. (You said "multiple stream frames for the same frame", where you meant same stream.) Do you think that removing "from multiple streams" would clarify this point?

@gloinul
Copy link
Contributor Author

gloinul commented Jun 8, 2017

I would rather be explicit and say; "A single QUIC packet MAY bundle multiple STREAM frames from one or more stream IDs."

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Jun 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

No branches or pull requests

2 participants