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

Encode cid #182

Merged
merged 3 commits into from
Oct 3, 2022
Merged
Changes from 2 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
14 changes: 7 additions & 7 deletions draft-ietf-quic-load-balancers.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,11 +64,11 @@ QUIC endpoints usually designate the connection ID which peers use to address
packets. Server-generated connection IDs create a potential need for out-of-band
communication to support QUIC.

QUIC allows servers (or load balancers) to designate an initial connection ID to
encode useful routing information for load balancers. It also encourages
servers, in packets protected by cryptography, to provide additional connection
IDs to the client. This allows clients that know they are going to change IP
address or port to use a separate connection ID on the new path, thus reducing
QUIC allows servers (or load balancers) to designate encode useful routing
martinthomson marked this conversation as resolved.
Show resolved Hide resolved
information for load balancers in connection IDs. It also encourages servers,
in packets protected by cryptography, to provide additional connection IDs to
the client. This allows clients that know they are going to change IP address
or port to use a separate connection ID on the new path, thus reducing
linkability as clients move through the world.

There is a tension between the requirements to provide routing information and
Expand Down Expand Up @@ -343,7 +343,7 @@ addresses. The corresponding server configurations contain one or
more unique server IDs.

The configuration agent chooses a server ID length for each configuration that
MUST be at least one octet.
MUST be at least one octet.

A QUIC-LB configuration MAY significantly over-provision the server ID space
(i.e., provide far more codepoints than there are servers) to increase the
Expand Down Expand Up @@ -432,7 +432,7 @@ the second through seventeenth most significant bytes of the connection ID.
### General Case: Four-Pass Encryption

Any other field length requires four passes for encryption and at least three
for decryption. To understand this algorithm, it is useful to define four
for decryption. To understand this algorithm, it is useful to define four
functions that minimize the amount of bit-shifting necessary in the event that
there are an odd number of octets.

Expand Down