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

Mike Jones <Michael.Jones@microsoft.com> Tue, 19 February 2013 20:47 UTC

Return-Path: <Michael.Jones@microsoft.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 5871D21F8806; Tue, 19 Feb 2013 12:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level:
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599]
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 hmiLsFIsQ5iy; Tue, 19 Feb 2013 12:47:34 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (na01-by2-obe.ptr.protection.outlook.com [207.46.100.26]) by ietfa.amsl.com (Postfix) with ESMTP id 860E421F87E1; Tue, 19 Feb 2013 12:47:34 -0800 (PST)
Received: from BL2FFO11FD015.protection.gbl (10.173.161.202) by BL2FFO11HUB029.protection.gbl (10.173.161.53) with Microsoft SMTP Server (TLS) id 15.0.620.12; Tue, 19 Feb 2013 20:47:32 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD015.mail.protection.outlook.com (10.173.160.223) with Microsoft SMTP Server (TLS) id 15.0.620.12 via Frontend Transport; Tue, 19 Feb 2013 20:47:31 +0000
Received: from TK5EX14MBXC284.redmond.corp.microsoft.com ([169.254.1.96]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.02.0318.003; Tue, 19 Feb 2013 20:47:03 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Thread-Topic: [apps-discuss] JSON mailing list and BoF
Thread-Index: AQHODhKwsPxTte9Ry0KhDmvQvHsA3piCCRiA//+eqLA=
Date: Tue, 19 Feb 2013 20:47:02 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367477490@TK5EX14MBXC284.redmond.corp.microsoft.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70F8943CC@xmb-rcd-x10.cisco.com> <BF7E36B9C495A6468E8EC573603ED9411513E818@xmb-aln-x11.cisco.com>
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411513E818@xmb-aln-x11.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.74]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454001)(51704002)(13464002)(189002)(199002)(24454001)(65816001)(79102001)(53806001)(80022001)(16406001)(54316002)(56776001)(46406002)(76482001)(51856001)(50986001)(46102001)(55846006)(56816002)(4396001)(47736001)(47976001)(50466001)(49866001)(31966008)(74662001)(63696002)(54356001)(5343655001)(47446002)(15202345001)(5343635001)(66066001)(74502001)(77982001)(23726001)(44976002)(59766001)(20776003)(33656001)(47776003); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB029; H:TK5EX14HUBC102.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0762FFD075
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [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: Tue, 19 Feb 2013 20:47:35 -0000

I'm strongly against canonicalization.  The XML canonicalization experience was horrible and resulted in more interop bugs than any other aspect of XML DSIG, XML ENC, etc.  Let's not repeat the mistakes of our elders. ;-)

I also haven't seen a clear use case that canonicalization solves that can't be more easily solved another way.

				-- Mike

-----Original Message-----
From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Matt Miller (mamille2)
Sent: Tuesday, February 19, 2013 12:33 PM
To: Joe Hildebrand (jhildebr)
Cc: apps-discuss@ietf.org; json@ietf.org
Subject: Re: [apps-discuss] JSON mailing list and BoF

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

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss