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

Clarify OOO CRYPTO data handling #1787

Closed
wants to merge 2 commits into from
Closed

Clarify OOO CRYPTO data handling #1787

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9acc7c1
Clarify OOO CRYPTO data handling
martinduke Sep 21, 2018
97943b1
Changed "received" to "processed"
martinduke Sep 21, 2018
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
4 changes: 4 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3710,6 +3710,10 @@ functionally identical to STREAM frames, except that they do not bear a stream
identifier; they are not flow controlled; and they do not carry markers for
optional offset, optional length, and the end of the stream.

If a QUIC endpoint processses a CRYPTO frame for a cryptographic context, having
already processed a CRYPTO frame in a more secure context, it MUST drop the data
in the frame without delivering it to TLS for processing.

A CRYPTO frame is shown below.

~~~
Expand Down