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

No "field" #4770

Merged
merged 3 commits into from Jan 22, 2021
Merged
Changes from 1 commit
Commits
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
20 changes: 10 additions & 10 deletions draft-ietf-quic-qpack.md
Expand Up @@ -148,7 +148,7 @@ Field section:
: An ordered collection of HTTP field lines associated with an HTTP message. A
field section can contain multiple field lines with the same name. It can
also contain duplicate field lines. An HTTP message can include both header
field and trailer field sections.
and trailer sections.

Representation:

Expand Down Expand Up @@ -207,15 +207,15 @@ decoder and vice versa.

## Encoder

An encoder converts a header or trailer field section into a series of
representations by emitting either an indexed or a literal representation for
each field line in the list; see {{field-line-representations}}. Indexed
representations achieve high compression by replacing the literal name and
possibly the value with an index to either the static or dynamic table.
References to the static table and literal representations do not require any
dynamic state and never risk head-of-line blocking. References to the dynamic
table risk head-of-line blocking if the encoder has not received an
acknowledgment indicating the entry is available at the decoder.
An encoder converts a header or trailer section into a series of representations
by emitting either an indexed or a literal representation for each field line in
the list; see {{field-line-representations}}. Indexed representations achieve
high compression by replacing the literal name and possibly the value with an
index to either the static or dynamic table. References to the static table and
literal representations do not require any dynamic state and never risk
head-of-line blocking. References to the dynamic table risk head-of-line
blocking if the encoder has not received an acknowledgment indicating the entry
is available at the decoder.

An encoder MAY insert any entry in the dynamic table it chooses; it is not
limited to field lines it is compressing.
Expand Down