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

Notation synchronization #4866

Closed
martinthomson opened this issue Apr 27, 2021 · 1 comment
Closed

Notation synchronization #4866

martinthomson opened this issue Apr 27, 2021 · 1 comment
Labels
-invariants -transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@martinthomson
Copy link
Member

Invariants Section 4: We see that the meanings for the notation
definitions appear to be the same as those for the notation
definitions in [QUIC-TRANSPORT], but some of the wordings are
different. Please let us know if you would like the wordings to
match in both documents (and if yes, which document's wordings
should we use?).

Let's work this out. I don't think that it matters much which wins, but there might have been changes that only made it into one or other document, so we should probably take the one that was updated last.

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport -invariants labels Apr 27, 2021
@larseggert larseggert added this to Triage in Late Stage Processing via automation Apr 29, 2021
@larseggert larseggert moved this from Triage to Editorial Issues in Late Stage Processing May 3, 2021
@janaiyengar
Copy link
Contributor

This has been fixed.

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

No branches or pull requests

2 participants