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

Deemphasize TCP SACKs reference in ACK frame description #1312

Merged
merged 2 commits into from Apr 25, 2018
Merged

Deemphasize TCP SACKs reference in ACK frame description #1312

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8024912
Deemphasize TCP SACKs reference in ACK frame description
Apr 20, 2018
520f722
Improve the irrevokable ACK frame paragraph; add SACK RFC ref
Apr 25, 2018
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
6 changes: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2581,9 +2581,9 @@ received and processed. A sent packet that has never been acknowledged is
missing. The ACK frame contains any number of ACK blocks. ACK blocks are
ranges of acknowledged packets.

Unlike TCP SACKs, QUIC acknowledgements are irrevocable. Once a packet has
been acknowledged, even if it does not appear in a future ACK frame,
it remains acknowledged.
QUIC acknowledgements are irrevocable. Once acknowledged, a packet remains
acknowledged, even if it does not appear in a future ACK frame. This is unlike
TCP SACKs ({{?RFC2018}}).

A client MUST NOT acknowledge Retry packets. Retry packets include the packet
number from the Initial packet it responds to. Version Negotiation packets
Expand Down