Skip to content

application protocols might constrain use of RESET_STREAM_AT #68

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

Merged
merged 1 commit into from
Feb 18, 2024
Merged

application protocols might constrain use of RESET_STREAM_AT #68

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 6 additions & 0 deletions draft-ietf-quic-reliable-stream-reset.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,6 +196,12 @@ bit for the same stream, the initiator MUST NOT change the Application Error
Code or the Final Size. If the receiver detects a change in those fields, it
MUST close the connection with a connection error of type STREAM_STATE_ERROR.

While multiple RESET_STREAM_AT frames can reduce Reliable Size, some
applications might need to ensure that a minimum amount of data is always
delivered on a stream. Application protocols can establish rules for streams
that ensure that Reliable Size is not reduced below a certain threshold if that
is necessary to ensure correct operation of the protocol.

## Stream States {#stream-states}

In terms of stream state transitions ({{Section 3 of RFC9000}}), the effect of a
Expand Down