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

Early data with external PSK #1043

Closed
mattcaswell opened this issue Jul 5, 2017 · 1 comment
Closed

Early data with external PSK #1043

mattcaswell opened this issue Jul 5, 2017 · 1 comment

Comments

@mattcaswell
Copy link
Contributor

The Early Data Indication section contains this sentence:

The parameters for the 0-RTT data (symmetric cipher suite, ALPN
protocol, etc.) are the same as those which were negotiated in the
connection which established the PSK.

This implies to me that you can only do 0-RTT where the PSK was established via an earlier connection. In external PSK this is not the case. I don't think this interpretation was the intention.
@kaduk
Copy link
Contributor

kaduk commented Jul 5, 2017

This is stale text from before we allowed 0-RTT with external PSK, IIRC.

kaduk added a commit to kaduk/tls13-spec that referenced this issue Jul 21, 2017
@kaduk
Be more explicit about PSK requirements
fc68585 
Both for 0-RTT and 1-RTT.

Give NST- and externally-provisioned PSKs more uniform treatment.

Closes: tlswg#1040
Closes: tlswg#1043
@kaduk kaduk mentioned this issue Jul 21, 2017
Merged
@ekr ekr closed this as completed in #1061 Nov 13, 2017
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
2 participants
@kaduk @mattcaswell