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.

Sign up for GitHub

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

Jump to bottom

allow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame #3186

Merged
merged 1 commit into from Dec 9, 2019
Merged

allow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame #3186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -4985,7 +4985,8 @@ level is treated as a separate CRYPTO stream of data.

The largest offset delivered on a stream - the sum of the offset and data
length - cannot exceed 2^62-1. Receipt of a frame that exceeds this limit MUST
be treated as a connection error of type FRAME_ENCODING_ERROR.
be treated as a connection error of type FRAME_ENCODING_ERROR or
CRYPTO_BUFFER_EXCEEDED.

Unlike STREAM frames, which include a Stream ID indicating to which stream the
data belongs, the CRYPTO frame carries data for a single stream per encryption
Expand Down