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

STOPPING is sent by transport not application #863

Merged
merged 1 commit into from Oct 12, 2017
Merged

STOPPING is sent by transport not application #863

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2687,10 +2687,10 @@ frames count toward flow control.

STOP_SENDING can only be sent for any stream that is not "idle", however it is
mostly useful for streams in the "open" or "half-closed (local)" states. A
STOP_SENDING frame requests that the receiving application send a RST_STREAM
frame. An endpoint that receives a STOP_SENDING frame MUST send a RST_STREAM
frame for that stream with an error code of STOPPING. If the STOP_SENDING frame
is received on a stream that is already in the "half-closed (local)" or "closed"
STOP_SENDING frame requests that the receiving endpoint send a RST_STREAM frame.
An endpoint that receives a STOP_SENDING frame MUST send a RST_STREAM frame for
that stream with an error code of STOPPING. If the STOP_SENDING frame is
received on a stream that is already in the "half-closed (local)" or "closed"
states, a RST_STREAM frame MAY still be sent in order to cancel retransmission
of previously-sent STREAM frames.

Expand Down