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

Negative base values are invalid #4940

Merged
merged 2 commits into from Apr 26, 2022
Merged

Negative base values are invalid #4940

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e22ccf
Negative base values are invalid
martinthomson Oct 4, 2021
10e134a
Merge remote-tracking branch 'origin/h3qp_auth48' into negative-base
MikeBishop Apr 26, 2022
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
6 changes: 6 additions & 0 deletions rfc9204.md
View file
Open in desktop
Expand Up @@ -990,6 +990,12 @@ recent entry in the table and did not insert any new entries, the Base will be
greater than the Required Insert Count, so the delta will be positive and the
sign bit is set to 0.

The value of Base MUST NOT be negative. Though the protocol might operate
correctly with a negative base using post-base indexing, it is unnecessary and
inefficient. An endpoint MUST treat a field block with an S bit of 1 as invalid
if the value of Required Insert Count is less than or equal to the value of
Delta Base.

An encoder that produces table updates before encoding a field section might set
Base to the value of Required Insert Count. In such a case, both the sign bit
and the Delta Base will be set to zero.
Expand Down