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

A day in the life #3225

Merged
merged 5 commits into from Dec 3, 2019
Merged
Changes from 1 commit
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
Expand Up @@ -1141,7 +1141,7 @@ protocol exchanges information.
Each connection starts with a handshake phase, during which client and server
Copy link
Contributor

Choose a reason for hiding this comment

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

unless of course your intended audience is primarily from East End

Copy link
Contributor

Choose a reason for hiding this comment

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

@MikeBishop Cockney an 'andshake

establish a shared secret using the cryptographic handshake protocol
{{QUIC-TLS}} and negotiate the application protocol. The handshake
({{handshake}}) confirms that endpoints are willing to communicate
({{handshake}}) confirms that both endpoints are willing to communicate
({{validate-handshake}}) and establishes parameters for the connection
({{transport-parameters}}).

Expand All @@ -1153,7 +1153,7 @@ attacks in 0-RTT; see {{QUIC-TLS}}. Separately, a server can also send
application data to a client before it receives the final cryptographic
handshake messages that allow it to confirm the identity and liveness of the
client. These capabilities allow an application protocol to offer the option to
trade some security guarantees for improved latency.
trade some security guarantees for reduced latency.

The use of connection IDs ({{connection-id}}) allows connections to migrate to a
new network path, both as a direct choice of an endpoint and when forced by a
Expand Down