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
Perhaps clarify that RST_STREAM is only sent for application level errors and that any transport protocol violation such as, for example, sending a stream beyond MAX_STREAM_ID, MUST be closed with a PROTOCOL_ERROR message.
Some implementers might try to keep a connection alive as far as possible thus preferring RST_STREAM, but if protocol errors are not hard, it can lead to various interop errors.
The text was updated successfully, but these errors were encountered:
It seems vague that a stream might be reset in favor of a protocol violation but this seems to be possible via the text in section 12.2
https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#rfc.section.12.2
Perhaps clarify that RST_STREAM is only sent for application level errors and that any transport protocol violation such as, for example, sending a stream beyond MAX_STREAM_ID, MUST be closed with a PROTOCOL_ERROR message.
Some implementers might try to keep a connection alive as far as possible thus preferring RST_STREAM, but if protocol errors are not hard, it can lead to various interop errors.
The text was updated successfully, but these errors were encountered: