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

TLS dependencies and packet number encryption #1669

Closed
mirjak opened this issue Aug 16, 2018 · 3 comments
Closed

TLS dependencies and packet number encryption #1669

mirjak opened this issue Aug 16, 2018 · 3 comments
Labels
-tls -transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@mirjak
Copy link
Contributor

mirjak commented Aug 16, 2018

Given that PN encryption is not TLS specific and could/should be performed the same way even if a different crypto handshake protocol is used, I wonder if that part should rather go in the tranport draft. Not that the tls draft is actually named "Using Transport Layer Security (TLS) to Secure QUIC".

@mikkelfj
Copy link
Contributor

The same argument could be made about transport parameters.

@MikeBishop
Copy link
Contributor

@mikkelfj, transport parameters are in the transport doc. The TLS doc simply defines a TLS extension capable of transporting the blob QUIC hands it. That bit is TLS-specific.

I tend to think that all of packet protection belongs in the transport document, not the TLS document. TLS produces keys; QUIC consumes keys from its crypto handshake (which in this version is TLS).

@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport -tls labels Aug 16, 2018
@martinthomson
Copy link
Member

One of the pieces of restructuring we have considered is moving the packet protection completely across. That's tracked by #411. We'll address that there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-tls -transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

No branches or pull requests

4 participants