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 all commits
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
11 changes: 6 additions & 5 deletions rfc9114.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1137,10 +1137,11 @@ create additional streams as allowed by their peer.

If the stream header indicates a stream type that is not supported by the
recipient, the remainder of the stream cannot be consumed as the semantics are
unknown. Recipients of unknown stream types MAY abort reading of the stream with
an error code of H3_STREAM_CREATION_ERROR or a reserved error code
({{http-error-codes}}), but the recipients MUST NOT consider such streams to be
a connection error of any kind.
unknown. Recipients of unknown stream types MUST either abort reading of the
stream or discard incoming data without further processing. If reading is
aborted, the recipient SHOULD use the H3_STREAM_CREATION_ERROR error code or a
reserved error code ({{http-error-codes}}). The recipient MUST NOT consider
unknown stream types to be a connection error of any kind.

As certain stream types can affect connection state, a recipient SHOULD NOT
discard data from incoming unidirectional streams prior to reading the stream
Expand Down Expand Up @@ -1789,7 +1790,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 frames and 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