IETF Logo Mail Archive

Re: [Json] [apps-discuss] JSON mailing list and BoF

"Matt Miller (mamille2)" <mamille2@cisco.com> Tue, 19 February 2013 20:33 UTC

Return-Path: <mamille2@cisco.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E718A21F8658; Tue, 19 Feb 2013 12:33:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.528
X-Spam-Level:
X-Spam-Status: No, score=-10.528 tagged_above=-999 required=5 tests=[AWL=0.071, 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 0QdebbXIlXkL; Tue, 19 Feb 2013 12:33:17 -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 E8C1621F84E9; Tue, 19 Feb 2013 12:33:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1788; q=dns/txt; s=iport; t=1361305991; x=1362515591; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Drd6s5ZvuG2mgNKfIq+jcA+UtF3Ak3ObPUOmLYvOkx0=; b=ZHqOFsC4hw26j0oog65VRrkNjEy5PvCbQgOHeULcTWK9O2d+Ww+qxgd7 3++/y7nfxdgEpq//YGw0WtKSBzoJrLasa7KoM50oHCF4OdvTcaYcOQlMq 4Ne3uuxghZyiq4fYlThs6eCi2EP0f8unMiRcA6rdf1x74wv746vNeKHjT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAJ/gI1GtJXHB/2dsb2JhbABFwDuBDRZzgh8BAQEDAQEBATctBAMLBQsCAQgiFBAnCyUCBA4FCAGIAwYMsDOQJ41NgQ4CMQIFgl9hA5dIjzuDB4FyNQ
X-IronPort-AV: E=Sophos;i="4.84,697,1355097600"; d="scan'208";a="178900590"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-3.cisco.com with ESMTP; 19 Feb 2013 20:33:10 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1JKXAGM011800 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 20:33:10 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.203]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 14:33:10 -0600
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Thread-Topic: [apps-discuss] JSON mailing list and BoF
Thread-Index: AQHODhKwsPxTte9Ry0KhDmvQvHsA3piCCRiA
Date: Tue, 19 Feb 2013 20:33:09 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411513E818@xmb-aln-x11.cisco.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70F8943CC@xmb-rcd-x10.cisco.com>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F8943CC@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.129.24.55]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2350A2168A8B494C9EAD3849DB8EB7D6@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 19 Feb 2013 20:33:19 -0000

Another topic that might worth discussing is canonicalization.  It's come up in JOSE a couple of times[1], and it would be helpful to standardize an approach.

- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

[1] The most recent discussing starts at < http://www.ietf.org/mail-archive/web/jose/current/msg01575.html >, instigated by < http://www.ietf.org/mail-archive/web/jose/current/msg01553.html >

On Feb 18, 2013, at 1:01 PM, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote:

> 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
> 
> 
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

v2.23.0 | Report a Bug | By Email