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

Clients send datagrams with 1200 byte payloads #3051

Merged
merged 3 commits into from Oct 22, 2019
Merged

Clients send datagrams with 1200 byte payloads #3051

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f77bd1e
Clients send datagrams with 1200 byte payloads
ianswett Sep 19, 2019
3801ebd
More UDP
ianswett Sep 20, 2019
6cfcbe2
Closes #3053 too
martinthomson Sep 21, 2019
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-transport.md
View file
Open in desktop
Expand Up @@ -1592,7 +1592,7 @@ magnitude of any amplification attack that can be mounted using spoofed source
addresses. In determining this limit, servers only count the size of
successfully processed packets.

Clients MUST ensure that UDP datagrams containing only Initial packets have UDP
Clients MUST ensure that UDP datagrams containing Initial packets have UDP
payloads of at least 1200 bytes, adding padding to packets in the datagram as
ianswett marked this conversation as resolved.
Show resolved Hide resolved
necessary. Sending padded datagrams ensures that the server is not overly
constrained by the amplification restriction.
Expand Down