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

Short abstract #92

Merged
merged 3 commits into from Feb 17, 2017
Merged

Short abstract #92

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5d8cd38
Shorten the abstract
martinthomson Dec 19, 2016
752537c
Small digestible chunks
martinthomson Dec 19, 2016
996f3aa
Take 2
martinthomson Feb 17, 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
39 changes: 17 additions & 22 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -95,19 +95,10 @@ informative:

--- abstract

QUIC is a multiplexed and secure transport protocol that runs on top of UDP.
QUIC builds on past transport experience, and implements mechanisms that make it
useful as a modern general-purpose transport protocol. Using UDP as the basis
of QUIC is intended to address compatibility issues with legacy clients and
middleboxes. QUIC authenticates all of its headers, preventing third parties
from changing them. QUIC encrypts most of its headers, thereby limiting
protocol evolution to QUIC endpoints only. Therefore, middleboxes, in large
part, are not required to be updated as new protocol versions are deployed.
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 recovery and
congestion control, and the use of TLS 1.3 for key negotiation.
This document defines the core of the QUIC transport protocol. This document
describes connection establishment, packet format, multiplexing and reliability.
Accompanying documents describe the cryptographic handshake and loss detection.


--- note_Note_to_Readers

Expand All @@ -124,19 +115,23 @@ code and issues list for this draft can be found at
# Introduction

QUIC is a multiplexed and secure transport protocol that runs on top of UDP.
QUIC builds on past transport experience and implements mechanisms that make it
useful as a modern general-purpose transport protocol. Using UDP as the
substrate, QUIC seeks to be compatible with legacy clients and middleboxes.
QUIC authenticates all of its headers, preventing middleboxes and other third
parties from changing them, and encrypts most of its headers, limiting protocol
evolution largely to QUIC endpoints only.
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. Accompanying documents describe QUIC's loss detection and
congestion control {{QUIC-RECOVERY}}, and the use of TLS 1.3 for key negotiation
{{QUIC-TLS}}.
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}}.


# Conventions and Definitions
Expand Down