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

Gorrys invariant nits #3730

Merged
merged 7 commits into from
Jun 9, 2020
Merged

Gorrys invariant nits #3730

merged 7 commits into from
Jun 9, 2020

Conversation

gorryfair
Copy link
Contributor

Editorial NiTs when reviewing the invariant text. These NiTs address readability issues, and do not intend to change the meaning of the text.

@larseggert
Copy link
Member

Is there an associated issue?

@gorryfair gorryfair mentioned this pull request Jun 5, 2020
@larseggert larseggert linked an issue Jun 5, 2020 that may be closed by this pull request
@ianswett ianswett added -invariants editorial An issue that does not affect the design of the protocol; does not require consensus. labels Jun 9, 2020
Copy link
Contributor

@ianswett ianswett left a comment

Choose a reason for hiding this comment

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

Thanks for changing SCID/DCID to "Source Connection ID" and "Destination Connection ID", that seems like a good change.

packet can be delivered to the correct instance of an endpoint. At the
endpoint, the connection ID is used to identify which QUIC connection the packet
is intended for.
connection to be delivered to the wrong transport endpoint. The connection ID
Copy link
Contributor

Choose a reason for hiding this comment

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

What's a transport endpoint? I don't recall us using that term elsewhere, so endpoint seems sufficient to me. Or maybe we need another term for this case?

Copy link
Member

Choose a reason for hiding this comment

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

This was really trying to avoid having to pull in the definition of "endpoint" from the transport doc. I see that I failed there. Happy to take suggestions, like:

Suggested change
connection to be delivered to the wrong transport endpoint. The connection ID
connection to be delivered to the wrong destination. The connection ID

Copy link
Contributor Author

Choose a reason for hiding this comment

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

"destination" sounds like it could be network-layer?

The document uses "QUIC endpoint" elsewhere to refer to an endpoint at the transport layer, so that may perhaps be the term we are looking for?

@janaiyengar janaiyengar merged commit 4f0be56 into master Jun 9, 2020
@janaiyengar janaiyengar deleted the gorrys-invariant-nits branch June 9, 2020 22:28
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.

Gorrys invariant nits
5 participants