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

Remove exception for Initial padding #2523

Merged
merged 2 commits into from
Apr 23, 2019
Merged
Changes from all commits
Commits
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
9 changes: 4 additions & 5 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -1478,11 +1478,10 @@ 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 Initial packets are sized to
at least 1200 bytes, adding padding to packets in the datagram as necessary.
Once a client has received an acknowledgment for a Handshake packet it MAY send
smaller datagrams. Sending padded datagrams ensures that the server is not
overly constrained by the amplification restriction.
Clients MUST ensure that UDP datagrams containing only Initial packets are sized
to at least 1200 bytes, adding padding to packets in the datagram as necessary.
Sending padded datagrams ensures that the server is not overly constrained by
the amplification restriction.

Packet loss, in particular loss of a Handshake packet from the server, can cause
a situation in which the server cannot send when the client has no data to send
Expand Down