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.

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

RST_STREAM vs PROTOCOL_ERROR #1119

Closed
mikkelfj opened this issue Feb 18, 2018 · 0 comments
Closed

RST_STREAM vs PROTOCOL_ERROR #1119

mikkelfj opened this issue Feb 18, 2018 · 0 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@mikkelfj
Copy link
Contributor

mikkelfj commented Feb 18, 2018

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.

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Feb 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

No branches or pull requests

2 participants