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 reserved frame streams #4235

Merged
merged 2 commits into from
Oct 19, 2020
Merged

Clarify reserved frame streams #4235

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e21668
Clarify reserved frame streams
MikeBishop Oct 16, 2020
cee2add
Update draft-ietf-quic-http.md
MikeBishop Oct 19, 2020
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 draft-ietf-quic-http.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -470,7 +470,8 @@ Header and trailer field sections are described in Sections 5.4 and 5.6 of
Receipt of an invalid sequence of frames MUST be treated as a connection error
of type H3_FRAME_UNEXPECTED ({{errors}}). In particular, a DATA frame before
any HEADERS frame, or a HEADERS or DATA frame after the trailing HEADERS frame
is considered invalid.
is considered invalid. Other frame types, especially unknown frame types,
might be permitted subject to their own rules; see {{extensions}}.

A server MAY send one or more PUSH_PROMISE frames ({{frame-push-promise}})
before, after, or interleaved with the frames of a response message. These
Expand Down Expand Up @@ -1614,10 +1615,10 @@ a connection error of type H3_ID_ERROR.

Frame types of the format `0x1f * N + 0x21` for non-negative integer values of N
are reserved to exercise the requirement that unknown types be ignored
({{extensions}}). These frames have no semantics, and can be sent on any open
stream when application-layer padding is desired. They MAY also be sent on open
streams in connections where no data is currently being transferred. Endpoints
MUST NOT consider these frames to have any meaning upon receipt.
({{extensions}}). These frames have no semantics, and MAY be sent on any stream
where frames are allowed to be sent. This enables their use for
application-layer padding. Endpoints MUST NOT consider these frames to have any
meaning upon receipt.

The payload and length of the frames are selected in any manner the
implementation chooses.
Expand Down