Subject: [quicwg/base-drafts] RST_STREAM vs PROTOCOL_ERROR (#1119)

From: MikkelFJ <[email-masked]>
Date: Sun, 18 Feb 2018 08:59:54 -0800

It seems vaguae that a stream might be reset in favor of a protocol violation but this seems to be possible via the text in sectin 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.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1119