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

Rephrase size requirement for Initial packets #2520

Merged
merged 3 commits into from Mar 15, 2019
Merged

Rephrase size requirement for Initial packets #2520

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
79c731c
Rephrase size requirement for Initial packets
janaiyengar Mar 13, 2019
a69e90d
Update draft-ietf-quic-transport.md
martinthomson Mar 15, 2019
50011f2
reflow
janaiyengar Mar 15, 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
9 changes: 5 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1468,10 +1468,11 @@ 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 pad UDP datagrams that contain only Initial packets to at least
1200 bytes. 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 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.

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