A JSON Encoding for HTTP Header Field Values
draft-reschke-http-jfv-10

Document Type Active Internet-Draft (individual)
Last updated 2019-10-14
Stream (None)
Intended RFC status (None)
Formats plain text html 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                                      J. F. Reschke
Internet-Draft                                                greenbytes
Intended status: Informational                           14 October 2019
Expires: 16 April 2020

              A JSON Encoding for HTTP Header Field Values
                       draft-reschke-http-jfv-10

Abstract

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

Editorial Note

   This note is to be removed before publishing as an RFC.

   Distribution of this document is unlimited.  Although this is not a
   work item of the HTTPbis Working Group, comments should be sent to
   the Hypertext Transfer Protocol (HTTP) mailing list at ietf-http-
   wg@w3.org (mailto:ietf-http-wg@w3.org), which may be joined by
   sending a message with subject "subscribe" to ietf-http-wg-
   request@w3.org (mailto:ietf-http-wg-
   request@w3.org?subject=subscribe).

   Discussions of the HTTPbis Working Group are archived at
   http://lists.w3.org/Archives/Public/ietf-http-wg/.

   XML versions and latest edits for this document are available from
   http://greenbytes.de/tech/webdav/#draft-reschke-http-jfv.

   The changes in this draft are summarized in Appendix E.13.

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

Reschke                   Expires 16 April 2020                 [Page 1]
Internet-Draft     JSON Encoding for HTTP Field Values      October 2019

   This Internet-Draft will expire on 16 April 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
   2.  Data Model and Format . . . . . . . . . . . . . . . . . . . .   4
   3.  Sender Requirements . . . . . . . . . . . . . . . . . . . . .   5
   4.  Recipient Requirements  . . . . . . . . . . . . . . . . . . .   5
   5.  Using this Format in Header Field Definitions . . . . . . . .   5
   6.  Deployment Considerations . . . . . . . . . . . . . . . . . .   6
   7.  Interoperability Considerations . . . . . . . . . . . . . . .   6
     7.1.  Encoding and Characters . . . . . . . . . . . . . . . . .   6
     7.2.  Numbers . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.3.  Object Constraints  . . . . . . . . . . . . . . . . . . .   6
   8.  Internationalization Considerations . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Appendix A.  Examples . . . . . . . . . . . . . . . . . . . . . .   9
     A.1.  Content-Length  . . . . . . . . . . . . . . . . . . . . .   9
     A.2.  Content-Disposition . . . . . . . . . . . . . . . . . . .  10
     A.3.  WWW-Authenticate  . . . . . . . . . . . . . . . . . . . .  11
     A.4.  Accept-Encoding . . . . . . . . . . . . . . . . . . . . .  12
   Appendix B.  Use of JSON Field Value Encoding in the
           Wild  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     B.1.  W3C Reporting API Specification . . . . . . . . . . . . .  13
     B.2.  W3C Clear Site Data Specification . . . . . . . . . . . .  13
     B.3.  W3C Feature Policy Specification  . . . . . . . . . . . .  13
   Appendix C.  Relation to HTTP 'Key' Header Field  . . . . . . . .  14
   Appendix D.  Discussion . . . . . . . . . . . . . . . . . . . . .  14
   Appendix E.  Change Log . . . . . . . . . . . . . . . . . . . . .  14
     E.1.  Since draft-reschke-http-jfv-00 . . . . . . . . . . . . .  14
     E.2.  Since draft-reschke-http-jfv-01 . . . . . . . . . . . . .  14
Show full document text