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

Comment about notational conventions #1500

Merged
merged 1 commit into from
Jul 6, 2018
Merged

Conversation

martinthomson
Copy link
Member

Someone commented that we don't really explain what (i) means in diagrams, for instance.

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -invariants labels Jun 29, 2018
@@ -106,6 +106,8 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
document are to be interpreted as described in BCP 14 {{!RFC2119}} {{!RFC8174}}
when, and only when, they appear in all capitals, as shown here.

This document uses terms and notational conventions from {{QUIC-TRANSPORT}}.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't it be the other way around? Given that invariants are less likely to change.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We decided that the transport doc should be standalone (that is, it does not depend on invariants normatively). v1 of the transport might eventually be obsolete, but the terminology will still be there.

@martinthomson martinthomson merged commit f0217bc into master Jul 6, 2018
@martinthomson martinthomson deleted the invariants-convenstions branch July 6, 2018 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-invariants editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants