QUIC: A UDP-Based Secure and Reliable Transport for HTTP/2
draft-hamilton-early-deployment-quic-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ryan Hamilton , Jana Iyengar , Ian Swett , Alyssa Wilk | ||
Last updated | 2017-01-09 (Latest revision 2016-07-08) | ||
Replaces | draft-tsvwg-quic-protocol | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
QUIC (Quick UDP Internet Connection) is a new multiplexed and secure transport atop UDP, designed from the ground up and optimized for HTTP/2 semantics. While built with HTTP/2 as the primary application protocol, QUIC builds on decades of transport and security experience, and implements mechanisms that make it attractive as a modern general-purpose transport. QUIC provides multiplexing and flow control equivalent to HTTP/2, security equivalent to TLS, and connection semantics, reliability, and congestion control equivalent to TCP. This draft documents the early deployment of the QUIC protocol prior to standardization.
Authors
Ryan Hamilton
Jana Iyengar
Ian Swett
Alyssa Wilk
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)