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

Confusing duplication in TLS Encryption Level Changes #3816

Closed
MikeBishop opened this issue Jul 2, 2020 · 1 comment · Fixed by #3819
Closed

Confusing duplication in TLS Encryption Level Changes #3816

MikeBishop opened this issue Jul 2, 2020 · 1 comment · Fixed by #3819
Labels
-tls editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing

Comments

@MikeBishop
Copy link
Contributor

The first two sentences of QUIC-TLS, Section 4.1.4 clearly intend to say different things, but I can't figure out the distinction. Is there a way we could reword them to make them clearer?

As keys for new encryption levels become available, TLS provides QUIC with those
keys. Separately, as keys at a given encryption level become available to TLS,
TLS indicates to QUIC that reading or writing keys at that encryption level are
available.
@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -tls labels Jul 2, 2020
@martinthomson
Copy link
Member

I think that this is not separately at all. Let's reduce that to a single statement.

martinthomson added a commit that referenced this issue Jul 3, 2020
@martinthomson
Reduce and un-separate
7962f3e 
These two statements are - to the extent that I can best determine -
redundant.  One is better.

Closes #3816.
@martinthomson martinthomson mentioned this issue Jul 3, 2020
Merged
@larseggert larseggert added this to Triage in Late Stage Processing via automation Jul 3, 2020
@larseggert larseggert moved this from Triage to Editorial Issues in Late Stage Processing Jul 3, 2020
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-tls editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reduce and un-separate quicwg/base-drafts
2 participants
@martinthomson @MikeBishop