HTTP over QUIC - Mapping and Header Compression
draft-bishop-quic-http-and-qpack-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-11-15
Replaced by draft-ietf-quic-qpack
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
QUIC Working Group                                             M. Bishop
Internet-Draft                                                 Microsoft
Intended status: Standards Track                       November 15, 2016
Expires: May 19, 2017

            HTTP over QUIC - Mapping and Header Compression
                  draft-bishop-quic-http-and-qpack-00

Abstract

   HTTP/2 [RFC7540] uses HPACK [RFC7541] for header compression.
   However, HPACK relies on the in-order message-based semantics of the
   HTTP/2 framing layer in order to function.  Messages can only be
   successfully decoded if processed by the receiver in the same order
   as generated by the sender.  This draft refines HPACK to loosen the
   ordering requirements for use over QUIC
   [I-D.hamilton-quic-transport-protocol] and describes changes to
   [I-D.shade-quic-http2-mapping] to leverage the new compression.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 19, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Bishop                    Expires May 19, 2017                  [Page 1]
Internet-Draft                    QPACK                    November 2016

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  QPACK . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Changes to Static and Dynamic Tables  . . . . . . . . . .   3
       2.1.1.  Dynamic table state synchronization . . . . . . . . .   4
     2.2.  Changes to Binary Format  . . . . . . . . . . . . . . . .   5
       2.2.1.  Literal Header Field Representation . . . . . . . . .   5
       2.2.2.  Deletion  . . . . . . . . . . . . . . . . . . . . . .   6
       2.2.3.  The QPACK-ACK frame . . . . . . . . . . . . . . . . .   7
   3.  HTTP over QUIC Mapping  . . . . . . . . . . . . . . . . . . .   7
     3.1.  Stream usage  . . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  On-Stream Framing Definition  . . . . . . . . . . . . . .   8
       3.2.1.  DATA  . . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.2.  HEADERS . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.3.  PUSH_PROMISE  . . . . . . . . . . . . . . . . . . . .  10
       3.2.4.  PRIORITY  . . . . . . . . . . . . . . . . . . . . . .  10
       3.2.5.  SETTINGS  . . . . . . . . . . . . . . . . . . . . . .  11
       3.2.6.  Other frames not mentioned  . . . . . . . . . . . . .  11
     3.3.  HTTP Message Exchanges  . . . . . . . . . . . . . . . . .  11
   4.  Performance Considerations  . . . . . . . . . . . . . . . . .  13
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   HPACK has a number of features that were intended to provide
   performance advantages to HTTP/2, but which don't live well in an
   out-of-order environment such as that provided by QUIC.

   The largest challenge is the fact that elements are referenced by a
   very fluid index.  Not only is the index implicit when an item is
   added to the header table, the index will change without notice as
   other items are added to the header table.  Static entries occupy the
   first 61 values, followed by dynamic entries.  A newly-added dynamic
Show full document text