Skip to content

Commit

Permalink
Allow RST_STREAM to be sent and received after FIN
Browse files Browse the repository at this point in the history
  • Loading branch information
Jana Iyengar committed Sep 19, 2017
1 parent 4c2e608 commit c15a611
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -2615,8 +2615,10 @@ Any frame type that mentions a stream ID can be sent in this state.
A stream that is in the "half-closed (local)" state MUST NOT be used for sending
on new STREAM frames. Retransmission of data that has already been sent on
STREAM frames is permitted. An endpoint MAY also send MAX_STREAM_DATA and
STOP_SENDING in this state.
STREAM frames is permitted. If the stream is canceled or reset while in this
state, a RST_STREAM frame MAY be sent. A RST_STREAM frame sent in this state
MUST carry the stream's final offset. An endpoint MAY also send MAX_STREAM_DATA
and STOP_SENDING in this state.
An endpoint that closes a stream MUST NOT send data beyond the final offset that
it has chosen, see {{state-closed}} for details.
Expand Down Expand Up @@ -2648,6 +2650,10 @@ closes a stream SHOULD be discarded. An endpoint MAY choose to limit the period
over which it ignores frames and treat frames that arrive after this time as
being in error.
An endpoint may receive a RST_STREAM after a FIN if the peer resets the stream
after sending a FIN on it. In this case, the endpoint MAY discard any data that
it already received on that stream.
An endpoint will know the final offset of the data it receives on a stream when
it reaches the "half-closed (remote)" state, see {{final-offset}} for details.
Expand Down

0 comments on commit c15a611

Please sign in to comment.