
From nobody Fri Feb  8 21:11:02 2019
Return-Path: <ietf@augustcellars.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E584913115A; Fri,  8 Feb 2019 21:11:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yux3PtK_c8jA; Fri,  8 Feb 2019 21:10:59 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2D48131151; Fri,  8 Feb 2019 21:10:58 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 8 Feb 2019 21:10:51 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Anders Rundgren' <anders.rundgren.net@gmail.com>
CC: <draft-rundgren-json-canonicalization-scheme@ietf.org>, 'Mark Nottingham' <mnot@mnot.net>, 'Samuel Erdtman' <samuel@erdtman.se>, 'Bret Jordan' <jordan.ietf@gmail.com>, <json-canon@ietf.org>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com>
In-Reply-To: <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com>
Date: Fri, 8 Feb 2019 21:10:48 -0800
Message-ID: <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKM6YQQYC7r3DsdqZf77BCrHHAS2AJANXPspFSVrIA=
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/agF4SSnBZI6RqwRqBBufiw3vcF0>
Subject: Re: [Json-canon] JSON Subtype handling. Re: Review of draft-rundgren-json-canonicalization-scheme-03
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2019 05:11:01 -0000

Anders,

Two items.  First note that I changed the address of the IETF mailing =
list as the "-request" should be omitted.  This sends mail to the =
administrator not to the list.

Second.  I like the text that you have placed in Appendix E as it seems =
to do a good job of both describing the problem and providing a =
solution.  The problem is that it provides two different solutions and =
the reference from section 3.1 does not state which of the two methods =
to use.  I think you probably want to state - "Use Appendix E.2 for =
creation of new items, but use Appendix E.1 when parsing and checking an =
existing JSON serialization."

Jim


