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

acks are not congestion control -> be careful #478

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

acks are not congestion control -> be careful #478

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 4 additions & 1 deletion draft-ietf-quic-multipath.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -979,7 +979,10 @@ faster if the scheduling strategy is stable, but besides that
implementations can choose between multiple strategies such as sending
PATH_ACK frames on the path they acknowledge packets, or sending
PATH_ACK frames on the shortest path, which results in shorter control loops
and thus better performance.
and thus better performance. As packets that only carries PATH_ACK frames
are not congestion controlled, sending only PATH_ACK frames on a path
should carefully consider the load induced by these packets, especially
if the capacity is unknown on that path.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The additional sentence uses the passive form and is a bit hard to read. If we want something, I would suggest:

However, since packets that only carries PATH_ACK frames
are not congestion controlled, senders should carefully consider the load induced by these packets, especially
if the capacity is unknown on that path.

## Retransmissions

Expand Down
Loading