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.

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

Clarify how the initial CWND is limited #4740

Merged
merged 3 commits into from Jan 13, 2021
Merged
Changes from all commits
Commits
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
9 changes: 5 additions & 4 deletions draft-ietf-quic-recovery.md
Expand Up @@ -825,10 +825,11 @@ peer-reported ECN-CE count increases; see Section 13.4.2 of {{QUIC-TRANSPORT}}.

QUIC begins every connection in slow start with the congestion window set to
an initial value. Endpoints SHOULD use an initial congestion window of 10 times
the maximum datagram size (max_datagram_size), limited to the larger of 14720
bytes or twice the maximum datagram size. This follows the analysis and
recommendations in {{?RFC6928}}, increasing the byte limit to account for the
smaller 8-byte overhead of UDP compared to the 20-byte overhead for TCP.
the maximum datagram size (max_datagram_size), while limiting the window
to the larger of 14720 bytes or twice the maximum datagram size. This follows
the analysis and recommendations in {{?RFC6928}}, increasing the byte limit to
account for the smaller 8-byte overhead of UDP compared to the 20-byte overhead
for TCP.

If the maximum datagram size changes during the connection, the initial
congestion window SHOULD be recalculated with the new size. If the maximum
Expand Down