> -----Original Message-----
> From: Anders Rundgren <anders.rundgren.net@gmail.com>
> Sent: Friday, February 8, 2019 8:54 PM
> To: Jim Schaad <ietf@augustcellars.com>
> Cc: draft-rundgren-json-canonicalization-scheme@ietf.org; json-canon-
> request@ietf.org; Mark Nottingham <mnot@mnot.net>; Samuel Erdtman
> <samuel@erdtman.se>; Bret Jordan <jordan.ietf@gmail.com>
> Subject: JSON Subtype handling. Re: Review of draft-rundgren-json-
> canonicalization-scheme-03
>=20
> On 2019-01-26 03:10, Jim Schaad wrote:
> > Here are a set of comments on the current version of the draft.
>=20
> Thank you very much for these insightful comments!
>=20
> Since the comments were many I take the liberty splitting the =
responses in
> separate threads.
>=20
> Handling of subtypes in JSON strings was clearly missing in the 03 =
draft.
> The 04 draft adds the following to section 3.1 "Creation of Input =
Data":
>=20
>      Note: parsed String data MUST NOT be altered during subsequent
>      serializations.  For more information see Appendix E
>=20
> The added Appendix E (https://tools.ietf.org/html/draft-rundgren-json-
> canonicalization-scheme-04#appendix-E)
> contains a pretty extensive description of how this must be dealt =
with.
>=20
> A side-effect of this is that the updated draft now makes a =
distinction
> between "Hashable" JSON and "true" canonicalization ("Comparable" =
JSON).
> The latter is a more demanding deployment option.
>=20
> Cheers,
> Anders


From nobody Fri Feb  8 22:10:30 2019
Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECDA128AFB; Fri,  8 Feb 2019 22:10:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fEwx2I8riM80; Fri,  8 Feb 2019 22:10:27 -0800 (PST)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDD2C124C04; Fri,  8 Feb 2019 22:10:26 -0800 (PST)
Received: by mail-wm1-x32b.google.com with SMTP id f16so6928818wmh.4; Fri, 08 Feb 2019 22:10:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=tUvz9YW9TYdUaSA3NyfNdP1etr3pq0FRBm4SXG9+N3k=; b=UX17UccTr7gsNtsqxgX9p6ggVlkJVWQmxj50uN3Dw5EJ5gcJaY4i2LXP7jctrg5Fsu 6N7Qd5ScCa6G4MlVfxSfu9aCGyGsUug5jXjU2r95egfRHFg9LhrJOz963Et1Awygb5M1 uSHsmV/SupTzjTy5X17+kFbzHSIl89s9jQCBWbZ9U43D+5wecc458qPx+1qgPJzqkpVS 5+BH9O/PwtGe1jUpl38lC8GNXlX1oROn5c+zDvgH8l+r1YDbJiK0IOMPmubpZEEjH1lF jXxfMxUbqsss4IU+tCOJerKql03IqKjDYlDHoGEkIzhy1ftnCnmMJyxhdZVc5M45wKGl VqFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=tUvz9YW9TYdUaSA3NyfNdP1etr3pq0FRBm4SXG9+N3k=; b=d+gUlhJIptt+r2lIjRs9m3SnTuSl5KezgYpydGdUeYC2FfpHFIKfL5368S3UpFVQbG a26AEH7yXUefWNUrzr84Qj/9H+nISPiyKRSFHhukypJ/mDxgpNhi4UPqKjoR1I26kPPr lrKDY1D23hRKGqjuKOnbJU+fNa7TXUCDfAu9Z4O+3dzYaG9EuGdzD/VwC///HKiuL4zH 0Gy03ctspGujjkD0jQslkmjL+TU+AFmB1l7trYgK4BXUyaWg8SK7uHiLGpAIcCPPiJ0D i5zJMX3bI6ke2BbGNq7krB2zEGRIc3xMzJTgYumA+dEUyH/enQWUKwa95yQY8sMScrgj Ml0g==
X-Gm-Message-State: AHQUAuZgubhMTY1xWzXU4Xn7AlZ0dllfiQ6XLi8xxXjlmpnfjaIk/+Ui rK6DvM1ykUf/1s44mG3FeqhjiRbP
X-Google-Smtp-Source: AHgI3IYx+ens4wpMMNBVAOlYsQjuVWVx+jkJRq11Jeo1J8aUzf11UTOTARceNh9b31sLVrzSXbFkIA==
X-Received: by 2002:a5d:6b8b:: with SMTP id n11mr18924871wrx.216.1549692624766;  Fri, 08 Feb 2019 22:10:24 -0800 (PST)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id m21sm6007462wmi.43.2019.02.08.22.10.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Feb 2019 22:10:23 -0800 (PST)
To: Jim Schaad <ietf@augustcellars.com>
Cc: draft-rundgren-json-canonicalization-scheme@ietf.org, 'Mark Nottingham' <mnot@mnot.net>, 'Samuel Erdtman' <samuel@erdtman.se>, 'Bret Jordan' <jordan.ietf@gmail.com>, json-canon@ietf.org
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <b9c8312d-88f0-04f7-c019-e2a62fa3aea5@gmail.com>
Date: Sat, 9 Feb 2019 07:10:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/nxWM2M-_CDF_ozuuO1u5QSa01Ro>
Subject: Re: [Json-canon] JSON Subtype handling. Re: Review of draft-rundgren-json-canonicalization-scheme-03
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2019 06:10:29 -0000

On 2019-02-09 06:10, Jim Schaad wrote:
> Anders,
> 
> Two items.  First note that I changed the address of the IETF mailing list as the "-request" should be omitted.  This sends mail to the administrator not to the list.

Sorry, it was just a carbon copy of the original list of recipients..

> Second.  I like the text that you have placed in Appendix E as it seems to do a good job of both describing the problem and providing a solution.

Thanx!

> The problem is that it provides two different solutions and the reference from section 3.1 does not state which of the two methods to use.  I think you probably want to state - "Use Appendix E.2 for creation of new items, but use Appendix E.1 when parsing and checking an existing JSON serialization."

I believe this rather highlights a somewhat less clear part of the 04 draft: The distinction between "Hashable" and "Comparable" JSON.

Only "Comparable" JSON actually requires Appendix E.2 measures to function while "Hashable" JSON works with both.

These are effectively forming two levels of canonicalization:
- Hashable: JSON native level canonicalization only
- Comparable: Full canonicalization including custom data types

Anders

> 
> Jim
> 
> 
>> -----Original Message-----
>> From: Anders Rundgren <anders.rundgren.net@gmail.com>
>> Sent: Friday, February 8, 2019 8:54 PM
>> To: Jim Schaad <ietf@augustcellars.com>
>> Cc: draft-rundgren-json-canonicalization-scheme@ietf.org; json-canon-
>> request@ietf.org; Mark Nottingham <mnot@mnot.net>; Samuel Erdtman
>> <samuel@erdtman.se>; Bret Jordan <jordan.ietf@gmail.com>
>> Subject: JSON Subtype handling. Re: Review of draft-rundgren-json-
>> canonicalization-scheme-03
>>
>> On 2019-01-26 03:10, Jim Schaad wrote:
>>> Here are a set of comments on the current version of the draft.
>>
>> Thank you very much for these insightful comments!
>>
>> Since the comments were many I take the liberty splitting the responses in
>> separate threads.
>>
>> Handling of subtypes in JSON strings was clearly missing in the 03 draft.
>> The 04 draft adds the following to section 3.1 "Creation of Input Data":
>>
>>       Note: parsed String data MUST NOT be altered during subsequent
>>       serializations.  For more information see Appendix E
>>
>> The added Appendix E (https://tools.ietf.org/html/draft-rundgren-json-
>> canonicalization-scheme-04#appendix-E)
>> contains a pretty extensive description of how this must be dealt with.
>>
>> A side-effect of this is that the updated draft now makes a distinction
>> between "Hashable" JSON and "true" canonicalization ("Comparable" JSON).
>> The latter is a more demanding deployment option.
>>
>> Cheers,
>> Anders
> 


From nobody Fri Feb  8 23:05:41 2019
Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6E5613117A for <json-canon@ietfa.amsl.com>; Fri,  8 Feb 2019 23:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OebcP4WgbnqX for <json-canon@ietfa.amsl.com>; Fri,  8 Feb 2019 23:05:37 -0800 (PST)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50ECD130F28 for <json-canon@ietf.org>; Fri,  8 Feb 2019 23:05:37 -0800 (PST)
Received: by mail-ed1-x52f.google.com with SMTP id h50so4657309ede.5 for <json-canon@ietf.org>; Fri, 08 Feb 2019 23:05:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:cc:references:from:to:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=vAYJjk9PltaePUOo+0BYk63f/8yPmg94gMkkeXVbB4E=; b=chO8ppOkiBOY3hUobfg8OD9i+vrEUqRGE3SOT0ihd9uClESr3n5wKRlxtk5qNYVSBD xrus5zQ90PSNUaiLHSVBNK2cRn/13tmZqigZOJ4t8RufQWm028YnBHSLx0on+5OiDb0z 65qbIqYzwxwK34hLxhAS9lpDFrtsVUWBCJpMYccnqbeX8bU/IcbMMeilpzj9DQoEDpXl vzUbaMx7HvWuC4nhTC/r19ZDPG2tmqwmnA6LO4HWmjb/yiu6mLK7Q9LtbTg2p95YAt53 kqUp+XF+AIrtTPyq8uQnO5pR1H3Cs7HfEGUHbA3VjyhZ+3SVegy4sLqRfMfcP1pSJw8e yxTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:cc:references:from:to:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=vAYJjk9PltaePUOo+0BYk63f/8yPmg94gMkkeXVbB4E=; b=lfHReAkuEWaE93YVrS8OgK+DM19NyDF4utL9cZSQQ4Z1QYKMPpfulllkgHUY/NlYRL CICzsRWI2Y9FUtHumDr2nS04L5q6MfvKD69o2uCf4yxxaZXS31kKXsg8Tl0ByN++N4+1 RiIzBAa5V+UTmrJrHWb0posKCB19NLySepKYTkfBHryzGr8S88NH5ct6WpPTKPJaZsi4 y9qci0yXX9zvwoiPykZUJsQoRb6/vQQW2+zw9M60rCBADX94x+hAJ7VOn4zp9zJjoqh/ LQ5TitFwJklPfVLKj9fQKD1gnDPFpYj+GeSbhjwnDSM9GtzB9ce2mI7PePpIK1hOHg/8 E3Gw==
X-Gm-Message-State: AHQUAuaNFUyGS2T+ow9R97iptdNia1dqDKBE+xcHBy3fUR1UWo9775WR sKI17dstB5gI6zMXrNUIhlA=
X-Google-Smtp-Source: AHgI3IZOYckvGYNsxHWu4LOF+N8Gu/jLQfSvXUIvCgL+lB3IFvrbtDd+Uh1tdp+SAUEmNXdVQAecqw==
X-Received: by 2002:a17:906:63c9:: with SMTP id u9mr18989566ejk.190.1549695935601;  Fri, 08 Feb 2019 23:05:35 -0800 (PST)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id c12sm1179688edi.52.2019.02.08.23.05.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 08 Feb 2019 23:05:34 -0800 (PST)
Cc: 'Samuel Erdtman' <samuel@erdtman.se>, 'Bret Jordan' <jordan.ietf@gmail.com>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
To: json-canon@ietf.org
Message-ID: <7f7557ae-c86a-013a-6758-279034728be5@gmail.com>
Date: Sat, 9 Feb 2019 08:05:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/l5vHTamEl8N4QnzolBLM9UvDHgo>
Subject: [Json-canon] Dropping "Comparable" JSON
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2019 07:05:40 -0000

All,
This is an open question.
Ideally you want a design to cover as many use-cases as possible, right?
Sometimes that ambition turns out to be counterproductive making your most important use-cases suffer.


When I in retrospect look at
https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-04
I begin to wonder if "Comparable" JSON (in the draft named "true" canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call this.

Why is that?  Well, to begin with "Comparable" JSON leaves a lot of thorny decisions to some other document or entity to worry about:
https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-04#appendix-E.2

In addition, having actually built a few test systems comparing JSON data, I note that the possibility for creating 100% stable input data is unlikely to be particularly common. Time stamps, transaction IDs and last but not least crypto, makes this requirement rather hard to achieve in practice.

That is, "Comparable" JSON appears to be a difficult edge case and IMHO [probably] not worth dealing with. The 80/20 rule is pretty much a fact.

This seems like an ideal topic for the BoF session we have requested :-)

WDYT?

Anders


From nobody Mon Feb 11 20:47:52 2019
Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2601412D4EF for <json-canon@ietfa.amsl.com>; Mon, 11 Feb 2019 20:47:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fblzsUKkHDBq for <json-canon@ietfa.amsl.com>; Mon, 11 Feb 2019 20:47:48 -0800 (PST)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E718C12D4E9 for <json-canon@ietf.org>; Mon, 11 Feb 2019 20:47:47 -0800 (PST)
Received: by mail-wm1-x334.google.com with SMTP id a62so1442080wmh.4 for <json-canon@ietf.org>; Mon, 11 Feb 2019 20:47:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=a04YBNtomHFMVF03vWkUMmrvBci257mLs/5MlK+J31w=; b=cU9cOo8elZ1BxPpDk3UtcY8UNx4h8dn6Pu1bGfFG0zw3DAX0p0XJmaKTloBHAtWfsj gnqpIpxK6d+ZoTrNNIdHiClqbM0sp+gH3Kmoa+vinnInAUyyqLvtgwPWPSOJyEsSFS8d m13hVeiR0/W2pFvBg3QnLE6RTIfMNq3kvaqalFQ9egEz5rxAoa5qf8oQlSPl7+3bjnxV pXOixhMRbqv5LhmffJU7whf43SLq/OcCPspM9iv9zu29VMGkwN+FUFreSN/Ay50r1+W/ ORpmWZuH5QMv1bEqW4Pk5gFH1nDTsNp3pI23Q114z4NoAGIiQn9Zf5J/rNdX7TH92HCi yECw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=a04YBNtomHFMVF03vWkUMmrvBci257mLs/5MlK+J31w=; b=Iq8cbGuv42s1j03nLuLQD46N5Gao4X02jCZ6jx3UVopAQCORPsN73hm5wDqA+EAHxH t/hBY9XiSCN8xd2sNvy7Oyop9oGQ2Eg6RXbzyHVlZpwrGbMIidQhpauv3xcYAxixBMBU ZGGZWICxi+CTu6SJ0WjwOGsTvKd3afUky09H4UQC2SK9MxcMu8h5eI1ky714H1ZhbIJS 6INl4sxIbhLny/q7xFaTFu5qG1S2oTIRJLBqcN82YtO3kqrL8G073uL8yEMmVKW6mtay dTO129e2dapyz/4X92VzTrmzGJMB86tHgrycx8Gio4BjT/5stIMViF3FzeP7NvR24Ss9 T+jA==
X-Gm-Message-State: AHQUAuZWyE5cDdlzn4HItAmeGm49OVMSyZQO+eKpKfLzdNRRyKtP2OQw xmleGU/o5WVDvkonN7s2q6dfsNPK
X-Google-Smtp-Source: AHgI3Ib8aOefV4P640HLrYhexKCTr4AC5ssvdZox5SQvnJgtgF4w7AbDxaHGvlvy4m5I83JX4BqYJg==
X-Received: by 2002:a1c:ce8a:: with SMTP id e132mr1210890wmg.12.1549946865986;  Mon, 11 Feb 2019 20:47:45 -0800 (PST)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id 184sm3182725wmz.18.2019.02.11.20.47.44 for <json-canon@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Feb 2019 20:47:44 -0800 (PST)
From: Anders Rundgren <anders.rundgren.net@gmail.com>
To: "json-canon@ietf.org" <json-canon@ietf.org>
References: <154977434604.29489.7608744124216682984.idtracker@ietfa.amsl.com>
Message-ID: <f5470801-8c22-9095-1946-ab3cc37f5f96@gmail.com>
Date: Tue, 12 Feb 2019 05:47:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <154977434604.29489.7608744124216682984.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/9-lpf_mwC17knQXAT8LC5Xe77CI>
Subject: [Json-canon] draft-rundgren-comparable-json-03
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2019 04:47:50 -0000

https://tools.ietf.org/html/draft-rundgren-comparable-json-03

Abstract:
     This application note describes how JCS [JCS] can be utilized to
     support applications needing canonicalization beyond the core JSON
     [RFC8259] level, with comparisons as the primary target.


The idea behind this proposal is keeping JCS focused on "Hashable" JSON
while leaving "Comparable" JSON to the (non-standard) application space.

Anders





From nobody Tue Feb 12 06:55:31 2019
Return-Path: <jordan.ietf@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1954012426A for <json-canon@ietfa.amsl.com>; Tue, 12 Feb 2019 06:55:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JukVmFwHieqa for <json-canon@ietfa.amsl.com>; Tue, 12 Feb 2019 06:55:27 -0800 (PST)
Received: from mail-it1-x12e.google.com (mail-it1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F97C1200ED for <json-canon@ietf.org>; Tue, 12 Feb 2019 06:55:27 -0800 (PST)
Received: by mail-it1-x12e.google.com with SMTP id v72so8204220itc.0 for <json-canon@ietf.org>; Tue, 12 Feb 2019 06:55:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=p04b/FHUlj2xWLBNa8Kk9/UdRpOfzRJyrKRVeKvgxvM=; b=ETT1K23ryuGM3vZa9U+550r8STl3nv2YPSXeiHwP8jv8Xf5OK3Fdbnu1m6Ppz4Hy/d QE06aJ9FAA0mXI1vjRbDT2492fiqcO9MdXLCng2+gy7p0ba70UiYQpymteeheh3Y30KC 1uRTFt+7sKyJOTpDLd3omhvLNIyX1pQ8IiFfSbuSBx6lzg/6dmvRxxWfjTaMiOY1JPz4 Zg6R+/qUoj37e8Ld7WefOA2ua2+GeNLx8Hjn+t6njhWM50JfqenKni+YWt6fIhXbgrkN enkw5u2kjJswtuv/DtLm+4ihXUkBRQ7QvSaq6xkzxDJbFz5LB+Ye21aDMsSRhMKt07cD tbxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=p04b/FHUlj2xWLBNa8Kk9/UdRpOfzRJyrKRVeKvgxvM=; b=dIhpKdJUj0/qZTPoIdqdIvJN7B6mKc3p1Fh0RzEuMvMY5bnY+HgdWlz0WK18zfnRMb SVJdu2zpVpUiYi0QWvHIeO+IvjH/0L9p76eHZ0f6JvPpMrxm9g2DPpuzAGJK96/Uqytz Nqr6h4BIOk48HK2fWuX4q6Aer85Db+Va/916lOQzX0khZ406/A5PRZpNNCKB14bqUGsE Ez9IN5xEkcwoL4y4a+k4jJLK9RjW83A0GeOVs+Ak9j/DrqrybDtxRqe3hDzz+cxMYTNs bJ2y2WIXKimHi+/1G18hH/Yd/GLeBQHSYdKILgxb1ZKpNs4V77Mo5RDvAf9xXEBafHe0 G+iA==
X-Gm-Message-State: AHQUAuZdHTwSXvqEQ6NyVWtpn6/AvO/vndSwhwHitPlamUE58efeQu7Q CjHbcQPjDC637glH97fU2Os=
X-Google-Smtp-Source: AHgI3IZWXtkFUDEU1E0KYoB8uoGobo1KyKqOlYSFd735HhujL3MabLrRvAP86Lh1HyVmGGvl+OUSXg==
X-Received: by 2002:a02:5546:: with SMTP id e67mr2222463jab.10.1549983326290;  Tue, 12 Feb 2019 06:55:26 -0800 (PST)
Received: from ?IPv6:2605:a601:a028:986:90f5:f3fe:6967:5a85? ([2605:a601:a028:986:90f5:f3fe:6967:5a85]) by smtp.gmail.com with ESMTPSA id a21sm6061785iod.63.2019.02.12.06.55.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Feb 2019 06:55:25 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <874D3146-9FD5-4998-B051-5D3244A91B9F@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D3646832-7471-4FCA-8809-E5CDAFA90B5F"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 12 Feb 2019 07:55:22 -0700
In-Reply-To: <7f7557ae-c86a-013a-6758-279034728be5@gmail.com>
Cc: json-canon@ietf.org, Samuel Erdtman <samuel@erdtman.se>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com> <7f7557ae-c86a-013a-6758-279034728be5@gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/uUc15mBerDNu5KZBUK-prOJP_sw>
Subject: Re: [Json-canon] Dropping "Comparable" JSON
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2019 14:55:30 -0000

--Apple-Mail=_D3646832-7471-4FCA-8809-E5CDAFA90B5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I would rather focus on the key deliverable and punt on this for a =
future version.=20


Thanks,
Bret
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that =
can not be unscrambled is an egg."

> On Feb 9, 2019, at 12:05 AM, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>=20
> All,
> This is an open question.
> Ideally you want a design to cover as many use-cases as possible, =
right?
> Sometimes that ambition turns out to be counterproductive making your =
most important use-cases suffer.
>=20
>=20
> When I in retrospect look at
> =
https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-04=

> I begin to wonder if "Comparable" JSON (in the draft named "true" =
canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call =
this.
>=20
> Why is that?  Well, to begin with "Comparable" JSON leaves a lot of =
thorny decisions to some other document or entity to worry about:
> =
https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-04=
#appendix-E.2
>=20
> In addition, having actually built a few test systems comparing JSON =
data, I note that the possibility for creating 100% stable input data is =
unlikely to be particularly common. Time stamps, transaction IDs and =
last but not least crypto, makes this requirement rather hard to achieve =
in practice.
>=20
> That is, "Comparable" JSON appears to be a difficult edge case and =
IMHO [probably] not worth dealing with. The 80/20 rule is pretty much a =
fact.
>=20
> This seems like an ideal topic for the BoF session we have requested =
:-)
>=20
> WDYT?
>=20
> Anders


--Apple-Mail=_D3646832-7471-4FCA-8809-E5CDAFA90B5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">I =
would rather focus on the key deliverable and punt on this for a future =
version.&nbsp;<div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""><div class=3D"">
<div style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div class=3D"" style=3D"orphans: 2; widows: 2; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; line-height: normal; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none;">Thanks,</span></div><div =
class=3D"" style=3D"orphans: 2; widows: 2; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; line-height: normal; text-align: =
-webkit-auto; border-spacing: 0px; -webkit-text-decorations-in-effect: =
none;">Bret</span></div><div class=3D"" style=3D"orphans: 2; widows: =
2;"><span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; text-align: -webkit-auto; =
border-spacing: 0px;"><div class=3D"" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; text-align: -webkit-auto; =
border-spacing: 0px;"><div class=3D""><font color=3D"#7c7c7c" =
face=3D"Calibre, Verdana" class=3D"" style=3D"font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"" style=3D"font-size: 11px;">PGP =
Fingerprint:&nbsp;</span></font><span class=3D"" style=3D"text-align: =
-webkit-auto; font-size: 11px;"><font color=3D"#7c7c7c" face=3D"Calibre, =
Verdana" class=3D"">63B4 FC53 680A 6B7D 1447 &nbsp;F2C0 74F8 ACAE 7415 =
0050</font></span></div><div class=3D"" style=3D"font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"" style=3D"color: rgb(124, 124, 124); font-size: 8pt; =
font-family: Calibre, Verdana; text-align: -webkit-auto;">"Without =
cryptography vihv vivc ce xhrnrw, however, the only thing that can not =
be unscrambled is an =
egg."</span></div></span></div></span></div></span></div></span></span></d=
iv></div>
</div>
<div style=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Feb 9, 2019, at 12:05 AM, Anders Rundgren &lt;<a =
href=3D"mailto:anders.rundgren.net@gmail.com" =
class=3D"">anders.rundgren.net@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">All,<br class=3D"">This is an open question.<br =
class=3D"">Ideally you want a design to cover as many use-cases as =
possible, right?<br class=3D"">Sometimes that ambition turns out to be =
counterproductive making your most important use-cases suffer.<br =
class=3D""><br class=3D""><br class=3D"">When I in retrospect look at<br =
class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-rundgren-json-canonicalization-s=
cheme-04" =
class=3D"">https://tools.ietf.org/html/draft-rundgren-json-canonicalizatio=
n-scheme-04</a><br class=3D"">I begin to wonder if "Comparable" JSON (in =
the draft named "true" canonicalization) shouldn't be a "Feature at =
Risk" as the W3C folks call this.<br class=3D""><br class=3D"">Why is =
that? &nbsp;Well, to begin with "Comparable" JSON leaves a lot of thorny =
decisions to some other document or entity to worry about:<br =
class=3D"">https://tools.ietf.org/html/draft-rundgren-json-canonicalizatio=
n-scheme-04#appendix-E.2<br class=3D""><br class=3D"">In addition, =
having actually built a few test systems comparing JSON data, I note =
that the possibility for creating 100% stable input data is unlikely to =
be particularly common. Time stamps, transaction IDs and last but not =
least crypto, makes this requirement rather hard to achieve in =
practice.<br class=3D""><br class=3D"">That is, "Comparable" JSON =
appears to be a difficult edge case and IMHO [probably] not worth =
dealing with. The 80/20 rule is pretty much a fact.<br class=3D""><br =
class=3D"">This seems like an ideal topic for the BoF session we have =
requested :-)<br class=3D""><br class=3D"">WDYT?<br class=3D""><br =
class=3D"">Anders<br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_D3646832-7471-4FCA-8809-E5CDAFA90B5F--


From nobody Tue Feb 12 09:02:15 2019
Return-Path: <cabo@tzi.org>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C341292F1 for <json-canon@ietfa.amsl.com>; Tue, 12 Feb 2019 09:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yQ8GqUVXAJO2 for <json-canon@ietfa.amsl.com>; Tue, 12 Feb 2019 09:02:11 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B944128B33 for <json-canon@ietf.org>; Tue, 12 Feb 2019 09:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x1CH202T015395; Tue, 12 Feb 2019 18:02:06 +0100 (CET)
Received: from [192.168.217.106] (p54A6CC50.dip0.t-ipconnect.de [84.166.204.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 43zTTh50l5z1Br6; Tue, 12 Feb 2019 18:02:00 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7f7557ae-c86a-013a-6758-279034728be5@gmail.com>
Date: Tue, 12 Feb 2019 18:02:15 +0100
Cc: json-canon@ietf.org, Samuel Erdtman <samuel@erdtman.se>, Bret Jordan <jordan.ietf@gmail.com>
X-Mao-Original-Outgoing-Id: 571683730.587326-1247682731b5da55db503e0358c0c549
Content-Transfer-Encoding: quoted-printable
Message-Id: <F80FF7EB-B1A2-4337-8BC7-86E6C1AB725D@tzi.org>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com> <7f7557ae-c86a-013a-6758-279034728be5@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/XscmwAGMPS6dwqRAb4WQxF6Fa-I>
Subject: Re: [Json-canon] Dropping "Comparable" JSON
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2019 17:02:13 -0000

On Feb 9, 2019, at 08:05, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>=20
> I begin to wonder if "Comparable" JSON (in the draft named "true" =
canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call =
this.

Well, first of all, there is no =E2=80=9Cfeature=E2=80=9D here =E2=80=94 =
the current draft just points out that deterministic encoding =
(=E2=80=9Ccanonicalization=E2=80=9D) reaches up to the application using =
JSON wherever that does its own encoding work.

That is a fact that is good to know, but nothing is contributed to =
interoperability by this document.

To do so, one would need a way to describe elements of the application =
data model and constrain the application data encoding decisions made on =
the way to the JSON data model.  We don=E2=80=99t have a good way to do =
this at the moment (even if the document misleadingly mentions the =
=E2=80=9Cschema=E2=80=9D word).

Actually, the document about deterministic encoding of JSON (your =
=E2=80=9CHashable=E2=80=9D thing =E2=80=94 I still have no idea where =
these confused terms came from) could be stating this fact, if only as a =
matter of delineating what is *not* being defined in that document.

The document currently does not say how it was intended to be developed =
further.  As it stands, it is indeed of little use.  Collecting a set of =
preferred application-data-model to JSON-data-model encoding decisions, =
however, might be a useful undertaking, somewhat unrelated to the =
constraints on serializing the JSON data model that the other document =
wants to define, and probably on a much longer time scale.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Feb 13 13:21:59 2019
Return-Path: <jordan.ietf@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2859912F18C for <json-canon@ietfa.amsl.com>; Wed, 13 Feb 2019 13:21:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVKXM6EOLH5R for <json-canon@ietfa.amsl.com>; Wed, 13 Feb 2019 13:21:56 -0800 (PST)
Received: from mail-it1-x129.google.com (mail-it1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA09C12E7C1 for <json-canon@ietf.org>; Wed, 13 Feb 2019 13:21:55 -0800 (PST)
Received: by mail-it1-x129.google.com with SMTP id h6so7994036itl.1 for <json-canon@ietf.org>; Wed, 13 Feb 2019 13:21:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=MOof1l/EkZMfxQ+VhBBV/DrCYnMIKRBAZqRjnqd1wj4=; b=cPQLBBsHH3k7N1NwN558KRE4jd2tQeMtCKtcWHPThxokihdZVxTGCw8sfr33VYoKI9 b58s2fqnlcuKW2DSXiPFtBiZbC28Ga7VAJvHUvq8POiqxkFZlbDwV/V4P5eewW9Tdgev nycJWNnQeCx1e5F7WmX8WAFpIi5lSSsve5767Ex2bKun5iEn2ipMf8A1xWiYm1F1UJG3 5VoxPaODYiyWvduEWAAvY2U5I97kcMEEZ/OnurNvUxpy6I94w1B+JPrP8bKix9sfIMog y9o3lF2ybygbD3ERdzSsEfqqDE/+KT8mzJxpkVba8Q8K778lHJf7GjNHOay/Z9HpYaxt jyiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=MOof1l/EkZMfxQ+VhBBV/DrCYnMIKRBAZqRjnqd1wj4=; b=IXlkM8qwMWK6G3MjXNxuyfAGuosRA9Pw8q0f/WGKULTUxjPKmaJ0tc/q49FASw/8kr FYb6DHE63IR9tDe44VAVCCAG98kiGGNU+OzzAb+E7Qe/8hbjwIgXJdv677KSpoAsMh75 8SYSl5hRF0DLaoObA1fEMJQD3kuQ15McxM1po0phAyg5EvzSGF8kWHjc2BuzCdm0Z4ZT Hp3rWctoe52T8eQAfFpDSeeeIt2si+XPy+5QBh6R/7EriYzuik0rJ6TnRZaL3769dBLV bXkL2Uo/0coBLH1apWcOHDqwROefm/UOOOtdP6h3LeweAq4lx1q+D6gVu6P6RB3nk5zE WpSA==
X-Gm-Message-State: AHQUAuYW6XACOzt5YiIdLHHomGQSmGhyn0Hv0IQIDfaRAhtj2zSoplsI /OkbzdCH/RO5nLmJSqxuYQQ=
X-Google-Smtp-Source: AHgI3IaMaOwErM0AJM3TaRfg0SC8apdkqEgaxJSdNSQL8w3ZNTfzE1TUoCDr3P+Kn90FOKAJrj+XiQ==
X-Received: by 2002:a24:3391:: with SMTP id k139mr128329itk.25.1550092915183;  Wed, 13 Feb 2019 13:21:55 -0800 (PST)
Received: from [172.16.255.50] ([216.194.115.4]) by smtp.gmail.com with ESMTPSA id 196sm202654itu.33.2019.02.13.13.21.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 13:21:54 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <354466BD-9D7C-463F-BBB4-E797267726A4@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D5E9AE9E-F376-4A91-A0CF-0E70B5AEBF8A"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Wed, 13 Feb 2019 14:21:51 -0700
In-Reply-To: <F80FF7EB-B1A2-4337-8BC7-86E6C1AB725D@tzi.org>
Cc: Anders Rundgren <anders.rundgren.net@gmail.com>, json-canon@ietf.org, Samuel Erdtman <samuel@erdtman.se>
To: Carsten Bormann <cabo@tzi.org>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com> <7f7557ae-c86a-013a-6758-279034728be5@gmail.com> <F80FF7EB-B1A2-4337-8BC7-86E6C1AB725D@tzi.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/PJ_BQ6KH2lf5yQGkJZfBbH2_v6g>
Subject: Re: [Json-canon] Dropping "Comparable" JSON
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2019 21:21:58 -0000

--Apple-Mail=_D5E9AE9E-F376-4A91-A0CF-0E70B5AEBF8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I am not sure I understand what you are proposing or what changes you =
would like.   I personally think that JCS should focus on a very limited =
and narrow set of use cases.  We should address how to represent JSON in =
a canonical form, period.  What people do with it beyond that is =
out-of-scope.

Thanks,
Bret
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that =
can not be unscrambled is an egg."

> On Feb 12, 2019, at 10:02 AM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On Feb 9, 2019, at 08:05, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>>=20
>> I begin to wonder if "Comparable" JSON (in the draft named "true" =
canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call =
this.
>=20
> Well, first of all, there is no =E2=80=9Cfeature=E2=80=9D here =E2=80=94=
 the current draft just points out that deterministic encoding =
(=E2=80=9Ccanonicalization=E2=80=9D) reaches up to the application using =
JSON wherever that does its own encoding work.
>=20
> That is a fact that is good to know, but nothing is contributed to =
interoperability by this document.
>=20
> To do so, one would need a way to describe elements of the application =
data model and constrain the application data encoding decisions made on =
the way to the JSON data model.  We don=E2=80=99t have a good way to do =
this at the moment (even if the document misleadingly mentions the =
=E2=80=9Cschema=E2=80=9D word).
>=20
> Actually, the document about deterministic encoding of JSON (your =
=E2=80=9CHashable=E2=80=9D thing =E2=80=94 I still have no idea where =
these confused terms came from) could be stating this fact, if only as a =
matter of delineating what is *not* being defined in that document.
>=20
> The document currently does not say how it was intended to be =
developed further.  As it stands, it is indeed of little use.  =
Collecting a set of preferred application-data-model to JSON-data-model =
encoding decisions, however, might be a useful undertaking, somewhat =
unrelated to the constraints on serializing the JSON data model that the =
other document wants to define, and probably on a much longer time =
scale.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20


--Apple-Mail=_D5E9AE9E-F376-4A91-A0CF-0E70B5AEBF8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">I =
am not sure I understand what you are proposing or what changes you =
would like. &nbsp; I personally think that JCS should focus on a very =
limited and narrow set of use cases. &nbsp;We should address how to =
represent JSON in a canonical form, period. &nbsp;What people do with it =
beyond that is out-of-scope.<div class=3D""><br class=3D""></div><div =
class=3D""><span style=3D"-webkit-text-decorations-in-effect: none; =
orphans: 2; widows: 2;" class=3D"">Thanks,</span></div><div =
class=3D""><div class=3D""><div style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div class=3D"" =
style=3D"orphans: 2; widows: 2; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; line-height: normal; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none;">Bret</span></div><div =
class=3D"" style=3D"orphans: 2; widows: 2;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; text-align: -webkit-auto; =
border-spacing: 0px;"><div class=3D"" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; text-align: -webkit-auto; =
border-spacing: 0px;"><div class=3D""><font color=3D"#7c7c7c" =
face=3D"Calibre, Verdana" class=3D"" style=3D"font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"" style=3D"font-size: 11px;">PGP =
Fingerprint:&nbsp;</span></font><span class=3D"" style=3D"text-align: =
-webkit-auto; font-size: 11px;"><font color=3D"#7c7c7c" face=3D"Calibre, =
Verdana" class=3D"">63B4 FC53 680A 6B7D 1447 &nbsp;F2C0 74F8 ACAE 7415 =
0050</font></span></div><div class=3D"" style=3D"font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"" style=3D"color: rgb(124, 124, 124); font-size: 8pt; =
font-family: Calibre, Verdana; text-align: -webkit-auto;">"Without =
cryptography vihv vivc ce xhrnrw, however, the only thing that can not =
be unscrambled is an =
egg."</span></div></span></div></span></div></span></div></span></span></d=
iv></div>
</div>
<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Feb 12, 2019, at 10:02 AM, Carsten Bormann &lt;<a =
href=3D"mailto:cabo@tzi.org" class=3D"">cabo@tzi.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">On Feb 9, 2019, at 08:05, Anders Rundgren &lt;<a =
href=3D"mailto:anders.rundgren.net@gmail.com" =
class=3D"">anders.rundgren.net@gmail.com</a>&gt; wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">I begin =
to wonder if "Comparable" JSON (in the draft named "true" =
canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call =
this.<br class=3D""></blockquote><br class=3D"">Well, first of all, =
there is no =E2=80=9Cfeature=E2=80=9D here =E2=80=94 the current draft =
just points out that deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D) reaches up to the application using JSON wherever that does its own =
encoding work.<br class=3D""><br class=3D"">That is a fact that is good =
to know, but nothing is contributed to interoperability by this =
document.<br class=3D""><br class=3D"">To do so, one would need a way to =
describe elements of the application data model and constrain the =
application data encoding decisions made on the way to the JSON data =
model. &nbsp;We don=E2=80=99t have a good way to do this at the moment =
(even if the document misleadingly mentions the =E2=80=9Cschema=E2=80=9D =
word).<br class=3D""><br class=3D"">Actually, the document about =
deterministic encoding of JSON (your =E2=80=9CHashable=E2=80=9D thing =
=E2=80=94 I still have no idea where these confused terms came from) =
could be stating this fact, if only as a matter of delineating what is =
*not* being defined in that document.<br class=3D""><br class=3D"">The =
document currently does not say how it was intended to be developed =
further. &nbsp;As it stands, it is indeed of little use. =
&nbsp;Collecting a set of preferred application-data-model to =
JSON-data-model encoding decisions, however, might be a useful =
undertaking, somewhat unrelated to the constraints on serializing the =
JSON data model that the other document wants to define, and probably on =
a much longer time scale.<br class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe, =
Carsten<br class=3D""><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_D5E9AE9E-F376-4A91-A0CF-0E70B5AEBF8A--


From nobody Wed Feb 13 22:03:52 2019
Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 068BE131133 for <json-canon@ietfa.amsl.com>; Wed, 13 Feb 2019 22:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N0ow9bwLDt2O for <json-canon@ietfa.amsl.com>; Wed, 13 Feb 2019 22:03:48 -0800 (PST)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D592E131016 for <json-canon@ietf.org>; Wed, 13 Feb 2019 22:03:47 -0800 (PST)
Received: by mail-wr1-x42d.google.com with SMTP id c8so5073424wrs.4 for <json-canon@ietf.org>; Wed, 13 Feb 2019 22:03:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=76IoYRSF5ndstyePFAhLtbvY/b1PpYCbUg1QrCJhGqI=; b=agzznfx1deIHVfWrUNSRGJY3CyQ//cjRhXAtc3ci+TJqLFUL9FGEIUd94vzrqPFUNv S6r6I8Az9uaLeYXmGMVmnI69Yb+6k7gR08ig4/BfdT3Sxw5A/zsCeLUqbad1wY5OXD5a xJ17AEQsoki6e2m2tQywZxcT10IvWYe5Lx4vJBZOu9eMSkyB5zLma8nthQirzVWm8K4U 9yo405HrXDtoSGWoyWXXCkVSezSjPKT/y6QksA+KsaxxmNHUvzyk3/OG7Te9sat3Hr5T b94WeKfiao5TEd8hqlcNdLcAcyY+saucc5jHcBy/4x70HCwJQ3+a3OIfrTD1/wVI/+nM KKyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=76IoYRSF5ndstyePFAhLtbvY/b1PpYCbUg1QrCJhGqI=; b=TROtLCjBQBPczhknQQ58hwPe6NuIRqrIA0dzHeX2YJHUZnxACS2qzwLFwQETAoyemv CRJ48jvUR/eelUrmBX+dzXzjgamnub5J8Ph+sw9+pikR8e824rA4MfAV5I17tjlmRtzT /dCdrvSwexANzpVoNXpAt6M0C9SNpwCiuoTfCJ5dyv8XLdWLo9+FcvvID8uTuBwXEAIz 1PfhJkikdprumnNYh0TRU7UpxXZngQwefDWsUptk3uIPDXiAXM/dQUgaIf3T5OphM9Ul IsEujpmhXrW6x5ekEwc66iel9koVblRXwJhPDmDKHYxDNigLs/wWajMXgVm+Q0R978Mk yspw==
X-Gm-Message-State: AHQUAuZJGLooCvqy9Wavk8/VpYX9zq0VoZ8qsUVfXcTe/M2K/FVDDLBW +1KkqW3Bmhf90S8aXIZoJF0=
X-Google-Smtp-Source: AHgI3IbV7bpI+75ZHjEjkv5wXbTVUw9tKqWD9R++YMRO+9tT828q5Gv0bGsxZLlsKTMCdbrT2Ro38A==
X-Received: by 2002:adf:a104:: with SMTP id o4mr1214349wro.244.1550124226268;  Wed, 13 Feb 2019 22:03:46 -0800 (PST)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id p16sm1607803wro.25.2019.02.13.22.03.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 22:03:44 -0800 (PST)
From: Anders Rundgren <anders.rundgren.net@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: json-canon@ietf.org, Samuel Erdtman <samuel@erdtman.se>, Bret Jordan <jordan.ietf@gmail.com>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com> <7f7557ae-c86a-013a-6758-279034728be5@gmail.com> <F80FF7EB-B1A2-4337-8BC7-86E6C1AB725D@tzi.org>
Message-ID: <fea41437-88b8-c6aa-8e6e-b3d4c2bf5892@gmail.com>
Date: Thu, 14 Feb 2019 07:03:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <F80FF7EB-B1A2-4337-8BC7-86E6C1AB725D@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/45zNdPpBKjO9VDjFIm4OgzHPrYw>
Subject: Re: [Json-canon] Dropping "Comparable" JSON
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2019 06:03:50 -0000

Carsten,

Starting in another end...

As you probably know REST is a established way of architecting Web applications.  A fly in the soup is that there is no standard for creating signed REST requests.

Instead proprietary signature schemes based on detached clear text JSON data and HTTP bindings have become the norm while the JOSE WG has been concluded.  It has been claimed that the "right" solution (encoding and embedding the request data to be signed in the signature container itself) eventually will win.  However, I haven't seen this happening.  Maybe somebody can provide a link to such an activity?

In addition to be useful in entirely different contexts, JCS may function as a building block for future work in the REST space since it offers advantages over detached formats and HTTP bindings.

"Hashable" is a term I got from a related discussion on the ES-mozilla list.  In a JCS context "Hashable" means that a producer of (I-)JSON data can calculate a hash or signature over the data to be sent while the consumer of that data can use the hash or signature to verify the correctness of the received data. "Hashable" is obviously a lower form of canonicalization than required for comparing JSON data from arbitrary sources.

Regarding interoperability: With the (recently added...) constraint that the parsing of a JSON String followed by a serialization MUST return the same string you have together with the core JCS algorithm all the interoperability needed for supporting cryptographic methods.

Anders


On 2019-02-12 18:02, Carsten Bormann wrote:
> On Feb 9, 2019, at 08:05, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>
>> I begin to wonder if "Comparable" JSON (in the draft named "true" canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call this.
> 
> Well, first of all, there is no “feature” here — the current draft just points out that deterministic encoding (“canonicalization”) reaches up to the application using JSON wherever that does its own encoding work.
> 
> That is a fact that is good to know, but nothing is contributed to interoperability by this document.
> 
> To do so, one would need a way to describe elements of the application data model and constrain the application data encoding decisions made on the way to the JSON data model.  We don’t have a good way to do this at the moment (even if the document misleadingly mentions the “schema” word).
> 
> Actually, the document about deterministic encoding of JSON (your “Hashable” thing — I still have no idea where these confused terms came from) could be stating this fact, if only as a matter of delineating what is *not* being defined in that document.
> 
> The document currently does not say how it was intended to be developed further.  As it stands, it is indeed of little use.  Collecting a set of preferred application-data-model to JSON-data-model encoding decisions, however, might be a useful undertaking, somewhat unrelated to the constraints on serializing the JSON data model that the other document wants to define, and probably on a much longer time scale.
> 
> Grüße, Carsten
> 


From nobody Sat Feb 16 11:36:17 2019
Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76108130F5F for <json-canon@ietfa.amsl.com>; Sat, 16 Feb 2019 11:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qbZ4YBXBEGWW for <json-canon@ietfa.amsl.com>; Sat, 16 Feb 2019 11:36:13 -0800 (PST)
Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06B26130F5B for <json-canon@ietf.org>; Sat, 16 Feb 2019 11:36:13 -0800 (PST)
Received: by mail-wm1-x344.google.com with SMTP id n19so1157968wmi.1 for <json-canon@ietf.org>; Sat, 16 Feb 2019 11:36:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:from:to:cc:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=doEBcznv7rqGF11eC6x/4kUmoBmneEAhx4pvOn+ZB9o=; b=l9jO0pRchLPYECF38w0bP2avWGsnG3fJiAYDTt9NC+mICZo3CM36PQ8WfjKseKFPw5 P7r0iCvUE3uTprdZ3Z0esP5MVq0Mp93Ge5KMcuxMwcUulBEczz/MMlsy8WQVdRsVwjrz zzqPOrRWlbw7cXZ0M6HvOFSxPCfYLnlgULgBT+xsa3imejbO6sFfNtvVDT/EI0O1NB6E KjUuyv4yKMSYcmFuo4nZIRsyoGeBoVxV6OPkas+1lt3s4Br5zdv/J3Sh08WjsvOG97M/ 2GqRA6ML54YAyxJV8wcYX/+Wn6suEt/EO/97WOBCggyJklDqdE9ysLDxXfufHHbXSga+ LecA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:from:to:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=doEBcznv7rqGF11eC6x/4kUmoBmneEAhx4pvOn+ZB9o=; b=HhksgFdxREmn33yvJnOPlWQoDvUVtEDpJ24B14+WjsCLuUkwaiJz7XZn7v+Vma8oTF m6e39GOJZzQ/x2psV4XPp/8QxLgjbr3Z0LbrvQlk89EF2xGk6rwwjlsOpIek1BEU4zvt +gJTMocZ4cTb2Oyr5mnlGMZE/f6Jw0HAv8ea+OdWJc2idge6153nhA7nuSnSxY2zUQ/X 7z20LX8diVpOS2Ru4b82RK0kpp0Jmaf72m4sSNowV1jqRpyB6HFIatBoylu2nO/O7t2O wdKYEjn8EO1ydCBWeQrfeMQXEkikSiddLI8+Uxe0cCHogJjMHRjFDXrGalLiVBoyaMc5 MVVQ==
X-Gm-Message-State: AHQUAua7mWl2eCC/qK5T4IfD5eHAjxN/nnDifOvAMwJA5boIK3LDxgOY +qEAvUm7G/rTJ/s3XzWg1Nc=
X-Google-Smtp-Source: AHgI3IbpxtQb/ZfLsmcsY0jor+4FGxO9pEofyZjau1xVRH8+WCMg79sKfsLoDCwZl0X2egEK93o3Bw==
X-Received: by 2002:a1c:ce06:: with SMTP id e6mr5190961wmg.41.1550345771119; Sat, 16 Feb 2019 11:36:11 -0800 (PST)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id j15sm5173937wrt.1.2019.02.16.11.36.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 16 Feb 2019 11:36:09 -0800 (PST)
References: <155034272200.28542.17533645078274353201.idtracker@ietfa.amsl.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
To: "json-canon@ietf.org" <json-canon@ietf.org>
Cc: Bret Jordan <jordan.ietf@gmail.com>, Samuel Erdtman <samuel@erdtman.se>
X-Forwarded-Message-Id: <155034272200.28542.17533645078274353201.idtracker@ietfa.amsl.com>
Message-ID: <38131ee7-32d6-077f-cc62-7278ae6c9e17@gmail.com>
Date: Sat, 16 Feb 2019 20:36:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <155034272200.28542.17533645078274353201.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/UlzujXT-HMm46-PPNPdVr_nHSes>
Subject: [Json-canon] I-D: draft-rundgren-json-canonicalization-scheme-05
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Feb 2019 19:36:16 -0000

https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-05

Abstract:
    Cryptographic operations like hashing and signing requires that the
    original data does not change during serialization or parsing.  By
    applying the rules defined by the JSON Canonicalization Scheme (JCS),
    data provided in JSON [RFC8259] format can be exchanged "as is",
    while still being usable by secure cryptographic operations.  JCS
    achieves this by building on the strict serialization formats for
    JSON primitives defined by ECMAScript [ES6], constraining JSON data
    to the I-JSON [RFC7493] subset, and through a platform independent
    property sorting scheme.

    The intended audiences of this document are JSON tool vendors, as
    well as designers of JSON based cryptographic solutions.


This update primarily addresses the scope which was somewhat unclear in 04:
JSON level canonicalization (aka "Hashable" JSON) with cryptographic methods as consumers.

However, there are also updates on:
- Sorting rationale/options
- NaN/Infinity handling
- JCS Sample code
- IEEE-754 Sample Table
- Visualization of the EURO symbol in the I-D
- Other Canonical JSON efforts

Added reference to external application note I-D

Various language and style refinements.

Anders for the JCS team


From nobody Sun Feb 17 21:56:35 2019
Return-Path: <ietf@augustcellars.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90614130ECA for <json-canon@ietfa.amsl.com>; Sun, 17 Feb 2019 21:56:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PW90yxGxg5Jm for <json-canon@ietfa.amsl.com>; Sun, 17 Feb 2019 21:56:32 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7269130EC5 for <json-canon@ietf.org>; Sun, 17 Feb 2019 21:56:31 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 17 Feb 2019 21:56:25 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Bret Jordan' <jordan.ietf@gmail.com>
CC: 'Samuel Erdtman' <samuel@erdtman.se>, <json-canon@ietf.org>, 'Anders Rundgren' <anders.rundgren.net@gmail.com>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com> <7f7557ae-c86a-013a-6758-279034728be5@gmail.com> <F80FF7EB-B1A2-4337-8BC7-86E6C1AB725D@tzi.org> <354466BD-9D7C-463F-BBB4-E797267726A4@gmail.com>
In-Reply-To: <354466BD-9D7C-463F-BBB4-E797267726A4@gmail.com>
Date: Sun, 17 Feb 2019 21:56:24 -0800
Message-ID: <015901d4c74e$b01e9dc0$105bd940$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_015A_01D4C70B.A1FC6F30"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKM6YQQYC7r3DsdqZf77BCrHHAS2AJANXPsAZ8LhsgCYSVWcAKXHTnBAnkjN4mkGkS14A==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/mwYD68CvoSkBUd8INZLk4bvsxUI>
Subject: Re: [Json-canon] Dropping "Comparable" JSON
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2019 05:56:35 -0000

------=_NextPart_000_015A_01D4C70B.A1FC6F30
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

+1

=20

What I care about here is JSON =E2=80=93 there are a limited number of =
data types for JSON.  I don=E2=80=99t care about trying to shove other =
JavaScript types or C++ types into JSON strings.

=20

Jim

=20

=20

From: json-canon <json-canon-bounces@ietf.org> On Behalf Of Bret Jordan
Sent: Wednesday, February 13, 2019 1:22 PM
To: Carsten Bormann <cabo@tzi.org>
Cc: Samuel Erdtman <samuel@erdtman.se>; json-canon@ietf.org; Anders =
Rundgren <anders.rundgren.net@gmail.com>
Subject: Re: [Json-canon] Dropping "Comparable" JSON

=20

I am not sure I understand what you are proposing or what changes you =
would like.   I personally think that JCS should focus on a very limited =
and narrow set of use cases.  We should address how to represent JSON in =
a canonical form, period.  What people do with it beyond that is =
out-of-scope.

=20

Thanks,

Bret

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that =
can not be unscrambled is an egg."





On Feb 12, 2019, at 10:02 AM, Carsten Bormann <cabo@tzi.org =
<mailto:cabo@tzi.org> > wrote:

=20

On Feb 9, 2019, at 08:05, Anders Rundgren <anders.rundgren.net@gmail.com =
<mailto:anders.rundgren.net@gmail.com> > wrote:




I begin to wonder if "Comparable" JSON (in the draft named "true" =
canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call =
this.


Well, first of all, there is no =E2=80=9Cfeature=E2=80=9D here =E2=80=94 =
the current draft just points out that deterministic encoding =
(=E2=80=9Ccanonicalization=E2=80=9D) reaches up to the application using =
JSON wherever that does its own encoding work.

That is a fact that is good to know, but nothing is contributed to =
interoperability by this document.

To do so, one would need a way to describe elements of the application =
data model and constrain the application data encoding decisions made on =
the way to the JSON data model.  We don=E2=80=99t have a good way to do =
this at the moment (even if the document misleadingly mentions the =
=E2=80=9Cschema=E2=80=9D word).

Actually, the document about deterministic encoding of JSON (your =
=E2=80=9CHashable=E2=80=9D thing =E2=80=94 I still have no idea where =
these confused terms came from) could be stating this fact, if only as a =
matter of delineating what is *not* being defined in that document.

The document currently does not say how it was intended to be developed =
further.  As it stands, it is indeed of little use.  Collecting a set of =
preferred application-data-model to JSON-data-model encoding decisions, =
however, might be a useful undertaking, somewhat unrelated to the =
constraints on serializing the JSON data model that the other document =
wants to define, and probably on a much longer time scale.

Gr=C3=BC=C3=9Fe, Carsten

=20


------=_NextPart_000_015A_01D4C70B.A1FC6F30
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>+1<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>What I care =
about here is JSON =E2=80=93 there are a limited number of data types =
for JSON.=C2=A0 I don=E2=80=99t care about trying to shove other =
JavaScript types or C++ types into JSON strings.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b>From:</b> =
json-canon &lt;json-canon-bounces@ietf.org&gt; <b>On Behalf Of </b>Bret =
Jordan<br><b>Sent:</b> Wednesday, February 13, 2019 1:22 =
PM<br><b>To:</b> Carsten Bormann &lt;cabo@tzi.org&gt;<br><b>Cc:</b> =
Samuel Erdtman &lt;samuel@erdtman.se&gt;; json-canon@ietf.org; Anders =
Rundgren &lt;anders.rundgren.net@gmail.com&gt;<br><b>Subject:</b> Re: =
[Json-canon] Dropping &quot;Comparable&quot; =
JSON<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I am not =
sure I understand what you are proposing or what changes you would like. =
&nbsp; I personally think that JCS should focus on a very limited and =
narrow set of use cases. &nbsp;We should address how to represent JSON =
in a canonical form, period. &nbsp;What people do with it beyond that is =
out-of-scope.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Thanks,<o:p></o:p></p></div><div><div><div><div><p =
class=3DMsoNormal><span class=3Dapple-style-span><span =
style=3D'font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black'=
>Bret</span></span><span =
style=3D'font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black'=
><o:p></o:p></span></p></div><div><div><div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:8.5pt;font-family:"Verdana",sans-serif;color:#7C7C7C'>=
PGP Fingerprint:&nbsp;63B4 FC53 680A 6B7D 1447 &nbsp;F2C0 74F8 ACAE 7415 =
0050</span><span =
style=3D'font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black'=
><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:8.0pt;font-family:"Verdana",sans-serif;color:#7C7C7C'>=
&quot;Without cryptography vihv vivc ce xhrnrw, however, the only thing =
that can not be unscrambled is an egg.&quot;</span><span =
style=3D'font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black'=
><o:p></o:p></span></p></div></div></div></div></div></div></div><div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p =
class=3DMsoNormal>On Feb 12, 2019, at 10:02 AM, Carsten Bormann &lt;<a =
href=3D"mailto:cabo@tzi.org">cabo@tzi.org</a>&gt; =
wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Feb 9, 2019, at 08:05, Anders Rundgren &lt;<a =
href=3D"mailto:anders.rundgren.net@gmail.com">anders.rundgren.net@gmail.c=
om</a>&gt; wrote:<br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><br>I begin to wonder if &quot;Comparable&quot; JSON =
(in the draft named &quot;true&quot; canonicalization) shouldn't be a =
&quot;Feature at Risk&quot; as the W3C folks call =
this.<o:p></o:p></p></blockquote><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>Well, first of all, there is no =
=E2=80=9Cfeature=E2=80=9D here =E2=80=94 the current draft just points =
out that deterministic encoding (=E2=80=9Ccanonicalization=E2=80=9D) =
reaches up to the application using JSON wherever that does its own =
encoding work.<br><br>That is a fact that is good to know, but nothing =
is contributed to interoperability by this document.<br><br>To do so, =
one would need a way to describe elements of the application data model =
and constrain the application data encoding decisions made on the way to =
the JSON data model. &nbsp;We don=E2=80=99t have a good way to do this =
at the moment (even if the document misleadingly mentions the =
=E2=80=9Cschema=E2=80=9D word).<br><br>Actually, the document about =
deterministic encoding of JSON (your =E2=80=9CHashable=E2=80=9D thing =
=E2=80=94 I still have no idea where these confused terms came from) =
could be stating this fact, if only as a matter of delineating what is =
*not* being defined in that document.<br><br>The document currently does =
not say how it was intended to be developed further. &nbsp;As it stands, =
it is indeed of little use. &nbsp;Collecting a set of preferred =
application-data-model to JSON-data-model encoding decisions, however, =
might be a useful undertaking, somewhat unrelated to the constraints on =
serializing the JSON data model that the other document wants to define, =
and probably on a much longer time scale.<br><br>Gr=C3=BC=C3=9Fe, =
Carsten<o:p></o:p></p></div></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_015A_01D4C70B.A1FC6F30--


From nobody Mon Feb 18 10:11:14 2019
Return-Path: <jordan.ietf@gmail.com>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83F90130E6E for <json-canon@ietfa.amsl.com>; Mon, 18 Feb 2019 10:11:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yYc2R7Q0E4ug for <json-canon@ietfa.amsl.com>; Mon, 18 Feb 2019 10:11:10 -0800 (PST)
Received: from mail-yb1-xb41.google.com (mail-yb1-xb41.google.com [IPv6:2607:f8b0:4864:20::b41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40097129B88 for <json-canon@ietf.org>; Mon, 18 Feb 2019 10:11:10 -0800 (PST)
Received: by mail-yb1-xb41.google.com with SMTP id j62so7127477ybb.1 for <json-canon@ietf.org>; Mon, 18 Feb 2019 10:11:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yCvpHlle6V6RfCmQseaPyYUUDTlyHocrPBKry7OHLSs=; b=KNT/frw6FMAYj3LrxDCsAfIqbJQ0doXMW4d5q6rEslvTTrCjJbrsyLoJ3P0Zmcj1zl aNjIWv86jZAX8EfPrP9bCFNvnSGHrn5wCj+hOZOKLCkaTyMtRIe6XJzFYTW4QkwXuA1M 4qsnpncZM+4R6unVW5KBv0NbWrExPrJaMp+irybFx9cD/cEhUFTYY23f/yMtTRvKj+AY OOj5wxWsGj2p9GfgIdGM462vUKptTQZRrczG+H5LxKSCAHzpYMdxU6KFocn7jDTOdQLj gNRWsQKo6xLIPrqSlCsT6OFfF/2zRw2zQzu2P1TLLESUVpY1V+CJ1ITSpBqunLmTLZ9k 5hWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yCvpHlle6V6RfCmQseaPyYUUDTlyHocrPBKry7OHLSs=; b=WAyGaff5wCMGVc8PtMZCtSErjjQ44ovBE8Bh0zQRYhN/w2wEs4Gmo8UiI3Izv4UY2d yLDjvZKlhz0cIpnb6zS+7T+nxzmljYaOnlXBW4wPN9N/oh/zx64qJyP2Mnr2kXnrOunP QsHX9k7jVGrKz0SBSPApYlkzDYtq4vgvDdebuQYtG5F/v/Q6wMPw2Q7SbuJ1FqiCzFiI ZWFMUWre+PuPlXVhtdpmfXHVk41UWEx2acBpNExSxNbdKw7DDN+UeYyp0U0lIzr6dUFq R+m961q53AJQwi4fjZhopKzJeL4e8rdgC8vnjBqiUIo9H0uHJDNzCY/pO02RtpTR2AAH oMWg==
X-Gm-Message-State: AHQUAuZPSVdL6TRWNuBosqKC0Zy0L+nJ32kesYHZT2g+QyOWC0HWaZT7 z3oBnZgQHE+G2l0ElAjG6vs=
X-Google-Smtp-Source: AHgI3IaoLXnMNGjeteA7AAUkzukTzeYo79D7y4q8DYNIYtAjgoVT8TcgBZwQZxRkG1gvAFPFoh8yaw==
X-Received: by 2002:a5b:406:: with SMTP id m6mr16438512ybp.367.1550513469368;  Mon, 18 Feb 2019 10:11:09 -0800 (PST)
Received: from ?IPv6:2605:a601:a028:986:6db5:118c:d6cc:e636? ([2605:a601:a028:986:6db5:118c:d6cc:e636]) by smtp.gmail.com with ESMTPSA id h189sm5730782ywd.24.2019.02.18.10.11.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Feb 2019 10:11:08 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <257C335A-DFD6-4A23-ACB9-9F6985D127D1@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_ED468970-DA06-420D-A5B0-48C0EB5BB784"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 18 Feb 2019 11:11:05 -0700
In-Reply-To: <015901d4c74e$b01e9dc0$105bd940$@augustcellars.com>
Cc: Samuel Erdtman <samuel@erdtman.se>, json-canon@ietf.org, Anders Rundgren <anders.rundgren.net@gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
References: <00dc01d4b51c$618cdbc0$24a69340$@augustcellars.com> <f4b64343-e8db-57cf-152e-aeba44dc4863@gmail.com> <060401d4c035$d35d3e10$7a17ba30$@augustcellars.com> <7f7557ae-c86a-013a-6758-279034728be5@gmail.com> <F80FF7EB-B1A2-4337-8BC7-86E6C1AB725D@tzi.org> <354466BD-9D7C-463F-BBB4-E797267726A4@gmail.com> <015901d4c74e$b01e9dc0$105bd940$@augustcellars.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/8vKkun82CrgCf6a2JXuByXvo74I>
Subject: Re: [Json-canon] Dropping "Comparable" JSON
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2019 18:11:13 -0000

--Apple-Mail=_ED468970-DA06-420D-A5B0-48C0EB5BB784
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I fully agree Jim


Thanks,
Bret
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that =
can not be unscrambled is an egg."

> On Feb 17, 2019, at 10:56 PM, Jim Schaad <ietf@augustcellars.com> =
wrote:
>=20
> +1
> =20
> What I care about here is JSON =E2=80=93 there are a limited number of =
data types for JSON.  I don=E2=80=99t care about trying to shove other =
JavaScript types or C++ types into JSON strings.
> =20
> Jim
> =20
> =20
> From: json-canon <json-canon-bounces@ietf.org> On Behalf Of Bret =
Jordan
> Sent: Wednesday, February 13, 2019 1:22 PM
> To: Carsten Bormann <cabo@tzi.org>
> Cc: Samuel Erdtman <samuel@erdtman.se>; json-canon@ietf.org; Anders =
Rundgren <anders.rundgren.net@gmail.com>
> Subject: Re: [Json-canon] Dropping "Comparable" JSON
> =20
> I am not sure I understand what you are proposing or what changes you =
would like.   I personally think that JCS should focus on a very limited =
and narrow set of use cases.  We should address how to represent JSON in =
a canonical form, period.  What people do with it beyond that is =
out-of-scope.
> =20
> Thanks,
> Bret
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
> "Without cryptography vihv vivc ce xhrnrw, however, the only thing =
that can not be unscrambled is an egg."
>=20
>=20
>> On Feb 12, 2019, at 10:02 AM, Carsten Bormann <cabo@tzi.org =
<mailto:cabo@tzi.org>> wrote:
>> =20
>> On Feb 9, 2019, at 08:05, Anders Rundgren =
<anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> =
wrote:
>>=20
>>>=20
>>> I begin to wonder if "Comparable" JSON (in the draft named "true" =
canonicalization) shouldn't be a "Feature at Risk" as the W3C folks call =
this.
>>=20
>> Well, first of all, there is no =E2=80=9Cfeature=E2=80=9D here =E2=80=94=
 the current draft just points out that deterministic encoding =
(=E2=80=9Ccanonicalization=E2=80=9D) reaches up to the application using =
JSON wherever that does its own encoding work.
>>=20
>> That is a fact that is good to know, but nothing is contributed to =
interoperability by this document.
>>=20
>> To do so, one would need a way to describe elements of the =
application data model and constrain the application data encoding =
decisions made on the way to the JSON data model.  We don=E2=80=99t have =
a good way to do this at the moment (even if the document misleadingly =
mentions the =E2=80=9Cschema=E2=80=9D word).
>>=20
>> Actually, the document about deterministic encoding of JSON (your =
=E2=80=9CHashable=E2=80=9D thing =E2=80=94 I still have no idea where =
these confused terms came from) could be stating this fact, if only as a =
matter of delineating what is *not* being defined in that document.
>>=20
>> The document currently does not say how it was intended to be =
developed further.  As it stands, it is indeed of little use.  =
Collecting a set of preferred application-data-model to JSON-data-model =
encoding decisions, however, might be a useful undertaking, somewhat =
unrelated to the constraints on serializing the JSON data model that the =
other document wants to define, and probably on a much longer time =
scale.
>>=20
>> Gr=C3=BC=C3=9Fe, Carsten
>>=20


--Apple-Mail=_ED468970-DA06-420D-A5B0-48C0EB5BB784
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">I =
fully agree Jim<div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""><div class=3D"">
<div style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div class=3D"" style=3D"orphans: 2; widows: 2; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; line-height: normal; =
-webkit-text-decorations-in-effect: none;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; line-height: normal; border-spacing: 0px; =
-webkit-text-decorations-in-effect: none;">Thanks,</span></div><div =
class=3D"" style=3D"orphans: 2; widows: 2; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; line-height: normal; text-align: =
-webkit-auto; border-spacing: 0px; -webkit-text-decorations-in-effect: =
none;">Bret</span></div><div class=3D"" style=3D"orphans: 2; widows: =
2;"><span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; text-align: -webkit-auto; =
border-spacing: 0px;"><div class=3D"" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
text-align: -webkit-auto; border-spacing: 0px;"><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; text-align: -webkit-auto; =
border-spacing: 0px;"><div class=3D""><font color=3D"#7c7c7c" =
face=3D"Calibre, Verdana" class=3D"" style=3D"font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"" style=3D"font-size: 11px;">PGP =
Fingerprint:&nbsp;</span></font><span class=3D"" style=3D"text-align: =
-webkit-auto; font-size: 11px;"><font color=3D"#7c7c7c" face=3D"Calibre, =
Verdana" class=3D"">63B4 FC53 680A 6B7D 1447 &nbsp;F2C0 74F8 ACAE 7415 =
0050</font></span></div><div class=3D"" style=3D"font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal; -webkit-text-decorations-in-effect: none;"><span =
class=3D"" style=3D"color: rgb(124, 124, 124); font-size: 8pt; =
font-family: Calibre, Verdana; text-align: -webkit-auto;">"Without =
cryptography vihv vivc ce xhrnrw, however, the only thing that can not =
be unscrambled is an =
egg."</span></div></span></div></span></div></span></div></span></span></d=
iv></div>
</div>
<div style=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Feb 17, 2019, at 10:56 PM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
class=3D"">ietf@augustcellars.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">+1<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">What I =
care about here is JSON =E2=80=93 there are a limited number of data =
types for JSON.&nbsp; I don=E2=80=99t care about trying to shove other =
JavaScript types or C++ types into JSON strings.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Jim<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"border-style: none none none =
solid; border-left-width: 1.5pt; border-left-color: blue; padding: 0in =
0in 0in 4pt;" class=3D""><div class=3D""><div style=3D"border-style: =
solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, =
225); padding: 3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><b class=3D"">From:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>json-canon &lt;<a =
href=3D"mailto:json-canon-bounces@ietf.org" =
class=3D"">json-canon-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Bret Jordan<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Wednesday, February 13, =
2019 1:22 PM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Carsten Bormann &lt;<a =
href=3D"mailto:cabo@tzi.org" class=3D"">cabo@tzi.org</a>&gt;<br =
class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Samuel Erdtman &lt;<a =
href=3D"mailto:samuel@erdtman.se" class=3D"">samuel@erdtman.se</a>&gt;; =
<a href=3D"mailto:json-canon@ietf.org" class=3D"">json-canon@ietf.org</a>;=
 Anders Rundgren &lt;<a href=3D"mailto:anders.rundgren.net@gmail.com" =
class=3D"">anders.rundgren.net@gmail.com</a>&gt;<br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Json-canon] Dropping =
"Comparable" JSON<o:p class=3D""></o:p></div></div></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">I am not sure I understand what you are =
proposing or what changes you would like. &nbsp; I personally think that =
JCS should focus on a very limited and narrow set of use cases. &nbsp;We =
should address how to represent JSON in a canonical form, period. =
&nbsp;What people do with it beyond that is out-of-scope.<o:p =
class=3D""></o:p></div><div class=3D""><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Thanks,<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
class=3D"apple-style-span"><span style=3D"font-size: 10.5pt; =
font-family: Helvetica, sans-serif;" class=3D"">Bret</span></span><span =
style=3D"font-size: 10.5pt; font-family: Helvetica, sans-serif;" =
class=3D""><o:p class=3D""></o:p></span></div></div><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 8.5pt; =
font-family: Verdana, sans-serif; color: rgb(124, 124, 124);" =
class=3D"">PGP Fingerprint:&nbsp;63B4 FC53 680A 6B7D 1447 &nbsp;F2C0 =
74F8 ACAE 7415 0050</span><span style=3D"font-size: 10.5pt; font-family: =
Helvetica, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 8pt; font-family: Verdana, =
sans-serif; color: rgb(124, 124, 124);" class=3D"">"Without cryptography =
vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled =
is an egg."</span><span style=3D"font-size: 10.5pt; font-family: =
Helvetica, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div></div></div></div></div></div></div></div><d=
iv class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></div><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D"" type=3D"cite"><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">On Feb 12, 2019, at 10:02 AM, Carsten =
Bormann &lt;<a href=3D"mailto:cabo@tzi.org" style=3D"color: purple; =
text-decoration: underline;" class=3D"">cabo@tzi.org</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">On Feb 9, 2019, at 08:05, Anders =
Rundgren &lt;<a href=3D"mailto:anders.rundgren.net@gmail.com" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">anders.rundgren.net@gmail.com</a>&gt; wrote:<br class=3D""><br =
class=3D""><o:p class=3D""></o:p></div><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D"" type=3D"cite"><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><br class=3D"">I begin to wonder if "Comparable" JSON (in the =
draft named "true" canonicalization) shouldn't be a "Feature at Risk" as =
the W3C folks call this.<o:p class=3D""></o:p></div></blockquote><p =
class=3D"MsoNormal" style=3D"margin: 0in 0in 12pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><br class=3D"">Well, first of all, =
there is no =E2=80=9Cfeature=E2=80=9D here =E2=80=94 the current draft =
just points out that deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D) reaches up to the application using JSON wherever that does its own =
encoding work.<br class=3D""><br class=3D"">That is a fact that is good =
to know, but nothing is contributed to interoperability by this =
document.<br class=3D""><br class=3D"">To do so, one would need a way to =
describe elements of the application data model and constrain the =
application data encoding decisions made on the way to the JSON data =
model. &nbsp;We don=E2=80=99t have a good way to do this at the moment =
(even if the document misleadingly mentions the =E2=80=9Cschema=E2=80=9D =
word).<br class=3D""><br class=3D"">Actually, the document about =
deterministic encoding of JSON (your =E2=80=9CHashable=E2=80=9D thing =
=E2=80=94 I still have no idea where these confused terms came from) =
could be stating this fact, if only as a matter of delineating what is =
*not* being defined in that document.<br class=3D""><br class=3D"">The =
document currently does not say how it was intended to be developed =
further. &nbsp;As it stands, it is indeed of little use. =
&nbsp;Collecting a set of preferred application-data-model to =
JSON-data-model encoding decisions, however, might be a useful =
undertaking, somewhat unrelated to the constraints on serializing the =
JSON data model that the other document wants to define, and probably on =
a much longer time scale.<br class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe, =
Carsten</p></div></div></blockquote></div></div></div></div></div></blockq=
uote></div><br class=3D""></div></body></html>=

--Apple-Mail=_ED468970-DA06-420D-A5B0-48C0EB5BB784--

