-
Notifications
You must be signed in to change notification settings - Fork 202
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
Add text on flow control deadlocks #5001
Labels
-bis
An issue that is best addressed in a future revision of a published document
-transport
editorial
An issue that does not affect the design of the protocol; does not require consensus.
Comments
WebTransport seems like the prime target audience for the applicability draft. Section 4.4 is titled "Flow Control Deadlocks" and is ~500 words. So a few of questions:
|
Oh, I forgot about that. I think that I wrote it, even. A pointer might be all that is needed then. |
Here's some archaeology for you, your original PR 5 years ago - #1927 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
-bis
An issue that is best addressed in a future revision of a published document
-transport
editorial
An issue that does not affect the design of the protocol; does not require consensus.
For a new revision of transport, it would be good to have general guidance text about flow control deadlocks. The best reference we have today is the somewhat specific text in Section 2.1.3 of RFC 9204 and that isn't very satisfactory. This has come up a few times in discussions about APIs for WebTransport, which replicates a lot of the QUIC stream mechanics.
The text was updated successfully, but these errors were encountered: