IETF Logo Mail Archive

Re: [apps-discuss] Canonicalization

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

Return-Path: <mamille2@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 94C9A21E8050; Tue, 19 Feb 2013 13:42:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.543
X-Spam-Level:
X-Spam-Status: No, score=-10.543 tagged_above=-999 required=5 tests=[AWL=0.056, 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 5TyRTKBxiZeo; Tue, 19 Feb 2013 13:42:17 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 799D321E803A; Tue, 19 Feb 2013 13:42:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1273; q=dns/txt; s=iport; t=1361310137; x=1362519737; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BDdK+KgOT9Z79uRebWEnsYWeE+8o15OnEUMNb5MPu+Y=; b=R9HqbXlx94NZNdmObehROXY22r3Z3aAgz0Hbd48ltvY6m4xMMw+bM/VS aogikTGdF6xA4jWZ11eU6S/0lsEnI9hytoBRw1Uu3/DPTQ41K2qGK8yiF Uc51SXWRqxBsDXt39GSM71JFTy4PU63bm713ufsWjYKMCmgm9msF9dw6A U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAKPwI1GtJXG+/2dsb2JhbABEwDyBDRZzgh8BAQEDATo/BQsCAQgYChQQMiUCBA4FCIgEBrA0kCiOWwIxB4JfYQOnA4MHgic
X-IronPort-AV: E=Sophos;i="4.84,697,1355097600"; d="scan'208";a="175901333"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-9.cisco.com with ESMTP; 19 Feb 2013 21:42:17 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1JLgGld007668 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 21:42:16 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.203]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 15:42:16 -0600
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Thread-Topic: Canonicalization
Thread-Index: AQHODuJJdWjMn+WyCECfYKD2BiK4E5iCGsgA
Date: Tue, 19 Feb 2013 21:42:16 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411513EAEC@xmb-aln-x11.cisco.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70F897263@xmb-rcd-x10.cisco.com>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F897263@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: <FEDA23625D695D40A7984278895BCB85@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: [apps-discuss] Canonicalization
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 21:42:18 -0000

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

> On 2/19/13 1:33 PM, "Matt Miller (mamille2)" <mamille2@cisco.com> wrote:
> 
>> 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.
> 
> (individual)
> 
> Do you think draft-staykov-hu-json-canonical-form is a valid starting
> point?  My biggest beef with it is that the number syntax uses capital E
> and JavaScript's toExponential() generates a lowercase e.
> 


Assuming I think canonicalization is something that ought to be done, I think it is a decent start that needs to be expanded.  The first thing that came to my mind is string normalization, and how that relates to escape sequences.

However, while not as violently opposed as some, I am hesitant.  XML canonicalization has bitten me hard in the past, so I am carrying a bias into this conversation.  Maybe a starting point can be "don't rely on canonicalization unless you really really really have to," and we can come up with a set of those "really really really have to" scenarios.


- m&m

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

v2.23.0 | Report a Bug | By Email