-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
implement the Reliable Stream Reset extension #4139
Labels
Comments
The primary use case for this is WebTransport. Since we discontinued work on webtransport-go (see quic-go/webtransport-go#156), there will likely be no work on this extension either. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Draft/ RFC here: https://datatracker.ietf.org/doc/draft-ietf-quic-reliable-stream-reset/
This extension will be a made a dependency of WebTransport over HTTP/3 in the near future, so we'll have to implement it if we want to continue supporting webtransport-go.
This will require some non-trivial changes to the stream state machine. We need to be extra careful here due to the concurrent nature of the stream.
API proposal:
Commit()
would commit to sending all the bytes that have been passed toWrite
on this stream so far to be delivered.Commit
wouldn't send any frames, but just make sure that ifCancelWrite
is called at a later point on the stream, it sends a RESET_STREAM_AT frame with the corresponding Reliable Size instead of a RESET_STREAM frame.The text was updated successfully, but these errors were encountered: