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

Update ACK generation policy #3623

Closed
wants to merge 5 commits into from
Closed

Update ACK generation policy #3623

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
b0d3867
Update ACK generation policy
adventureloop May 1, 2020
525035f
Update draft-ietf-quic-transport.md
adventureloop May 6, 2020
1bed083
Update draft-ietf-quic-transport.md
adventureloop May 6, 2020
2c87882
Update draft-ietf-quic-transport.md
adventureloop May 6, 2020
fff1097
Update draft-ietf-quic-transport.md
adventureloop May 6, 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 @@ -3268,7 +3268,7 @@ ack-elicitingpacket (recommended practice for TCP {{?RFC5681}}). QUIC permits
a larger ratio between ACKs and data, which can reduce
the number of ACK frames that are sent and need to be processed.
The receiver can provide a higher rate of acknowledgements
(e.g. every ack-eliciting packet) for the first 100 packets.
(e.g., every ack-eliciting packet) for the first 100 packets.
A receiver could decide to send an ACK frame less frequently if it has
information about how frequently the sender's congestion controller
needs feedback, or if the receiver is CPU or bandwidth constrained.
Expand Down