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

The first Initial needs to fit into a single IP packet #2183

Merged
merged 2 commits into from Dec 18, 2018
Merged

The first Initial needs to fit into a single IP packet #2183

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8d344bd
The first Initial needs to fit into a single IP packet
martinthomson Dec 14, 2018
a326fec
Also applies after Retry
martinthomson Dec 17, 2018
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
View file
Open in desktop
Expand Up @@ -3081,9 +3081,12 @@ corrupt ECN codepoints in the IP header.
The QUIC packet size includes the QUIC header and protected payload, but not the
UDP or IP header.

Clients MUST ensure they send the first Initial packet in single IP packet. The
payload of a UDP datagram carrying the first Initial packet MUST be expanded to
at least 1200 bytes, by adding PADDING frames to the Initial packet and/or by
Clients MUST ensure they send the first Initial packet in single IP packet.
Similarly, the first Initial packet sent after receiving a Retry packet MUST be
sent in a single IP packet.

The payload of a UDP datagram carrying the first Initial packet MUST be expanded
to at least 1200 bytes, by adding PADDING frames to the Initial packet and/or by
combining the Initial packet with a 0-RTT packet (see {{packet-coalesce}}).
Sending a UDP datagram of this size ensures that the network path supports a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We require networks to support 1280 bytes in order to be used with QUIC, so testing for 1200 bytes seems weird.
Why are we not padding to 1280 anyway?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because we don't know how much overhead there is.

reasonable Maximum Transmission Unit (MTU), and helps reduce the amplitude of
Expand Down