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

Ben Kaduk's TLS Comment 33 #4594

Closed
LPardue opened this issue Jan 6, 2021 · 2 comments
Closed

Ben Kaduk's TLS Comment 33 #4594

LPardue opened this issue Jan 6, 2021 · 2 comments
Labels
-tls iesg An issue raised during IESG review.
Projects
Late Stage Processing
Milestone
tls-iesg

Comments

@LPardue
Copy link
Member

LPardue commented Jan 6, 2021

@kaduk said:

Abstract

I think this document also specifies some generic bits about how QUIC
uses cryptography, that are not directly related to TLS integration.
@LPardue LPardue added -tls iesg An issue raised during IESG review. labels Jan 6, 2021
@LPardue LPardue added this to the tls-iesg milestone Jan 6, 2021
@martinthomson
Copy link
Member

I'm happy with the abstract without the extra detail.

@seanturner
Copy link
Contributor

I agree. If there is a Using [insert your favorite security protocol] with QUIC, they are going to need to figure out which bits need to go in their document anyway.

@larseggert larseggert added this to Triage in Late Stage Processing via automation Jan 11, 2021
Late Stage Processing automation moved this from Triage to Issue Handled Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-tls iesg An issue raised during IESG review.
Projects
Late Stage Processing
  
Issue Handled
Milestone
tls-iesg
Development

No branches or pull requests
3 participants
@martinthomson @seanturner @LPardue