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

Minor clarification. Fixes #2084 #2929

Merged
merged 2 commits into from Aug 26, 2019
Merged
Changes from all commits
Commits
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
7 changes: 4 additions & 3 deletions draft-ietf-quic-transport.md
Expand Up @@ -903,9 +903,10 @@ deployment-specific) method which will allow packets with that connection ID to
be routed back to the endpoint and identified by the endpoint upon receipt.

Connection IDs MUST NOT contain any information that can be used by an external
observer to correlate them with other connection IDs for the same connection.
As a trivial example, this means the same connection ID MUST NOT be issued more
than once on the same connection.
observer (that is, one that does not cooperate with the issuer) to correlate
them with other connection IDs for the same connection. As a trivial example,
this means the same connection ID MUST NOT be issued more than once on the same
connection.

Packets with long headers include Source Connection ID and Destination
Connection ID fields. These fields are used to set the connection IDs for new
Expand Down