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

More detail regarding dropping of ACK Ranges #3581

Merged
merged 2 commits into from Apr 29, 2020
Merged

More detail regarding dropping of ACK Ranges #3581

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
65d2acb
More detail regarding dropping of ACK Ranges
martinthomson Apr 15, 2020
88bbc30
Cite relevant section
martinthomson Apr 28, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3311,7 +3311,7 @@ with minimal state.

Receivers can discard all ACK Ranges, but they MUST retain the largest packet
number that has been successfully processed as that is used to recover packet
numbers from subsequent packets.
numbers from subsequent packets; see {{packet-encoding}}.

A receiver SHOULD include an ACK Range containing the largest received packet
number in every ACK frame. The Largest Acknowledged field is used in ECN
Expand Down