-
Notifications
You must be signed in to change notification settings - Fork 697
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
Quiche drops the packet with OOB stream id instead of sending CONNECTION_CLOSE #565
Comments
Also slightly refactor existing check to avoid repeating the same constant over and over. Fixes #565.
https://tools.ietf.org/html/draft-ietf-quic-transport-29#section-19.11-5 says
So I think this needs to be FRAME_ENCODING_ERROR, not STREAM_LIMIT_ERROR. |
Also slightly refactor existing check to avoid repeating the same constant over and over. Fixes #565.
This also changes the error used when the stream limit is exceeded as per the latest draft. Also slightly refactor existing check to avoid repeating the same constant over and over. Fixes #565.
This also changes the error used when the stream limit is exceeded as per the latest draft. Also slightly refactor existing check to avoid repeating the same constant over and over. Fixes #565.
The draft specifies both the error codes for this scenario For example, below is from section 4.5
Either should be fine, I think. |
Good point, I tend to agree either seems fine. I opened an issue on the QUIC specs to suggest it clarifies the text on this matter but I don't think the outcome affects the quiche PR; I'd be happy with either. |
This also changes the error used when the stream limit is exceeded as per the latest draft. Also slightly refactor existing check to avoid repeating the same constant over and over. Fixes #565.
When we inject a MAX_STREAMS frame with a value greater than 2^60 . The QUIC library must close the connection immediately with a connection error STREAM_LIMIT_ERROR.
Example,
MAX_STREAMS_BIDI[id=1152921504606846977]
Similar test for injecting OOB STREAMS_BLOCKED has same result, i.e. the packet is dropped without connection close.
The text was updated successfully, but these errors were encountered: