A JSON Encoding for HTTP Header Field Values
draft-ietf-httpbis-jfv-01

The information below is for an old version of the document
Document Type Active Internet-Draft (httpbis WG)
Last updated 2016-07-08
Replaces draft-reschke-http-jfv
Replaced by draft-ietf-httpbis-header-structure
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HTTP Working Group                                            J. Reschke
Internet-Draft                                                greenbytes
Intended status: Standards Track                            July 8, 2016
Expires: January 9, 2017

              A JSON Encoding for HTTP Header Field Values
                       draft-ietf-httpbis-jfv-01

Abstract

   This document establishes a convention for use of JSON-encoded field
   values in HTTP header fields.

Editorial Note (To be removed by RFC Editor before publication)

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

   Working Group information can be found at <http://httpwg.github.io/>;
   source code and issues list for this draft can be found at
   <https://github.com/httpwg/http-extensions>.

   The changes in this draft are summarized in Appendix A.

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 January 9, 2017.

Copyright Notice

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

Reschke                  Expires January 9, 2017                [Page 1]
Internet-Draft     JSON Encoding for HTTP Field Values         July 2016

   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
   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
   2.  Data Model and Format  . . . . . . . . . . . . . . . . . . . .  3
   3.  Sender Requirements  . . . . . . . . . . . . . . . . . . . . .  4
   4.  Recipient Requirements . . . . . . . . . . . . . . . . . . . .  5
   5.  Using this Format in Header Field Definitions  . . . . . . . .  5
   6.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     6.1.  Content-Length . . . . . . . . . . . . . . . . . . . . . .  5
     6.2.  Content-Disposition  . . . . . . . . . . . . . . . . . . .  6
     6.3.  WWW-Authenticate . . . . . . . . . . . . . . . . . . . . .  7
     6.4.  Accept-Encoding  . . . . . . . . . . . . . . . . . . . . .  8
   7.  Discussion . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   8.  Deployment Considerations  . . . . . . . . . . . . . . . . . .  9
   9.  Internationalization Considerations  . . . . . . . . . . . . .  9
   10. Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 10
     11.2. Informative References . . . . . . . . . . . . . . . . . . 11
   Appendix A.  Change Log (to be removed by RFC Editor before
                publication)  . . . . . . . . . . . . . . . . . . . . 11
     A.1.  Since draft-reschke-http-jfv-00  . . . . . . . . . . . . . 11
     A.2.  Since draft-reschke-http-jfv-01  . . . . . . . . . . . . . 12
     A.3.  Since draft-reschke-http-jfv-02  . . . . . . . . . . . . . 12
     A.4.  Since draft-reschke-http-jfv-03  . . . . . . . . . . . . . 12
     A.5.  Since draft-reschke-http-jfv-04  . . . . . . . . . . . . . 12
     A.6.  Since draft-ietf-httpbis-jfv-00  . . . . . . . . . . . . . 12
   Appendix B.  Acknowledgements  . . . . . . . . . . . . . . . . . . 12

Reschke                  Expires January 9, 2017                [Page 2]
Internet-Draft     JSON Encoding for HTTP Field Values         July 2016

1.  Introduction

   Defining syntax for new HTTP header fields ([RFC7230], Section 3.2)
   is non-trivial.  Among the commonly encountered problems are:

   o  There is no common syntax for complex field values.  Several well-
      known header fields do use a similarly looking syntax, but it is
      hard to write generic parsing code that will both correctly handle
      valid field values but also reject invalid ones.
Show full document text