Corrected: WG Action: Formed JavaScript Object Notation (json)

IESG Secretary <> Fri, 31 May 2013 16:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B9A7A21F87CD; Fri, 31 May 2013 09:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tDDOde+08yxX; Fri, 31 May 2013 09:33:01 -0700 (PDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 8035021F85E0; Fri, 31 May 2013 09:33:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <>
To: IETF Announcement List <>
Subject: Corrected: WG Action: Formed JavaScript Object Notation (json)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <>
Date: Fri, 31 May 2013 09:33:01 -0700
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 31 May 2013 16:33:08 -0000

A new IETF working group has been formed in the Applications Area. For
additional information please contact the Area Directors or the WG

JavaScript Object Notation (json)
Current Status: Proposed WG

  Matthew Miller <>
  Paul Hoffman <>

Assigned Area Director:
  Pete Resnick <>

Mailing list
  To Subscribe:


Javascript Object Notation (JSON) is a lightweight, text-based,
language-independent data interchange format.  It was derived from the
ECMAScript Programming Language Standard and was published in RFC 4627,
an Informational document.  JSON has come into very broad use, often
instead of or in addition to XML.

RFC 4627 cites a 1999 version of the ECMAScript Language Specification.
However, since the publication of RFC 4627, the ECMA specifications have
turned the relationship around, and themselves cite RFC 4627 as the
documentation for JSON.  A number of Standards Track IETF specifications
have also cited RFC 4627, and more are in development (for example, the
work in the JOSE working group).

It makes sense to move RFC 4627 onto the Standards Track.  There are
also a number of other JSON-related proposals for Standards Track that
would benefit from review from both the IETF and the larger JSON-using
communities created by a working group focused on JSON.

The JSON working group will have as its only initial task the minor
revision of RFC 4627 to bring it onto the Standards Track.  As noted
above, RFC 4627 is a mature and widely cited specification.  The work is
essentially a reclassification in place, with minimal changes.  The
working group will review errata and update the document as needed to
incorporate those, and will correct significant errors and
inconsistencies, but will keep changes to a minimum.

It is acknowledged that there are differences between RFC 4627 and the
ECMAScript specification in the rules for parsing JSON. Any changes that
break compatibility with existing implementations of either RFC 4627 or
the ECMAScript specification will need to have very strong justification
and broad support. All differences between RFC 4627 or the current
ECMAScript specification will be documented in the new RFC. This
documentation will include both the WG consensus for the rationale of
the changes and the expected impact of the changes.

The resulting document will be jointly published as an RFC and by ECMA.
ECMA participants will be participating in the working group editing
through the normal process of working group participation.  The
responsible AD will coordinate the approval process with ECMA so that
the versions of the document that are approved by each body are the

There are also various proposals for JSON extensions and related
standards. The working group will consider those proposals only after
the initial work is done, and must recharter with specific work items
for any additional work it might select.

  Jan 2014 - Request publication of JSON specification