Structured Headers for HTTP
draft-ietf-httpbis-header-structure-07

Document Type Active Internet-Draft (httpbis WG)
Last updated 2018-07-02
Replaces draft-kamp-httpbis-structure, draft-ietf-httpbis-jfv, draft-nottingham-structured-headers
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd Patrick McManus
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Patrick McManus <mcmanus@ducksong.com>
HTTP                                                       M. Nottingham
Internet-Draft                                                    Fastly
Intended status: Standards Track                               P-H. Kamp
Expires: January 3, 2019                       The Varnish Cache Project
                                                            July 2, 2018

                      Structured Headers for HTTP
                 draft-ietf-httpbis-header-structure-07

Abstract

   This document describes a set of data types and algorithms associated
   with them that are intended to make it easier and safer to define and
   handle HTTP header fields.  It is intended for use by new
   specifications of HTTP header fields as well as revisions of existing
   header field specifications when doing so does not cause
   interoperability issues.

Note to Readers

   _RFC EDITOR: please remove this section before publication_

   Discussion of this draft takes place on the HTTP working group
   mailing list (ietf-http-wg@w3.org), which is archived at
   https://lists.w3.org/Archives/Public/ietf-http-wg/ [1].

   Working Group information can be found at https://httpwg.github.io/
   [2]; source code and issues list for this draft can be found at
   https://github.com/httpwg/http-extensions/labels/header-structure
   [3].

   Tests for implementations are collected at https://github.com/httpwg/
   structured-header-tests [4].

   Implementations are tracked at https://github.com/httpwg/wiki/wiki/
   Structured-Headers [5].

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/.

Nottingham & Kamp        Expires January 3, 2019                [Page 1]
Internet-Draft         Structured Headers for HTTP             July 2018

   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 January 3, 2019.

Copyright Notice

   Copyright (c) 2018 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  . . . . . . . . . . . . . . . . .   4
   2.  Defining New Structured Headers . . . . . . . . . . . . . . .   4
   3.  Structured Header Data Types  . . . . . . . . . . . . . . . .   6
     3.1.  Dictionaries  . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Lists . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Parameterised Lists . . . . . . . . . . . . . . . . . . .   7
     3.4.  Items . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Integers  . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.6.  Floats  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.7.  Strings . . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.8.  Identifiers . . . . . . . . . . . . . . . . . . . . . . .   9
     3.9.  Binary Content  . . . . . . . . . . . . . . . . . . . . .   9
   4.  Structured Headers in HTTP/1  . . . . . . . . . . . . . . . .  10
     4.1.  Serialising Structured Headers into HTTP/1  . . . . . . .  10
     4.2.  Parsing HTTP/1 Header Fields into Structured Headers  . .  14
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  22
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  22
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  22
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  23
     7.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  24
   Appendix A.  Frequently Asked Questions . . . . . . . . . . . . .  24
     A.1.  Why not JSON? . . . . . . . . . . . . . . . . . . . . . .  24

Nottingham & Kamp        Expires January 3, 2019                [Page 2]
Internet-Draft         Structured Headers for HTTP             July 2018
Show full document text