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.

Sign up for GitHub

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

Jump to bottom

Why do we have final size? #3739

Merged
merged 3 commits into from
Jun 9, 2020
Merged

Why do we have final size? #3739

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
24a7163
Why do we have final size?
MikeBishop Jun 5, 2020
ec07d0f
Martin's suggestion, with some editing
MikeBishop Jun 8, 2020
2b0b2ba
Two implicit fields
MikeBishop Jun 8, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -910,7 +910,7 @@ if no bytes were sent.

The final size of a stream is always signaled to the recipient. The final size
is the sum of the Offset and Length fields of a STREAM frame with a FIN flag,
noting that the length might be implicit. Alternatively, the Final Size field
noting that these fields might be implicit. Alternatively, the Final Size field
of a RESET_STREAM frame carries this value. This ensures that all ways that a
stream can be closed result in the number of bytes on the stream being reliably
transmitted. This guarantees that both endpoints agree on how much flow control
Expand Down