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

Gorrys invariant nits #3730

Merged
merged 7 commits into from Jun 9, 2020
Merged

Gorrys invariant nits #3730

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
07a04fc
Expand SCID/DCID
martinthomson Jun 4, 2020
48cacc0
Add big endian to notation section
martinthomson Jun 4, 2020
bff4255
not specified -> not encoded for DCID length
martinthomson Jun 4, 2020
52a8b56
Make references to concepts clearer
martinthomson Jun 4, 2020
b07bf37
Use transport endpoint
martinthomson Jun 5, 2020
caaf168
Remove the bit about rules and just list the assumption
martinthomson Jun 5, 2020
8726e70
Going with QUIC endpoint
martinthomson Jun 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-quic-invariants.md
View file
Open in desktop
Expand Up @@ -240,7 +240,7 @@ A connection ID is an opaque field of arbitrary length.

The primary function of a connection ID is to ensure that changes in addressing
at lower protocol layers (UDP, IP, and below) don't cause packets for a QUIC
connection to be delivered to the wrong transport endpoint. The connection ID
connection to be delivered to the wrong QUIC endpoint. The connection ID
is used by endpoints and the intermediaries that support them to ensure that
each QUIC 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
Expand Down