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

sender MUST limit bursts, SHOULD limit to IW #3936

Merged
merged 8 commits into from Sep 1, 2020
Merged

sender MUST limit bursts, SHOULD limit to IW #3936

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
dbcfc22
sender SHOULD limit bursts
janaiyengar Jul 21, 2020
8974886
martin's suggestion
janaiyengar Jul 25, 2020
82526d0
smithing
janaiyengar Jul 25, 2020
325fcda
MUST pace or limit bursts
janaiyengar Jul 27, 2020
9dfc086
Update draft-ietf-quic-recovery.md
janaiyengar Jul 27, 2020
5bb2a83
reflow
janaiyengar Jul 27, 2020
371ef37
Praveen's suggestion
janaiyengar Jul 28, 2020
ffdf31f
Update draft-ietf-quic-recovery.md
janaiyengar Jul 29, 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-recovery.md
View file
Open in desktop
Expand Up @@ -884,7 +884,7 @@ Sending multiple packets into the network without any delay between them creates
a packet burst that might cause short-term congestion and losses. Senders MUST
either use pacing or limit such bursts. Senders SHOULD limit bursts to the
initial congestion window; see {{initial-cwnd}}. A sender with knowledge that
janaiyengar marked this conversation as resolved.
Show resolved Hide resolved
the network path to the receiver can absorb larger bursts may use a higher
the network path to the receiver can absorb larger bursts MAY use a higher
limit.

An implementation should take care to architect its congestion controller to
Expand Down