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

Make initial_max_stream_id_* optional and default to zero #971

Merged
merged 4 commits into from Nov 30, 2017
Merged

Make initial_max_stream_id_* optional and default to zero #971

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0276c89
Make initial_max_stream_id_* optional and default to zero
martinthomson Nov 29, 2017
654f8e5
Warn against silly values for 0-RTT
martinthomson Nov 29, 2017
4dfd06b
Correct far too many nits
martinthomson Nov 30, 2017
4360951
Grammar booboo
martinthomson Nov 30, 2017
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
5 changes: 5 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1223,6 +1223,11 @@ initial_max_stream_data that are smaller than the remembered value of those
parameters. Similarly, a server MUST NOT reduce the value of
initial_max_stream_id_bidi or initial_max_stream_id_uni.

Omitting or setting a zero value for certain transport parameters can result in
0-RTT data being enabled, but not usable. The following transport parameters
SHOULD be set to non-zero values for 0-RTT: initial_max_stream_id_bidi,
initial_max_stream_id_uni, initial_max_data, initial_max_stream_data.

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

Expand Down