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

fix MUST not in CRYPTO frame handling #3656

Merged
merged 1 commit into from May 14, 2020
Merged

fix MUST not in CRYPTO frame handling #3656

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
2 changes: 1 addition & 1 deletion draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -447,7 +447,7 @@ network, it proceeds as follows:
find the proper location in the data sequence. If the result of this process
is that new data is available, then it is delivered to TLS in order.

- If the packet is from a previously installed encryption level, it MUST not
- If the packet is from a previously installed encryption level, it MUST NOT
contain data which extends past the end of previously received data in that
flow. Implementations MUST treat any violations of this requirement as a
connection error of type PROTOCOL_VIOLATION.
Expand Down