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

Specify connection ID and version a unsigned numbers #788

Merged
merged 2 commits into from Sep 21, 2017
Merged

Specify connection ID and version a unsigned numbers #788

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c0c5e83
Specify connection ID and version a unsigned numbers
RyanTheOptimist Sep 21, 2017
0645271
more
RyanTheOptimist Sep 21, 2017
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
23 changes: 12 additions & 11 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -149,7 +149,7 @@ Connection:

Connection ID:

: The identifier for a QUIC connection.
: The 64-bit unsigned number used as an identifier for a QUIC connection.

QUIC packet:

Expand Down Expand Up @@ -275,15 +275,16 @@ processing.

## Connection Migration and Resilience to NAT Rebinding

QUIC connections are identified by a 64-bit Connection ID, randomly generated by
the server. QUIC's consistent connection ID allows connections to survive
changes to the client's IP and port, such as those caused by NAT rebindings or
by the client changing network connectivity to a new address. QUIC provides
automatic cryptographic verification of a rebound client, since the client
continues to use the same session key for encrypting and decrypting packets.
The consistent connection ID can be used to allow migration of the connection to
a new server IP address as well, since the Connection ID remains consistent
across changes in the client's and the server's network addresses.
QUIC connections are identified by a Connection ID, a 64-bit unsigned number
randomly generated by the server. QUIC's consistent connection ID allows
connections to survive changes to the client's IP and port, such as those
caused by NAT rebindings or by the client changing network connectivity to a
new address. QUIC provides automatic cryptographic verification of a rebound
lient, since the client continues to use the same session key for encrypting
and decrypting packets. The consistent connection ID can be used to allow
migration of the connection to a new server IP address as well, since the
Connection ID remains consistent across changes in the client's and the
server's network addresses.


## Version Negotiation {#benefit-version-negotiation}
Expand All @@ -295,7 +296,7 @@ deployed and used concurrently. Version negotiation is described in

# Versions {#versions}

QUIC versions are identified using a 32-bit value.
QUIC versions are identified using a 32-bit unsigned number.

The version 0x00000000 is reserved to represent an invalid version. This
version of the specification is identified by the number 0x00000001.
Expand Down