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

Editorial Fix for QUIC-Transport #3902

Closed
Jxck opened this issue Jul 14, 2020 · 0 comments · Fixed by #4003
Closed

Editorial Fix for QUIC-Transport #3902

Jxck opened this issue Jul 14, 2020 · 0 comments · Fixed by #4003
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@Jxck
Copy link

Jxck commented Jul 14, 2020

An endpoint might send a CONNECTION_CLOSE frame in an Initial packet or in response to unauthenticated information received in Initial or Handshake packets.

A or in B in C or D is hard to read.

  1. [A | in B in C | D]
  2. [A | in B in [C | D]]
  3. [A | in B [in C | D]]
  4. ...
@LPardue LPardue added this to Triage in Late Stage Processing Jul 14, 2020
@MikeBishop MikeBishop added -http editorial An issue that does not affect the design of the protocol; does not require consensus. labels Jul 14, 2020
@project-bot project-bot bot moved this from Triage to Editorial Issues in Late Stage Processing Jul 14, 2020
martinthomson added a commit that referenced this issue Aug 17, 2020
This sentence structure was unnecessarily byzantine.

Closes #3902.
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Aug 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Development

Successfully merging a pull request may close this issue.

3 participants