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

Mention every Transport Parameter in section on values for 0-RTT #3756

Merged
merged 3 commits into from Jun 23, 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
8 changes: 8 additions & 0 deletions draft-ietf-quic-transport.md
Expand Up @@ -1749,6 +1749,14 @@ values for 0-RTT. This includes initial_max_data and either
initial_max_streams_bidi and initial_max_stream_data_bidi_remote, or
initial_max_streams_uni and initial_max_stream_data_uni.

A server MAY store and recover the previously sent values of the
max_idle_timout, max_udp_payload_size, and disable_active_migration parameters
and reject 0-RTT if it selects smaller values. Lowering the values of these
nharper marked this conversation as resolved.
Show resolved Hide resolved
parameters while also accepting 0-RTT data could degrade the performance of the
connection. Specifically, lowering the max_udp_payload_size could result in
dropped packets leading to worse performance compared to rejecting 0-RTT data
outright.

A server MUST either reject 0-RTT data or abort a handshake if the implied
values for transport parameters cannot be supported.

Expand Down