[Json] WG Action: Formed Javascript Object Notation Update (jsonbis)

The IESG <iesg-secretary@ietf.org> Fri, 26 June 2015 16:42 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id DF7AD1A8912; Fri, 26 Jun 2015 09:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 4YvnFowMQQjl; Fri, 26 Jun 2015 09:42:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D6F251A8915; Fri, 26 Jun 2015 09:42:29 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150626164229.18696.20518.idtracker@ietfa.amsl.com>
Date: Fri, 26 Jun 2015 09:42:29 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/dnQlXyQ_5W3_sGI21w4AK82Tw6E>
Cc: jsonbis WG <json@ietf.org>
Subject: [Json] WG Action: Formed Javascript Object Notation Update (jsonbis)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2015 16:42:32 -0000

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

Javascript Object Notation Update (jsonbis)
Current Status: Proposed WG

  Matthew Miller <mamille2@cisco.com>

Assigned Area Director:
  Barry Leiba <barryleiba@computer.org>

Mailing list
  Address: json@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/json
  Archive: https://mailarchive.ietf.org/arch/browse/json/


Javascript Object Notation (JSON) is a lightweight, text-based,
language-independent data interchange format. It was derived from the
ECMAScript Programming Language Standard, and is published in both
ECMA-404 and RFC 7159. First published over 10 years ago, JSON has come
into nearly ubiquitous use, often the first choice for data interchange
over other forms -- especially for applications that work over the World
Wide Web.  Given this ubiquity it makes sense to move JSON to Internet

JSON is defined in two separate documents from two different bodies.
ECMA-404, published by Ecma International, focuses on the abstract 
syntax. RFC 7159, published by the IETF, focuses on the interoperability 
concerns when exchanging JSON over a network. The two documents agree on 
the structure of what JSON is.

The JSON working group will have as its only task the minor
revision of RFC 7159 to bring it to Internet Standard, and fully
acknowledge the syntax definition in ECMA-404. The work is essentially
a reclassification in place, with absolute minimal changes, though those
changes will require publication of a new RFC.  The working group will
review errata and update the document as needed to incorporate those.

The resulting RFC will be aligned with a corresponding publication by 
ECMA. The Working Group will work with the liaison managers to 
coordinate with Ecma International TC39 on the editing of both 
documents. The responsible AD will work with the liaison managers to 
coordinate the approval process with Ecma International so that the 
versions of the document that are approved by each body are properly 
aligned with regard to syntax and shared semantics.

  Oct 2015 - Request publication of JSON standard