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

Add more TLS-specifics #59

Open
rmarx opened this issue Feb 26, 2020 · 1 comment
Open

Add more TLS-specifics #59

rmarx opened this issue Feb 26, 2020 · 1 comment
Assignees
Labels
future-versions issue will be tackled but not for the current iteration

Comments

@rmarx
Copy link
Contributor

rmarx commented Feb 26, 2020

Currently, we have few options for logging a lot of TLS related data (e.g., cipher suites, supported groups, (E)SNI, ...).

Need to figure out a generic form for TLS (extensions) data so it can be logged using qlog as well.

Note: this is getting in the "new TCP+TLS+HTTP/2 schema" territory

@rmarx rmarx added the future-versions issue will be tackled but not for the current iteration label Sep 8, 2020
@marten-seemann
Copy link
Collaborator

Note that #27 suggests to add some resumption and 0-RTT events, which arguably are TLS-specific. They do however (at least 0-RTT does) change how the QUIC stack behaves, in pretty fundamental ways (namely sending and processing 0-RTT data, restoring transport parameters, etc.), which is a good justification for including these (but not other) events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future-versions issue will be tackled but not for the current iteration
Projects
None yet
Development

No branches or pull requests

2 participants