The I-JSON Message Format
draft-ietf-json-i-json-05
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Active Internet-Draft (json WG) | |
| Author | Tim Bray | ||
| Last updated | 2015-01-22 (latest revision 2014-12-18) | ||
| Replaces | draft-bray-i-json | ||
| Stream | Internent Engineering Task Force (IETF) | ||
| Formats | pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Matthew Miller | ||
| Shepherd write-up | Show (last changed 2014-09-16) | ||
| IESG | IESG state | IESG Evaluation::Revised I-D Needed | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Needs 8 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Pete Resnick | ||
| Send notices to | linuxwolf@outer-planes.net, draft-ietf-json-i-json.all@tools.ietf.org, json-chairs@tools.ietf.org, json@ietf.org | ||
| IANA | IANA review state | IANA OK - No Actions Needed | |
Network Working Group T. Bray, Ed.
Internet-Draft Textuality Services
Intended status: Standards Track December 18, 2014
Expires: June 21, 2015
The I-JSON Message Format
draft-ietf-json-i-json-05
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 June 21, 2015.
Copyright Notice
Copyright (c) 2014 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.
Bray Expires June 21, 2015 [Page 1]
Internet-Draft The I-JSON Message Format December 2014
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. I-JSON Messages . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Encoding and Characters . . . . . . . . . . . . . . . . . 3
2.2. Numbers . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Object constraints . . . . . . . . . . . . . . . . . . . 3
3. Software Behavior . . . . . . . . . . . . . . . . . . . . . . 4
4. Protocol-design Recommendations . . . . . . . . . . . . . . . 4
4.1. Top-level Constructs . . . . . . . . . . . . . . . . . . 4
4.2. Must-ignore Policy . . . . . . . . . . . . . . . . . . . 4
4.3. Time and Date Handling . . . . . . . . . . . . . . . . . 5
4.4. Binary Data . . . . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
RFC 7159 describes the JSON data interchange format, which is widely
used in Internet protocols. For historical reasons, that
specification 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. RFC 7159 describes practices which
may be used to avoid these interoperability problems.
This document specifies I-JSON, short for "Internet JSON". The unit
of definition is the "I-JSON message". I-JSON messages are also
"JSON texts" as defined in RFC 7159 but with certain extra
constraints which enforce the good interoperability practices
described in that specification.
1.1. Terminology
The terms "object", "member", "array", "number", "name", and "string"
in this document are to be interpreted as described in RFC 7159
[RFC7159].
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].
Bray Expires June 21, 2015 [Page 2]
Internet-Draft The I-JSON Message Format December 2014
2. I-JSON Messages
An I-JSON message is a JSON text, as defined by RFC 7159.
2.1. Encoding and Characters
I-JSON messages MUST be encoded using UTF-8 [RFC3629].
Object member names, and string values in arrays and object members,
Show full document text