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

Clarify when and what to ACK #739

Merged
merged 2 commits into from Aug 17, 2017
Merged

Clarify when and what to ACK #739

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
68fe216
Clarify when and what to ACK
ianswett Aug 16, 2017
b4e4fb9
Tweak
martinthomson Aug 17, 2017
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
3 changes: 2 additions & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2361,7 +2361,8 @@ containing the packet number of the received packet.
To avoid creating an indefinite feedback loop, an endpoint MUST NOT send an
ACK frame in response to a packet containing only ACK or PADDING frames, even
if there are packet gaps which precede the received packet. The endpoint MUST
ack packets containing only ACK or PADDING frames in the next sent ACK frame.
acknowledge packets containing only ACK or PADDING frames in the next ACK frame
that it sends.

Strategies and implications of the frequency of generating acknowledgments are
discussed in more detail in {{QUIC-RECOVERY}}.
Expand Down