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 is permitted for Ready streams #2354

Merged
merged 3 commits into from Jan 22, 2019
Merged

STOP_SENDING is permitted for Ready streams #2354

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c341422
STOP_SENDING is permitted for Ready streams
martinthomson Jan 21, 2019
387bdf4
Make the same changes for MAX_STREAM_DATA
martinthomson Jan 21, 2019
1002e76
My grammar isn't that good
martinthomson Jan 21, 2019
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
31 changes: 14 additions & 17 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -4479,16 +4479,15 @@ Final Size:
## STOP_SENDING Frame {#frame-stop-sending}

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.
data is being discarded on receipt at application request. STOP_SENDING
requests that a peer cease transmission on a stream.

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
stream that is "Ready" or not yet created MUST be treated as a connection error
of type STREAM_STATE_ERROR. An endpoint that receives a STOP_SENDING frame for
a receive-only stream MUST terminate the connection with error
STREAM_STATE_ERROR.
A STOP_SENDING frame can be sent for streams in the Recv or Size Known states
(see {{stream-send-states}}). Receiving a STOP_SENDING frame for a
locally-initiated stream that has not yet been created MUST be treated as a
connection error of type STREAM_STATE_ERROR. An endpoint that receives a
STOP_SENDING frame for a receive-only stream MUST terminate the connection with
error STREAM_STATE_ERROR.

The STOP_SENDING frame is as follows:

Expand Down Expand Up @@ -4700,14 +4699,12 @@ the initial limits (see {{zerortt-parameters}}).
The MAX_STREAM_DATA frame (type=0x11) is used in flow control to inform a peer
of the maximum amount of data that can be sent on a stream.

An endpoint that receives a MAX_STREAM_DATA frame for a receive-only stream
MUST terminate the connection with error STREAM_STATE_ERROR.

An endpoint that receives a MAX_STREAM_DATA frame for a send-only stream
it has not opened MUST terminate the connection with error STREAM_STATE_ERROR.

Note that an endpoint may legally receive a MAX_STREAM_DATA frame on a
bidirectional stream it has not opened.
A MAX_STREAM_DATA frame can be sent for streams in the Recv state (see
{{stream-send-states}}). Receiving a MAX_STREAM_DATA frame for a
locally-initiated stream that has not yet been created MUST be treated as a
connection error of type STREAM_STATE_ERROR. An endpoint that receives a
MAX_STREAM_DATA frame for a receive-only stream MUST terminate the connection
with error STREAM_STATE_ERROR.

The MAX_STREAM_DATA frame is as follows:

Expand Down