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

Clarify why post-handshake client auth is banned #3044

Merged

Conversation

DavidSchinazi
Copy link
Contributor

@DavidSchinazi DavidSchinazi commented Sep 17, 2019

Add short explanation and reference to explain why QUIC-TLS bans the use of post-handshake client authentication.

Fixes #2367.

Copy link
Member

@martinthomson martinthomson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to say that this is editorial-enough to just merge. MUST NOT implies PROTOCOL_VIOLATION, so the new normative language is fine as editorial. I'll give others a chance to disagree though.

draft-ietf-quic-tls.md Outdated Show resolved Hide resolved
draft-ietf-quic-tls.md Outdated Show resolved Hide resolved
Co-Authored-By: Martin Thomson <mt@lowentropy.net>
@ianswett ianswett added the -tls label Sep 17, 2019
@martinthomson martinthomson added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Oct 16, 2019
@martinthomson martinthomson merged commit a2ea7d7 into quicwg:master Oct 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-tls editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Text banning post-handshake client auth is unclear
5 participants