IETF Logo Mail Archive

Re: [Json] Canonicalization

Francis Galiegue <fgaliegue@gmail.com> Wed, 20 February 2013 01:28 UTC

Return-Path: <fgaliegue@gmail.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 189C121F8645 for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 17:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level:
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 zbu3SbDFG72W for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 17:28:26 -0800 (PST)
Received: from mail-ee0-f46.google.com (mail-ee0-f46.google.com [74.125.83.46]) by ietfa.amsl.com (Postfix) with ESMTP id B149621F85EB for <json@ietf.org>; Tue, 19 Feb 2013 17:28:15 -0800 (PST)
Received: by mail-ee0-f46.google.com with SMTP id e49so3826507eek.5 for <json@ietf.org>; Tue, 19 Feb 2013 17:28:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=h0/jH/WlBU4keSZFVHfdIUUduZ3BJ7BbVgWCnVmdcXs=; b=UUKG1WGESfIOKNbZl0pXMVukDD8/FXhHq+p232H6Ssjb1adGnE/gH2hjmtWpRrQMlJ Ih6wMZfs1PoXPosvH0cUhS1esnq/fkCp4O9MXDYzBZixpvN4EUan37NGt8QIWgHXH6O4 pBbwnxcssUJEPhoNcS5oxi0f09FxAnrLxsW7mwFYH0ZjT4c9zoWtZuZfpuRioeUfBktp 9b5z1y7BploWcPS1HJPifKPSsD0YCPyXDGqXj/lcIm9iRhnWYpJwSOjl51RBvF4DY12w Uh+aRGmgZHYeYObilIFCEYSXKVapzvWaEv1PAZNlVRlEtlMKXZ3ZegJpgd/csXBL0nbN +iCg==
MIME-Version: 1.0
X-Received: by 10.14.183.67 with SMTP id p43mr62802941eem.10.1361323694834; Tue, 19 Feb 2013 17:28:14 -0800 (PST)
Received: by 10.14.1.7 with HTTP; Tue, 19 Feb 2013 17:28:14 -0800 (PST)
In-Reply-To: <2510D743-1CCE-42D0-9067-836F03BDD606@vpnc.org>
References: <BF7E36B9C495A6468E8EC573603ED9411513E818@xmb-aln-x11.cisco.com> <A723FC6ECC552A4D8C8249D9E07425A70F897263@xmb-rcd-x10.cisco.com> <255B9BB34FB7D647A506DC292726F6E11507579808@WSMSG3153V.srv.dir.telstra.com> <1F2DF9AD-EE7A-4CC6-BBA6-AF07D02347F9@vpnc.org> <CAK3OfOhkSdi_4kuM3SG2N=bcfAwE-3E9+_SWW8ULSfedO8HAkQ@mail.gmail.com> <2510D743-1CCE-42D0-9067-836F03BDD606@vpnc.org>
Date: Wed, 20 Feb 2013 02:28:14 +0100
Message-ID: <CALcybBDfyDGh-Gt9v-94OBM7XFzzSwywZJW_fECuig6hrN0cCw@mail.gmail.com>
From: Francis Galiegue <fgaliegue@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Canonicalization
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: Wed, 20 Feb 2013 01:28:27 -0000

On Wed, Feb 20, 2013 at 2:21 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
[snip]
> Canonicalizing is part of the signature process, not part of the JSON creation process. The spec that specifies how to sign JSON will pick what to do about canonicalization; the JOSE WG is dealing with this.
>

Just curious: how shoud signing require canonicalization in any way?
As long as you have a media type and an encoding, the content is fully
defined, right? How would JSON be any different than, say, text/plain
here? AFAIK, text/plain has never required any "canonicalization" of
any kind...

-- 
Francis Galiegue, fgaliegue@gmail.com
Try out your JSON Schemas: http://json-schema-validator.herokuapp.com

v2.23.0 | Report a Bug | By Email