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

Rephrase sentence in Intro #716

Merged
merged 1 commit into from
Aug 10, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 8 additions & 9 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,15 +105,14 @@ QUIC aims to provide a flexible set of features that allow it to be a
general-purpose transport for multiple applications.

QUIC implements techniques learned from experience with TCP, SCTP and other
transport protocols. Using UDP as the substrate, QUIC seeks to be compatible
with legacy clients and middleboxes. 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, and data
reliability.
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, 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