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

STOP_SENDING opens streams #2013

Merged
merged 3 commits into from Nov 19, 2018
Merged

STOP_SENDING opens streams #2013

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
06b4cbd
STOP_SENDING opens streams
MikeBishop Nov 15, 2018
c149b56
Apply suggestions from code review
martinthomson Nov 19, 2018
a172c5a
Rewrap from GH suggestions
MikeBishop Nov 19, 2018
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -4280,8 +4280,8 @@ An endpoint uses a STOP_SENDING frame (type=0x05) to communicate that incoming
data is being discarded on receipt at application request. This signals a peer
to abruptly terminate transmission on a stream.

Receipt of a STOP_SENDING frame is invalid for a locally-initiated stream which
does not exist or is in the "Ready" state (see {{stream-send-states}}).
Receipt of a STOP_SENDING frame is invalid for a locally-initiated stream that
has not yet been created or is in the "Ready" state (see {{stream-send-states}}).
Receiving a STOP_SENDING frame for a locally-initiated send stream that is
"Ready" or non-existent MUST be treated as a connection error of type
PROTOCOL_VIOLATION. An endpoint that receives a STOP_SENDING frame for a
Expand Down