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

Don't require RESET_STREAM on terminated streams #3165

Merged
merged 1 commit into from
Oct 29, 2019
Merged

Don't require RESET_STREAM on terminated streams #3165

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
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -361,17 +361,17 @@ On the sending part of a stream, application protocols need to be able to:

- write data, understanding when stream flow control credit
({{data-flow-control}}) has successfully been reserved to send the written
data
data;
- end the stream (clean termination), resulting in a STREAM frame
({{frame-stream}}) with the FIN bit set; and
- reset the stream (abrupt termination), resulting in a RESET_STREAM frame
({{frame-reset-stream}}), even if the stream was already ended.
({{frame-reset-stream}}), if the stream was not already in a terminal state.

On the receiving part of a stream, application protocols need to be able to:

- read data
- read data; and
- abort reading of the stream and request closure, possibly resulting in a
STOP_SENDING frame ({{frame-stop-sending}})
STOP_SENDING frame ({{frame-stop-sending}}).

Applications also need to be informed of state changes on streams, including
when the peer has opened or reset a stream, when a peer aborts reading on a
Expand Down