Binary Structured HTTP Headers
draft-nottingham-binary-structured-headers-00

Document Type Active Internet-Draft (individual)
Last updated 2019-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
Network Working Group                                      M. Nottingham
Internet-Draft                                                    Fastly
Intended status: Standards Track                        November 1, 2019
Expires: May 4, 2020

                     Binary Structured HTTP Headers
             draft-nottingham-binary-structured-headers-00

Abstract

   This specification defines a binary serialisation of Structured
   Headers for HTTP, along with a negotiation mechanism for its use in
   HTTP/2.  It also defines how to use Structured Headers for many
   existing headers - thereby "backporting" them - when supported by two
   peers.

Note to Readers

   _RFC EDITOR: please remove this section before publication_

   The issues list for this draft can be found at
   https://github.com/mnot/I-D/labels/binary-structured-headers [1].

   The most recent (often, unpublished) draft is at
   https://mnot.github.io/I-D/binary-structured-headers/ [2].

   Recent changes are listed at https://github.com/mnot/I-D/commits/gh-
   pages/binary-structured-headers [3].

   See also the draft's current status in the IETF datatracker, at
   https://datatracker.ietf.org/doc/draft-nottingham-binary-structured-
   headers/ [4].

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 https://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."

Nottingham                 Expires May 4, 2020                  [Page 1]
Internet-Draft       Binary Structured HTTP Headers        November 2019

   This Internet-Draft will expire on May 4, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  Binary Structured Headers . . . . . . . . . . . . . . . . . .   3
     2.1.  The Binary Literal Representation . . . . . . . . . . . .   4
       2.1.1.  Lists . . . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.2.  Dictionaries  . . . . . . . . . . . . . . . . . . . .   4
       2.1.3.  Items . . . . . . . . . . . . . . . . . . . . . . . .   5
       2.1.4.  String Literals . . . . . . . . . . . . . . . . . . .   5
     2.2.  Binary Structured Types . . . . . . . . . . . . . . . . .   5
       2.2.1.  Inner Lists . . . . . . . . . . . . . . . . . . . . .   6
       2.2.2.  Parameters  . . . . . . . . . . . . . . . . . . . . .   6
       2.2.3.  Item Payload Types  . . . . . . . . . . . . . . . . .   7
   3.  Using Binary Structured Headers in HTTP/2 . . . . . . . . . .  10
     3.1.  Binary Structured Headers Setting . . . . . . . . . . . .  11
     3.2.  The BINHEADERS Frame  . . . . . . . . . . . . . . . . . .  11
   4.  Using Binary Structured Headers with Existing Fields  . . . .  12
     4.1.  Directly Represented Fields . . . . . . . . . . . . . . .  12
     4.2.  Aliased Fields  . . . . . . . . . . . . . . . . . . . . .  14
       4.2.1.  URLs  . . . . . . . . . . . . . . . . . . . . . . . .  15
       4.2.2.  Dates . . . . . . . . . . . . . . . . . . . . . . . .  15
       4.2.3.  ETags . . . . . . . . . . . . . . . . . . . . . . . .  16
       4.2.4.  Links . . . . . . . . . . . . . . . . . . . . . . . .  16
       4.2.5.  Cookies . . . . . . . . . . . . . . . . . . . . . . .  17
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  17
     7.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  19

Nottingham                 Expires May 4, 2020                  [Page 2]
Show full document text