The I-JSON Message Format
draft-bray-i-json-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-07-11
Replaced by draft-ietf-json-i-json, rfc7493
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)
Internet Engineering Task Force                           T.B. Bray, Ed.
Internet-Draft                                              Google, Inc.
Intended status: Standards Track                           July 11, 2013
Expires: January 12, 2014

                       The I-JSON Message Format
                          draft-bray-i-json-00

Abstract

   I-JSON is a restricted profile of JSON designed to maximize
   interoperability and increase confidence that software can process it
   successfully with predictable results.

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 12, 2014.

Copyright Notice

   Copyright (c) 2013 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
   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

Bray                    Expires January 12, 2014                [Page 1]
Internet-Draft         The I-JSON Message Format               July 2013

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  I-JSON Messages . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Self-identification . . . . . . . . . . . . . . . . . . .   3
     2.2.  Encoding and Characters . . . . . . . . . . . . . . . . .   3
     2.3.  Numbers . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.4.  Object member names . . . . . . . . . . . . . . . . . . .   3
   3.  Software Behavior . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   RFC4627bis specifies a data format called JSON which has come to be
   widely used in Internet protocols.  For historical reasons, that RFC
   allows the use of language idioms and text encoding patterns which
   are likely to lead to interoperability problems and software
   breakage, particularly when a program receiving JSON data uses
   automated software to map it into native programming-language
   structures or database records.

   This document specifies I-JSON, short for "Internet JSON".  I-JSON
   Messages are also JSON texts per RFC4627bis, but with improved
   interoperability and lower risk of breakage in receiving software.

1.1.  Terminology

   The terms "object", "member", "array", "number", "name", and "string"
   in this document are to be interpreted as described in RFC4627bis.

1.2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  I-JSON Messages

   An I-JSON Message is a "JSON text" as defined by RFC4626bis and
   therefore MUST be either an object or an array.

   For maximum flexibility, an I-JSON Message SHOULD be an object.  This
   allows self-identification (see below) and also allows protocol

Bray                    Expires January 12, 2014                [Page 2]
Internet-Draft         The I-JSON Message Format               July 2013

   designers to add new data items to messages, should that become
   necessary, without breaking existing deployments.  In other words, it
   makes a Must-Ignore policy possible.

2.1.  Self-identification

   If an I-JSON Message is an object, it MAY self-identify by including
   a member whose name is "urn:ietf:i-json" and whose value is an
Show full document text