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

Replace SETTINGS with EXTENDED_SETTINGS #80

Merged
merged 8 commits into from Dec 15, 2016
Merged

Replace SETTINGS with EXTENDED_SETTINGS #80

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
a48d8c2
Replace SETTINGS with EXTENDED_SETTINGS
MikeBishop Dec 9, 2016
6915f0e
Use a different example
MikeBishop Dec 9, 2016
b5ec771
Martin's other feedback
MikeBishop Dec 9, 2016
7166f37
Merge branch 'master' into extended_settings
MikeBishop Dec 12, 2016
9d08e3d
Diagram format for #54 again.
MikeBishop Dec 12, 2016
334bca2
Wording changes for Patrick
MikeBishop Dec 15, 2016
a5b2ff0
Possible SETTINGS_ACK proposal (#84)
MikeBishop Dec 15, 2016
10851ab
More of Patrick's and Martin's feedback.
MikeBishop Dec 15, 2016
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
10 changes: 5 additions & 5 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -443,11 +443,11 @@ is substantially different from {{!RFC7540}}. Individually, a SETTINGS parameter
can also be referred to as a "setting".

SETTINGS parameters are not negotiated; they describe characteristics of the
sending peer, which are used by the receiving peer. However, a negotiation can
be implied by the use of SETTINGS -- a peer uses SETTINGS to advertise a set of
supported values. The recipient can then choose which entries from this list are
also acceptable and proceed with the value it has chosen. (This choice could be
announced in a field of an extension frame, or in a value in SETTINGS.)
sending peer, which can be used by the receiving peer. However, a negotiation
can be implied by the use of SETTINGS -- a peer uses SETTINGS to advertise a set
of supported values. The recipient can then choose which entries from this list
are also acceptable and proceed with the value it has chosen. (This choice could
be announced in a field of an extension frame, or in its own value in SETTINGS.)

Different values for the same parameter can be advertised by each peer. For
example, a client might permit a very large HPACK state table while a server
Expand Down