You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should probably have some normative text on the reaction to STOP_SENDING. In general, RFC9000 senders should respond to STOP_SENDING with an immediate RESET_STREAM.
If the receiver has indicated it doesn't want the bytes the sender thinks are reliable, what then?
I'm leaning towards sending RESET_STREAM_AT with any desired reliable_size, regardless of receiver intent, but I don't feel strongly about it.
The text was updated successfully, but these errors were encountered:
We should probably have some normative text on the reaction to STOP_SENDING. In general, RFC9000 senders should respond to STOP_SENDING with an immediate RESET_STREAM.
If the receiver has indicated it doesn't want the bytes the sender thinks are reliable, what then?
I'm leaning towards sending RESET_STREAM_AT with any desired reliable_size, regardless of receiver intent, but I don't feel strongly about it.
The text was updated successfully, but these errors were encountered: