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

Do not use undefined term "successful processing" #1589

Merged
merged 2 commits into from
Jul 31, 2018
Merged

Do not use undefined term "successful processing" #1589

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
edd98c6
Do not use undefined term "successful processing"
Jul 20, 2018
e7e3ab6
Merge branch 'master' into 201807192239-rephrase-successful-processing
afrind Jul 24, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-quic-qpack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,12 +289,12 @@ SHOULD treat this as a stream error of type HTTP_QPACK_DECOMPRESSION_FAILED.
The decoder stream signals key events at the decoder that permit the encoder to
track the decoder's state. These events are:

- Successful processing of a header block
- Complete processing of a header block
- Abandonment of a stream which might have remaining header blocks
- Receipt of new dynamic table entries

Regardless of whether a header block contained blocking references, the
knowledge that it was processed successfully permits the encoder to evict
knowledge that it has been processed permits the encoder to evict
entries to which no unacknowledged references remain; see {{blocked-eviction}}.
When a stream is reset or abandoned, the indication that these header blocks
will never be processed serves a similar function; see {{stream-cancellation}}.
Expand Down