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

Clarify unknown unidirectional stream handling #4942

Merged
merged 4 commits into from
Feb 16, 2022
Merged

Clarify unknown unidirectional stream handling #4942

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7096acc
How to handle unknown stream type errors
MikeBishop Nov 2, 2021
2031eed
Section 9 alignment with Section 6.2
MikeBishop Nov 2, 2021
cacdd9b
and/or
MikeBishop Nov 15, 2021
070c6ee
Merge remote-tracking branch 'origin/h3qp_auth48' into http/unknown_uni
MikeBishop Feb 16, 2022
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
24 changes: 12 additions & 12 deletions draft-ietf-quic-http.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1223,16 +1223,16 @@ stream. This section describes HTTP/3 frame formats and their permitted stream
types; see {{stream-frame-mapping}} for an overview. A comparison between
HTTP/2 and HTTP/3 frames is provided in {{h2-frames}}.

| Frame | Control Stream | Request Stream | Push Stream | Section |
| -------------- | -------------- | -------------- | ----------- | ------------------------ |
| DATA | No | Yes | Yes | {{frame-data}} |
| HEADERS | No | Yes | Yes | {{frame-headers}} |
| CANCEL_PUSH | Yes | No | No | {{frame-cancel-push}} |
| SETTINGS | Yes (1) | No | No | {{frame-settings}} |
| PUSH_PROMISE | No | Yes | No | {{frame-push-promise}} |
| GOAWAY | Yes | No | No | {{frame-goaway}} |
| MAX_PUSH_ID | Yes | No | No | {{frame-max-push-id}} |
| Reserved | Yes | Yes | Yes | {{frame-reserved}} |
| Frame | Control Stream | Request Stream | Push Stream | Section |
| ------------ | -------------- | -------------- | ----------- | ---------------------- |
| DATA | No | Yes | Yes | {{frame-data}} |
| HEADERS | No | Yes | Yes | {{frame-headers}} |
| CANCEL_PUSH | Yes | No | No | {{frame-cancel-push}} |
| SETTINGS | Yes (1) | No | No | {{frame-settings}} |
| PUSH_PROMISE | No | Yes | No | {{frame-push-promise}} |
| GOAWAY | Yes | No | No | {{frame-goaway}} |
| MAX_PUSH_ID | Yes | No | No | {{frame-max-push-id}} |
| Reserved | Yes | Yes | Yes | {{frame-reserved}} |
{: #stream-frame-mapping title="HTTP/3 Frames and Stream Type Overview"}

The SETTINGS frame can only occur as the first frame of a Control stream; this
Expand Down Expand Up @@ -1772,7 +1772,7 @@ managing these extension points: frame types ({{iana-frames}}), settings
({{iana-stream-types}}).

Implementations MUST ignore unknown or unsupported values in all extensible
protocol elements. Implementations MUST discard data and/or abort reading on
protocol elements. Implementations MUST discard data or abort reading on
unidirectional streams that have unknown or unsupported types. This means that
any of these extension points can be safely used by extensions without prior
arrangement or negotiation. However, where a known frame type is required to be
Expand Down Expand Up @@ -2087,7 +2087,7 @@ its semantics, including any parts of the frame that are conditionally present.
The entries in {{iana-frame-table}} are registered by this document.

| ------------ | ------- | -------------------------- |
| Frame Type | Value | Specification |
| Frame Type | Value | Specification |
| ------------ | :-----: | -------------------------- |
| DATA | 0x00 | {{frame-data}} |
| HEADERS | 0x01 | {{frame-headers}} |
Expand Down