Skip to content

ACK-only packets are not congestion controlled #3453

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

Merged
ianswett merged 2 commits into from
Mar 5, 2020
Merged

ACK-only packets are not congestion controlled #3453

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
731f802
ACK-only packets are not congestion controlled
ianswett Feb 13, 2020
78bae10
Update draft-ietf-quic-recovery.md
janaiyengar Feb 28, 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
6 changes: 6 additions & 0 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -643,6 +643,12 @@ If an endpoint uses a different controller than that specified in this document,
the chosen controller MUST conform to the congestion control guidelines
specified in Section 3.1 of {{!RFC8085}}.

Similar to TCP, packets containing only ACK frames do not count towards bytes
in flight and are not congestion controlled. Unlike TCP, QUIC can detect the
loss of these packets and MAY use that information to adjust the congestion
controller or the rate of ACK-only packets being sent, but this document does
not describe a mechanism for doing so.

The algorithm in this document specifies and uses the controller's congestion
window in bytes.

Expand Down