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

draft-ietf-quic-tls-34 : Client side behavior when 0-RTT was rejected by server #71

Open
kinokrt opened this issue May 7, 2024 · 0 comments
Open

draft-ietf-quic-tls-34 : Client side behavior when 0-RTT was rejected by server #71

kinokrt opened this issue May 7, 2024 · 0 comments

Comments

@kinokrt
Copy link

kinokrt commented May 7, 2024 •
edited
Loading

According to draft-ietf-quic-tls-34:

[4.6.2. ][Accepting and Rejecting 0-RTT]
...
...
When 0-RTT was rejected, a client SHOULD treat receipt of an acknowledgement for a 0-RTT packet as a connection error of type PROTOCOL_VIOLATION, if it is able to detect the condition.
...
...

Could you point me how is this implemented in QUICHE?
@kinokrt kinokrt changed the title draft-ietf-quic-tls-34 : Client side behavior when 0-RTT (early data) was rejected by server draft-ietf-quic-tls-34 : Client side behavior when 0-RTT was rejected by server May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kinokrt