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

Make intro more accessible #1789

Merged
merged 1 commit into from Sep 24, 2018
Merged

Make intro more accessible #1789

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 10 additions & 9 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -128,15 +128,16 @@ general-purpose secure transport for multiple applications.

* Connection migration and resilience to NAT rebinding

QUIC implements techniques learned from experience with TCP, SCTP and other
transport protocols. QUIC uses UDP as substrate so as to not require changes to
legacy client operating systems and middleboxes to be deployable. QUIC
authenticates all of its headers and encrypts most of the data it exchanges,
including its signaling. This allows the protocol to evolve without incurring a
dependency on upgrades to middleboxes. This document describes the core QUIC
protocol, including the conceptual design, wire format, and mechanisms of the
QUIC protocol for connection establishment, stream multiplexing, stream and
connection-level flow control, connection migration, and data reliability.
QUIC uses UDP as substrate so as to not require changes to legacy client
operating systems and middleboxes to be deployable. QUIC authenticates all of
Copy link
Contributor

@mikkelfj mikkelfj Sep 24, 2018 •
edited

Choose a reason for hiding this comment

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

that sentence is hard to parse

Copy link
Contributor

Choose a reason for hiding this comment

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

Agreed, this sentence is awkward.

How about "QUIC uses UDP as a substrate to avoid changes to legacy client operating systems and middleboxes in order to be deployed."

its headers and encrypts most of the data it exchanges, including its signaling.
This allows the protocol to evolve without incurring a dependency on upgrades to
middleboxes.

This document describes the core QUIC protocol, including the conceptual design,
wire format, and mechanisms of the QUIC protocol for connection establishment,
stream multiplexing, stream and connection-level flow control, connection
migration, and data reliability.

Accompanying documents describe QUIC's loss detection and congestion control
{{QUIC-RECOVERY}}, and the use of TLS 1.3 for key negotiation {{QUIC-TLS}}.
Expand Down