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

Minor editorial: datagram not packet #4225

Merged
merged 1 commit into from Oct 15, 2020
Merged

Minor editorial: datagram not packet #4225

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -4089,11 +4089,11 @@ fragmentation on the path.
## Initial Datagram Size {#initial-size}

A client MUST expand the payload of all UDP datagrams carrying Initial packets
to at least the smallest allowed maximum datagram size (1200 bytes) by adding
to at least the smallest allowed maximum datagram size of 1200 bytes by adding
PADDING frames to the Initial packet or by coalescing the Initial packet; see
{{packet-coalesce}}. Similarly, a server MUST expand the payload of all UDP
datagrams carrying ack-eliciting Initial packets to at least the smallest
allowed maximum packet size (1200 bytes). Sending UDP datagrams of this size
allowed maximum datagram size of 1200 bytes. Sending UDP datagrams of this size
ensures that the network path supports a reasonable Path Maximum Transmission
Unit (PMTU), in both directions. Additionally, a client that expands Initial
packets helps reduce the amplitude of amplification attacks caused by server
Expand Down