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

Auth48 fixes for QPACK #4986

Merged
merged 5 commits into from
May 9, 2022
Merged

Auth48 fixes for QPACK #4986

merged 5 commits into from
May 9, 2022

Conversation

MikeBishop
Copy link
Contributor

Addresses most of the open RFC Editor questions.

Comment on lines +525 to +528
For clients not using 0-RTT data (whether 0-RTT is not attempted or is rejected)
and for all HTTP/3 servers, the maximum table capacity is 0 until the encoder
processes a SETTINGS frame with a non-zero value of
SETTINGS_QPACK_MAX_TABLE_CAPACITY.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

By parallel with the previous paragraph's first sentence.

rfc9204.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants