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

transport_parameters minimum size should be 22 #1042

Closed
rpaulo opened this issue Jan 9, 2018 · 0 comments
Closed

transport_parameters minimum size should be 22 #1042

rpaulo opened this issue Jan 9, 2018 · 0 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@rpaulo
Copy link
Contributor

rpaulo commented Jan 9, 2018

The current draft says the minimum size of TLS's transport_parameters is 30 but the format of the transport parameters was recently changed so the new minimum size is 22.
martinthomson added a commit that referenced this issue Jan 9, 2018
@martinthomson
Closes #1042
61ae23d
ghost pushed a commit to wireshark/wireshark that referenced this issue Jan 10, 2018
@alagoutte @AndersBroman
TLS(QUIC): minimal Transport Parameter Length is 22
841e24d 
only 3 parameters are mandatory, so 3 * 4 (type + length), 2 * 4 (initial_max_stream_data + initial_max_data) + 2 (idle_timeout) = 22

See quicwg/base-drafts#1042

Bug: 13881
Change-Id: I971b0badb81086bb4bf018cb4471973a3950ee50
Reviewed-on: https://code.wireshark.org/review/25184
Petri-Dish: Alexis La Goutte <alexis.lagoutte@gmail.com>
Tested-by: Petri Dish Buildbot
Reviewed-by: Anders Broman <a.broman58@gmail.com>
@mcmanus mcmanus mentioned this issue Jan 21, 2018
Merged
@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinthomson @rpaulo