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

Limit sending by the anti-amplification factor #3640

Merged
merged 2 commits into from May 13, 2020
Merged

Limit sending by the anti-amplification factor #3640

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
010574e
Limit sending by the anti-amplification factor
ianswett May 10, 2020
c8fa3f8
Update draft-ietf-quic-recovery.md
ianswett May 10, 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 @@ -752,7 +752,7 @@ 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.

Prior to validating the client's address, the server can also be limited by
Prior to validating the client's address, the server can be further limited by
the anti-amplification limit as specified in Section 8.1 of {{QUIC-TRANSPORT}}.
Though the anti-amplification limit can prevent the congestion window from
being fully utilized and therefore slow down the increase in congestion window,
Expand Down