Skip to content

0rtt after retry #1208

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

Merged
seanturner merged 3 commits into from
Mar 15, 2018
Merged

0rtt after retry #1208

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6ea7707
Trial decryption on TLS stream for 0-RTT rejection
martinthomson Mar 15, 2018
910a81f
0-RTT is rejected with Retry and VN
martinthomson Mar 15, 2018
e0fcbe8
Reboot state
martinthomson Mar 15, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -597,6 +597,21 @@ A server MUST NOT use post-handshake client authentication (see Section 4.6.2 of
{{!TLS13}}).


## Rejecting 0-RTT

A server rejects 0-RTT by rejecting 0-RTT at the TLS layer. This results in
early exporter keys being unavailable, thereby preventing the use of 0-RTT for
QUIC.

A client that attempts 0-RTT MUST also consider 0-RTT to be rejected if it
receives a Retry or Version Negotiation packet.

When 0-RTT is rejected, all connection characteristics that the client assumed
might be incorrect. This includes the choice of application protocol, transport
parameters, and any application configuration. The client therefore MUST reset
the state of all streams, including application state bound to those streams.


## TLS Errors

Errors in the TLS connection SHOULD be signaled using TLS alerts on stream 0. A
Expand Down Expand Up @@ -1377,6 +1392,9 @@ that 0-RTT data has been rejected.

A server MUST NOT use 0-RTT keys to protect packets.

If a server rejects 0-RTT, then the TLS stream will not include any TLS records
protected with 0-RTT keys.


## Receiving Out-of-Order Protected Frames {#pre-hs-protected}

Expand Down