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

Can CRYPTO frames be sent in 0-RTT packets? #2959

Closed
tandf opened this issue Aug 8, 2019 · 0 comments · Fixed by #2960
Closed

Can CRYPTO frames be sent in 0-RTT packets? #2959

tandf opened this issue Aug 8, 2019 · 0 comments · Fixed by #2960
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@tandf
Copy link
Contributor

tandf commented Aug 8, 2019

In quic-transport-22 section 19.6 it says CRYPTO frames can be sent in all packet types.

The CRYPTO frame (type=0x06) is used to transmit cryptographic handshake messages. It can be sent in all packet types.

However in quic-tls-22 section 4 it says the CRYPTO frames can't be sent in 0-RTT packets.

CRYPTO and CONNECTION_CLOSE frames MAY appear in packets of any encryption level except 0-RTT.

Also in quic-tls-22 section 8.3, similar statement.

A server MUST treat receipt of a CRYPTO frame in a 0-RTT packet as a connection error of type PROTOCOL_VIOLATION.

Maybe the statement in quic-transport-22 needs to be corrected?

@martinthomson martinthomson added -transport editorial An issue that does not affect the design of the protocol; does not require consensus. labels Aug 8, 2019
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

Successfully merging a pull request may close this issue.

2 participants