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

Refine STOP_SENDING reaction text #2361

Merged
merged 1 commit into from Jan 23, 2019
Merged

Refine STOP_SENDING reaction text #2361

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
12 changes: 8 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -647,10 +647,14 @@ upon receipt.

A STOP_SENDING frame requests that the receiving endpoint send a RESET_STREAM
frame. An endpoint that receives a STOP_SENDING frame MUST send a RESET_STREAM
frame for that stream. An endpoint SHOULD copy the error code from the
STOP_SENDING frame, but MAY use any application error code. The endpoint
that sends a STOP_SENDING frame can ignore the error code carried in any
RESET_STREAM frame it receives.
frame if the stream is in the Ready or Send state. If the stream is in the Data
Sent state and any outstanding data is declared lost, an endpoint SHOULD send a
RESET_STREAM frame in lieu of a retransmission.

An endpoint SHOULD copy the error code from the STOP_SENDING frame to the
RESET_STREAM frame it sends, but MAY use any application error code. The
endpoint that sends a STOP_SENDING frame MAY ignore the error code carried in
any RESET_STREAM frame it receives.

If the STOP_SENDING frame is received on a stream that is already in the
"Data Sent" state, an endpoint that wishes to cease retransmission of
Expand Down