IETF Logo Mail Archive

[apps-discuss] JSON mailing list and BoF

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Mon, 18 February 2013 20:01 UTC

Return-Path: <jhildebr@cisco.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1830D21F8C86; Mon, 18 Feb 2013 12:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kRqDlBztQ3IG; Mon, 18 Feb 2013 12:01:22 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 21E9421F8C84; Mon, 18 Feb 2013 12:01:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1004; q=dns/txt; s=iport; t=1361217676; x=1362427276; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=+8QzgxuCG7XPxuwv+GslP8WOuKbsW+QVuHuqrS7jd54=; b=HLTIdDA+CoDtbi4NQwO1e3KCsWCrmmoPrDODeCFK5DBfluIYoQLNgJyu mhhluZxqMhoznv2ceKna9dJ6ESH1QCIoYAS6fZJFGVgY1VZVWbjQh4mRP FRCwa3PgdyKI7Y6rsrL9cLczj0miId/UacVxbd6AS4UVS2TqJdYe9CKdy k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFABOIIlGtJXG+/2dsb2JhbABEhgK6IIEEFnOCIQEEAQEBNy0EAx0BKhQ3CycEARIIiAoMwQ6PBoMXYQOXSY87gweCJw
X-IronPort-AV: E=Sophos;i="4.84,690,1355097600"; d="scan'208";a="178465579"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-3.cisco.com with ESMTP; 18 Feb 2013 20:01:08 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1IK17YM024703 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 18 Feb 2013 20:01:07 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Mon, 18 Feb 2013 14:01:07 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "json@ietf.org" <json@ietf.org>
Thread-Topic: JSON mailing list and BoF
Thread-Index: AQHODhKwsPxTte9Ry0KhDmvQvHsA3g==
Date: Mon, 18 Feb 2013 20:01:07 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70F8943CC@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.0.121105
x-originating-ip: [10.129.24.68]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <ACE7D09F0A447745BF133F5141F01248@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [apps-discuss] JSON mailing list and BoF
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2013 20:01:23 -0000

We're planning on doing a BoF in Orlando to discuss starting up a JSON
working group.  The BoF is currently planned for Monday afternoon at 1300
in Carribean 6.  A very preliminary version of a charter can be found here:

http://trac.tools.ietf.org/wg/appsawg/trac/wiki/JSON


But obviously we'll need to build consensus on what it should actually
contain.  Please discuss on the json@ietf.org mailing list:

https://www.ietf.org/mailman/listinfo/json


As a start, we know there are a couple of things we'd like to fix about
RFC 4627:

- move to standards track
- an ABNF indentation typo in section 2.2
- change SHOULD to MUST for the uniqueness of names in an object

A *very* important goal would be to minimize change, and to ensure strict
backward-compatibility.

There are likely adjunct JSON topics that would make sense to tackle once
we've got the experts together, but the goal would be to keep that list
short, focused, and general-purpose.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email