Skip to main content

HTTP/2 Semantics Using The QUIC Transport Protocol

Document Type Replaced Internet-Draft (candidate for quic WG)
Expired & archived
Authors Robbie Shade , Mike Warres
Last updated 2016-11-23 (Latest revision 2016-07-08)
Replaced by draft-ietf-quic-http
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-quic-http
Consensus boilerplate Unknown
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:


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.


Robbie Shade
Mike Warres

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)