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

describe how 0-RTT is accepted and rejected #2841

Merged
merged 16 commits into from Aug 16, 2019
Merged

describe how 0-RTT is accepted and rejected #2841

Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
1585f08
describe how 0-RTT is accepted and rejected
marten-seemann Jun 24, 2019
de85a4b
s/with/without for rejecting 0-RTT
marten-seemann Jun 25, 2019
94cbd5a
error when 0-RTT is acked when 0-RTT is rejected
marten-seemann Jun 25, 2019
6facb9d
remove normative language for receiving 0-RTT packets
marten-seemann Jun 25, 2019
c0b38a3
add a paragraph describing how a client enables 0-RTT
marten-seemann Jun 25, 2019
a6c47ee
capitalize all words in section title
marten-seemann Jun 25, 2019
9440ab9
s/EarlyDataIndication/early_data extension/g
marten-seemann Jun 25, 2019
5fa9df2
clients SHOULD detect ACKs for 0-RTT packets after 0-RTT rejection
marten-seemann Jun 25, 2019
6ec7024
a client sends 0-RTT packets, not early data
marten-seemann Jun 25, 2019
c9386c4
*an* early_data extension
marten-seemann Jun 26, 2019
32a7bb0
rejecting 0-RTT means not generating 0-RTT keys
marten-seemann Jun 26, 2019
2ddaf6d
apply @kazuho's suggestions
marten-seemann Jun 26, 2019
0400ce1
early_data is sent in the EE, not the SH
marten-seemann Jun 26, 2019
607a9f4
another fix for early_data being sent in EE, not SH
marten-seemann Jun 26, 2019
9c7fa1a
fix reference to RFC 8446
marten-seemann Jun 26, 2019
025b18e
Merge branch 'master' into accept-and-reject-0-rtt
martinthomson Jul 9, 2019
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: 2 additions & 2 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -621,8 +621,8 @@ as a connection error of type PROTOCOL_VIOLATION.
## Accepting and rejecting 0-RTT
marten-seemann marked this conversation as resolved.
Show resolved Hide resolved

A server accepts 0-RTT by sending the EarlyDataIndication in the ServerHello
marten-seemann marked this conversation as resolved.
Show resolved Hide resolved
(see Section 4.10.2 of {{!TLS13}}). A server that accepts 0-RTT MUST process and
acknowledge all 0-RTT packets that it receives.
(see Section 4.10.2 of {{!TLS13}}). The server then processes and acknowledges
marten-seemann marked this conversation as resolved.
Show resolved Hide resolved
the 0-RTT packets that it receives.

A server rejects 0-RTT by sending a ServerHello without the EarlyDataIndication.
marten-seemann marked this conversation as resolved.
Show resolved Hide resolved
A server will always reject 0-RTT if it sends a TLS HelloRetryRequest. When
Expand Down