Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As proposed in https://marten-seemann.github.io/draft-seemann-quic-reliable-stream-reset/draft-seemann-quic-reliable-stream-reset.html.
Changes to the state machine can be found in 76ac2e0.
The sender design is, when a reliable reset is requested, pretend as if the stream was closed at current Final Size (i.e., amount of data that have already left the sender). But instead of sending FIN, send a RELIABLE_RESET_STREAM frame with the Reliable Size field set to the Final Size.
On the receiver-side, the reset signal is surfaced using the same API (i.e.,
on_receive_reset). But instead of clearing receive state (i.e., list of byte blocks that have been received), we continue running the receive state machinery until all bytes up tomin(FinalSize, ReliableSize)have been received.