Skip to content

Commit

Permalink
[HTTP/3] [editorial] Remove mention of redefining setting format.
Browse files Browse the repository at this point in the history
Each SETTINGS parameter consists of an identifier and a value, each
encoded as QUIC variable-length integer.  The sentence being removed is
a remnant from the time when setting values were encoded as
length-prefixed binary blobs.
  • Loading branch information
bnc-google committed Nov 11, 2019
1 parent 05201a3 commit 3248243
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions draft-ietf-quic-http.md
Original file line number Diff line number Diff line change
Expand Up @@ -1940,8 +1940,7 @@ SETTINGS_MAX_HEADER_LIST_SIZE:
In HTTP/3, setting values are variable-length integers (6, 14, 30, or 62 bits
long) rather than fixed-length 32-bit fields as in HTTP/2. This will often
produce a shorter encoding, but can produce a longer encoding for settings which
use the full 32-bit space. Settings ported from HTTP/2 might choose to redefine
the format of their settings to avoid using the 62-bit encoding.
use the full 32-bit space.

Settings need to be defined separately for HTTP/2 and HTTP/3. The IDs of
settings defined in {{!HTTP2}} have been reserved for simplicity. Note that
Expand Down

0 comments on commit 3248243

Please sign in to comment.