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

Eliminating double-muxing #71

Merged
merged 9 commits into from
Dec 8, 2016
Merged

Eliminating double-muxing #71

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
79540db
HTTP over QUIC, not HTTP/2 over QUIC
MikeBishop Dec 2, 2016
b086cad
Moving to a two-stream mapping with HPACK sequence numbers.
MikeBishop Dec 3, 2016
e1a8753
Fixing references.
MikeBishop Dec 3, 2016
49edae3
Minor tpyos
MikeBishop Dec 5, 2016
dddbdb8
PRIORITY has to be on control stream.
MikeBishop Dec 6, 2016
c2823e8
Exempt from connection-level flow control isn't exempt from *all* flo…
MikeBishop Dec 6, 2016
03c8ac6
Merge branch 'master' into http-unstraddled
MikeBishop Dec 6, 2016
77b11b3
Fixing priority reference again.
MikeBishop Dec 6, 2016
0fcaaeb
CONTINUATION, IANA
MikeBishop Dec 8, 2016
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
12 changes: 6 additions & 6 deletions draft-ietf-quic-http.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,8 +118,8 @@ The QUIC crypto handshake MUST use TLS {{QUIC-TLS}}.
While connection-level options pertaining to the core QUIC protocol are set in
the initial crypto handshake {{QUIC-TLS}}, HTTP-specific settings are conveyed
in the SETTINGS frame. After the QUIC connection is established, a SETTINGS
frame ({{SETTINGS}} MUST be sent as the initial frame of the HTTP control stream
(StreamID 3, see {{stream-mapping}}).
frame ({{SETTINGS}}) MUST be sent as the initial frame of the HTTP control
stream (StreamID 3, see {{stream-mapping}}).

# Stream Mapping and Usage {#stream-mapping}

Expand Down Expand Up @@ -356,7 +356,7 @@ Padding MUST NOT be used. The flags defined are:
: The Exclusive Flag (E), Stream Dependency, and Weight fields are present.

~~~~~~~~~~
+-+-------------+-----------------------------------------------+
+-+-------------------------------------------------------------+
|E| Stream Dependency? (31) |
+-+-------------+-----------------------------------------------+
| Weight? (8) |
Expand All @@ -375,7 +375,7 @@ The HEADERS frame payload has the following fields:

Stream Dependency:
: A 31-bit stream identifier for the stream that this stream depends on
(see [!RFC7540 Section 5.3). This field is only present if the PRIORITY
(see {{!RFC7540}} Section 5.3). This field is only present if the PRIORITY
flag is set.

Weight:
Expand Down Expand Up @@ -468,9 +468,9 @@ The PUSH_PROMISE frame (type=0x05) is used to carry a request header set from
server to client, as in HTTP/2. It defines no flags.

~~~~~~~~~~
+-+-------------+-----------------------------------------------+
+---------------------------------------------------------------+
| Promised Stream ID (32) |
+-+-----------------------------+-------------------------------+
+-------------------------------+-------------------------------+
| Sequence? (16) | Header Block (*) ...
+-------------------------------+-------------------------------+
~~~~~~~~~~
Expand Down