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

A section devoted to Initial packet size #3746

Merged
merged 1 commit into from Jun 9, 2020
Merged
Changes from all commits
Commits
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: 6 additions & 3 deletions draft-ietf-quic-transport.md
Expand Up @@ -3855,6 +3855,12 @@ known. However, prior to learning the value of the transport parameter,
endpoints risk datagrams being lost if they send packets larger than the
smallest allowed maximum packet size of 1200 bytes.

UDP datagrams MUST NOT be fragmented at the IP layer. In IPv4
{{!IPv4=RFC0791}}, the DF bit MUST be set to prevent fragmentation on the path.


## Initial Packet Size {#initial-size}

A client MUST expand the payload of all UDP datagrams carrying Initial packets
to at least the smallest allowed maximum packet size (1200 bytes) by adding
PADDING frames to the Initial packet or by coalescing the Initial packet; see
Expand All @@ -3867,9 +3873,6 @@ attacks caused by server responses toward an unverified client address; see
Datagrams containing Initial packets MAY exceed 1200 bytes if the client
believes that the network path and peer both support the size that it chooses.

UDP datagrams MUST NOT be fragmented at the IP layer. In IPv4
{{!IPv4=RFC0791}}, the DF bit MUST be set to prevent fragmentation on the path.

A server MUST discard an Initial packet that is carried in a UDP datagram with a
payload that is less than the smallest allowed maximum packet size of 1200
bytes. A server MAY also immediately close the connection by sending a
Expand Down