HTTP/2 Semantics Using The QUIC Transport Protocol
draft-shade-quic-http2-mapping-00
| Document | Type | Replaced Internet-Draft (candidate for quic WG) | |
|---|---|---|---|
| Last updated | 2016-11-23 (latest revision 2016-07-08) | ||
| Replaced by | draft-ietf-quic-http | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-quic-http | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-shade-quic-http2-mapping-00.txt
Abstract
The QUIC transport protocol has several features that are desirable in a transport for HTTP/2, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP/2 semantics over QUIC. Specifically, this document identifies HTTP/2 features that are subsumed by QUIC, and describes how the other features can be implemented atop QUIC.
Authors
Robbie Shade
(rjshade@google.com)
Mike Warres
(mpw@google.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)