
From rjs@mitre.org  Thu Jan 17 18:50:09 2019
Return-Path: <rjs@mitre.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 869CD13108B for <json-canon@ietfa.amsl.com>; Thu, 17 Jan 2019 18:50:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.442
X-Spam-Level: 
X-Spam-Status: No, score=-4.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mitre.onmicrosoft.com header.b=pVcJxnY8; dkim=pass (1024-bit key) header.d=mitre.org header.b=HUkNCy6q
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 QD_Uhb8rIL1f for <json-canon@ietfa.amsl.com>; Thu, 17 Jan 2019 18:50:07 -0800 (PST)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66BEE131088 for <json-canon@ietf.org>; Thu, 17 Jan 2019 18:50:04 -0800 (PST)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 78FD76C005F for <json-canon@ietf.org>; Thu, 17 Jan 2019 21:50:03 -0500 (EST)
Received: from imshyb02.MITRE.ORG (unknown [129.83.29.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtpvmsrv1.mitre.org (Postfix) with ESMTPS id 64F146C0046 for <json-canon@ietf.org>; Thu, 17 Jan 2019 21:50:03 -0500 (EST)
Received: from imshyb02.MITRE.ORG (129.83.29.3) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 17 Jan 2019 21:50:02 -0500
Received: from GCC01-CY1-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 17 Jan 2019 21:50:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com;  s=selector1-mitre-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ICt7jyUQXbysadLUb+qMsy6gho1cS/aB9mrbXOoO8mI=; b=pVcJxnY8sAeTk8JCkewdGQ2/SDi90kRc/t26uhcPj0ArlqxS2kekFlSDujWwt8W7dRFAuOpzgtFkCNBA91nY7EZNzwGhe4PP/PLTGG+LRvpM3TBImg9+2cv1FmSldtSHlnq//hoX2EzAkwzeK6KR5nXIXZlxf0fZZsh0jnW7H0A=
Received: from BN6PR09MB1524.namprd09.prod.outlook.com (10.173.204.8) by BN6PR09MB1524.namprd09.prod.outlook.com (10.173.204.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1537.26; Fri, 18 Jan 2019 02:50:00 +0000
Received: from BN6PR09MB1524.namprd09.prod.outlook.com ([fe80::71:14d6:1ad9:1e28]) by BN6PR09MB1524.namprd09.prod.outlook.com ([fe80::71:14d6:1ad9:1e28%4]) with mapi id 15.20.1537.018; Fri, 18 Jan 2019 02:50:00 +0000
From: "Struse, Richard J." <rjs@mitre.org>
To: "json-canon@ietf.org" <json-canon@ietf.org>
Thread-Topic: Support for a WG
Thread-Index: AQHUrtiBAcQCRDGu4UC3Ij3FNjzyvA==
Date: Fri, 18 Jan 2019 02:50:00 +0000
Message-ID: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rjs@mitre.org; 
x-originating-ip: [192.80.55.89]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR09MB1524; 6:ZFiYKd7z9eEf+hwT9q6KjIym/47F0ymaVapvDqxjkuOR23eYL+JNN4U+iGMKodSgPcf3Vgeo11u6GR20jZ0vifTV9sHbTniFDV0W9bmOKUajMWVcb13ZH2NEQ5UKCnNBCaXrr0/36+cPE4qjKGnPolV8C5bbZ1qpmGNqWiVVO3DL+PBNaF+lcD8TwReB/vdTHZkiyuvT/E++ozq1bw8CzuHA8lUWmu4bpVm++lTY4876KBvmEWGswoCNcNkg57aNavtQYeF3LuxpWLiDrmubQcRWVYgp867Ztsg7JdS4bna5qPxy8XhJeUYsFYwfhjzr1sXa4G0yVNAEp9ULcvk07XVb8s4RHfl5nF5dNq/e2G5k8EXRSnVxYXKK+cJ7LdCAL88hRhgrtoYG4U/w7K5KCjc9GE6s+xN9pMShWmtFWmaJN43yi0Bv637Y/dVy+zoG/5jNmDM+9FRAKS7zKMP3gQ==; 5:/onLfQvY1TVQ4q5p7O9cqiFI5aDXnkjldGw/NLUNfVT+n6IelpFzMpgl6HFctdPzoWibUqUCcTYDm8XkPgzyUfvAg8oXZDGBrAhTylg7w/oYaZ0K8oWkfpkX/PvdiSXqLcLfinF/24sHb9iz//D11YMLU4ljFiT83GHzTw8KO+ipEuY5YuCAFNtnKNZJw3nPI8yL3QcP/cVMD3uJ+E3HEQ==; 7:cqTvmseLsd2RC9h9CcLSm4rWu8nV7hSfbPw00S5pvEeUTjRiRPLn13pm5F4eerAV2r8quHZSZrNxhzBu/4+9VS0l9DxtBvPd9QByybcb86zcjXa3bvXyPsZNSgpew+gpXPZ67QQuJKJd+RbEMnx+KQ==
x-ms-office365-filtering-correlation-id: 35267d50-ed2e-4643-4a65-08d67cefa3f7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BN6PR09MB1524; 
x-ms-traffictypediagnostic: BN6PR09MB1524:
x-microsoft-antispam-prvs: <BN6PR09MB1524861BBB9E02CF0365AD36A29C0@BN6PR09MB1524.namprd09.prod.outlook.com>
x-forefront-prvs: 0921D55E4F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(136003)(396003)(346002)(376002)(189003)(199004)(38284003)(2906002)(33656002)(54896002)(6512007)(71200400001)(3480700005)(68736007)(9686003)(6486002)(25786009)(6306002)(53936002)(486006)(86362001)(2351001)(106356001)(105586002)(36756003)(82746002)(97736004)(6436002)(5640700003)(256004)(316002)(7736002)(478600001)(476003)(2501003)(5660300001)(83716004)(71190400001)(81156014)(8676002)(81166006)(66066001)(6916009)(14454004)(102836004)(6506007)(99286004)(6116002)(3846002)(33896004)(8936002)(186003)(26005); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR09MB1524; H:BN6PR09MB1524.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ZXibPgB1G3AiquD3vplU41qoBoG7RHxLclm+HqWlXzxJ5xvDkU01TP/3M1G3+THyYyPvcsMS83EKKlym6sBzgqyATEy5t7AGAI73BzyTVpXxAwhgINBuLEa1Bruy1z2kq/y+/BmBmDKrvSt9qhZLwotsYAn2RVIh79EDAEkx1jXvKh8A3hRBQMsqz8aucQ9HEz+k2hJr6CUl2u6GUYXF7qWGRXLjNLmQN6PjfHPa6KZThjcr8xg1SdNv2hOGxr6ZPhhBlMTItijXkFxbf9BtndlqVyjapS5sI5AhwAHs8C2d730JPSStTyj/mazoR/qJTCByoHTUgZb/DnAuExXhdGxBJ1ZQ189bD7PkCltpZUGMF01atUzYeJdexuUkPb7im2nEAO8Aw/C+tZyvCp4ilvUsIbZIcFcqAs8bSj5Keek=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_38C844593D2E4E78BF48FE277388E33Acontosocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 35267d50-ed2e-4643-4a65-08d67cefa3f7
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jan 2019 02:50:00.7632 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR09MB1524
X-OriginatorOrg: mitre.org
X-MITRE: 8GQsMWxq66rxk57w
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.org; h=from:to:subject:date:message-id:content-type:mime-version; s=selector1; bh=ICt7jyUQXbysadLUb+qMsy6gho1cS/aB9mrbXOoO8mI=; b=HUkNCy6q83O1+Yc7j8tuj3bEzWuWuFI0rkzHEr+LIuiAVoDU+/jHDNizwltDn25OjGmvCl/rQezuKKeZGH1NUak2Tssw1eWjukLtVf8NMAG/ichMlwQY3GNX/LrrsDBBB63U9jXzfmHNQmcyrQFZ6JrnFGw1PW8hHwoSCBPTwCs=
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/2t901Q61IvJa6NXofufOPR8gKPo>
Subject: [Json-canon] Support for a WG
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: Fri, 18 Jan 2019 02:51:32 -0000

--_000_38C844593D2E4E78BF48FE277388E33Acontosocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QSBzdGFuZGFyZGl6ZWQgZGV0ZXJtaW5pc3RpYyBjYW5vbmljYWxpemF0aW9uIG9mIEpTT04gZGF0
YSBzdHJlYW1zIGlzIGVzc2VudGlhbCBhbmQgYXMgc3VjaCBJIHN1cHBvcnQgdGhlIGZvcm1hdGlv
biBvZiBhIFdHIHRvIHRhY2tsZSB0aGlzIHByb2JsZW0uDQoNClRoYW5rIHlvdS4NCg0KUmljaGFy
ZCBKLiBTdHJ1c2UNCg0KQ28tY2hhaXIsIE9BU0lTIEN5YmVyIFRocmVhdCBJbnRlbGxpZ2VuY2Ug
VGVjaG5pY2FsIENvbW1pdHRlZQ0KQ2hpZWYgU3RyYXRlZ2lzdCBmb3IgQ3liZXIgVGhyZWF0IElu
dGVsbGlnZW5jZQ0KVGhlIE1JVFJFIENvcnBvcmF0aW9uDQorMS03MDMtOTgzLTcwNDkgKG9mZmlj
ZSkNCisxLTcwMy0zNDItODM2OCAobW9iaWxlKQ0K

--_000_38C844593D2E4E78BF48FE277388E33Acontosocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <01AE443831D646438A8DCC6B83123ECD@namprd09.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpz
cGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1z
dHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4w
aW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0
aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMw
NTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+QSBzdGFuZGFy
ZGl6ZWQgZGV0ZXJtaW5pc3RpYyBjYW5vbmljYWxpemF0aW9uIG9mIEpTT04gZGF0YSBzdHJlYW1z
IGlzIGVzc2VudGlhbCBhbmQgYXMgc3VjaCBJIHN1cHBvcnQgdGhlIGZvcm1hdGlvbiBvZiBhIFdH
IHRvIHRhY2tsZSB0aGlzIHByb2JsZW0uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0Ij5UaGFuayB5b3UuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdCI+UmljaGFyZCBKLiBTdHJ1c2U8bzpwPjwvbzpwPjwvc3Bhbj48L2I+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvYj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+Q28tY2hhaXIsIE9BU0lTIEN5YmVyIFRo
cmVhdCBJbnRlbGxpZ2VuY2UgVGVjaG5pY2FsIENvbW1pdHRlZTxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5D
aGllZiBTdHJhdGVnaXN0IGZvciBDeWJlciBUaHJlYXQgSW50ZWxsaWdlbmNlPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQiPlRoZSBNSVRSRSBDb3Jwb3JhdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij4mIzQzOzEtNzAz
LTk4My03MDQ5IChvZmZpY2UpIDxvOnA+DQo8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPiYjNDM7MS03MDMtMzQyLTgz
NjggKG1vYmlsZSk8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5
Pg0KPC9odG1sPg0K

--_000_38C844593D2E4E78BF48FE277388E33Acontosocom_--


From nobody Thu Jan 17 22:46:42 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 98BD113112D for <json-canon@ietfa.amsl.com>; Thu, 17 Jan 2019 22:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 vBhHBZDIepg7 for <json-canon@ietfa.amsl.com>; Thu, 17 Jan 2019 22:46:38 -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 412E5126BED for <json-canon@ietf.org>; Thu, 17 Jan 2019 22:46:38 -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 x0I6kTQC006364; Fri, 18 Jan 2019 07:46:34 +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 43gs1071ylz1Br6; Fri, 18 Jan 2019 07:46:28 +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: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com>
Date: Fri, 18 Jan 2019 07:46:28 +0100
Cc: "json-canon@ietf.org" <json-canon@ietf.org>
X-Mao-Original-Outgoing-Id: 569486785.957178-a202fac2647b16ec58c88acb6132a65e
Content-Transfer-Encoding: quoted-printable
Message-Id: <34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com>
To: "Struse, Richard J." <rjs@mitre.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/qFC_6rViFq1ZjY-Zw5KGYZ3RzCk>
Subject: Re: [Json-canon] Support for a WG
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: Fri, 18 Jan 2019 06:46:41 -0000

On Jan 18, 2019, at 03:50, Struse, Richard J. <rjs@mitre.org> wrote:
>=20
> A standardized deterministic canonicalization of JSON data streams is =
essential

For what?

I think we would all benefit if you could explain your use case.

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


From nobody Fri Jan 18 09:40:25 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 93220131259 for <json-canon@ietfa.amsl.com>; Fri, 18 Jan 2019 09:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=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 NorCn4OoQdkH for <json-canon@ietfa.amsl.com>; Fri, 18 Jan 2019 09:40:20 -0800 (PST)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 9BF97131255 for <json-canon@ietf.org>; Fri, 18 Jan 2019 09:40:20 -0800 (PST)
Received: by mail-qt1-x82f.google.com with SMTP id d19so16051132qtq.9 for <json-canon@ietf.org>; Fri, 18 Jan 2019 09:40:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=y7smAYS3ginFXQ8bmd6GRxuQmv3gZkHh9a5p4RcBQRU=; b=U0uBi6eNJ3CHlFP1qcYCAJfYP2+E+3G42QomIh32jMFaiqdWIFKcutYxr2WBOaLeQw Yk4RgFk1luGuDolyMX/gNWgNd25Y5B6iD1NEYw+psFGwXlRgRq++uFTO3UXFeRu7tx0L HIJnRkR6r9YMAwfLZmt7vOoTI/MDv3gm9ETHphZybkfnG6lz6P3SuVLRw87XYdC+CVO0 xdMz8GAde4UODHkS8DJV6ag5ozRYJZqx91LXjg9Ea2vuKfaFggtFud1LtoyxxvcglJZO QJfXGqnp8VSm1ZXmDpDBwY8J75kA5gQbHZT458wpF33BpdYNLFJvnTnBcxU5BBm4i1s0 qIbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=y7smAYS3ginFXQ8bmd6GRxuQmv3gZkHh9a5p4RcBQRU=; b=FGu43+196Q0XXwISS5fu9NHgvvaB/pHNPrAovpYnPaRH5h/oSffWZv1EffusWIpZrr //1TSYBCS8+xcSPAyFVhnEl0uDdpxe/zAnkarBmFlefuP32L8YfUK65SNTjhAv8kh9K5 45HKKX2lEfocpjTv5OMZHdcX2MlK9riREDCLZqt1881U26MPy49UBGGZ+E8aLjsOCZtg PXSO0KcsNCAhVYJ6Lrv0wEduGsFN+SzxJu2+0OFdnu3NoN5KzQbfqnhkHIZ+IaqsbuIc QQV2QRkj4HHh7J7bpTwXBDQrUwr31FQINs44qkYSm5zoA83ZBQugm/L4q2gEQ5K9210t EW0Q==
X-Gm-Message-State: AJcUukczwuasRz0+zZ2gBkmQqJn+kT1iYkI8CjDpOZMUGCCRsDrrnO82 9yGvx0WGfSfLPtK6IKKd6JCmm8Bj
X-Google-Smtp-Source: ALg8bN75ktcCD0udmZZGMt407DmqpE6jRQkN3AkRxYc3834Y7sNO6ArREl24Tifir9XZwJhTW+utjw==
X-Received: by 2002:a0c:9961:: with SMTP id i30mr16456317qvd.229.1547833219520;  Fri, 18 Jan 2019 09:40:19 -0800 (PST)
Received: from [100.64.51.130] (25.sub-174-201-8.myvzw.com. [174.201.8.25]) by smtp.gmail.com with ESMTPSA id l30sm48758804qte.44.2019.01.18.09.40.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Jan 2019 09:40:18 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-11C99BC3-1511-4AAD-BF88-3EE96ABEC25C
Mime-Version: 1.0 (1.0)
From: Bret Jordan <jordan.ietf@gmail.com>
X-Mailer: iPhone Mail (16C101)
In-Reply-To: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com>
Date: Fri, 18 Jan 2019 18:40:15 +0100
Cc: "json-canon@ietf.org" <json-canon@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <9FDFCC19-9210-4681-8726-EE8AE57C23B7@gmail.com>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com>
To: "Struse, Richard J." <rjs@mitre.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/INfgedLliyjuntLIPVtNv9G2KCg>
Subject: Re: [Json-canon] Support for a WG
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: Fri, 18 Jan 2019 17:40:24 -0000

--Apple-Mail-11C99BC3-1511-4AAD-BF88-3EE96ABEC25C
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I fully support the creation of a WG for JSON canonicalization as well. =20

Bret=20

Sent from my Commodore 128D

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

> On Jan 18, 2019, at 3:50 AM, Struse, Richard J. <rjs@mitre.org> wrote:
>=20
> A standardized deterministic canonicalization of JSON data streams is esse=
ntial and as such I support the formation of a WG to tackle this problem.
> =20
> Thank you.
> =20
> Richard J. Struse
> =20
> Co-chair, OASIS Cyber Threat Intelligence Technical Committee
> Chief Strategist for Cyber Threat Intelligence
> The MITRE Corporation
> +1-703-983-7049 (office)
> +1-703-342-8368 (mobile)
> --=20
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon

--Apple-Mail-11C99BC3-1511-4AAD-BF88-3EE96ABEC25C
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">I fully support the creation of a WG for JS=
ON canonicalization as well. &nbsp;<div><br></div><div>Bret&nbsp;<br><br><di=
v id=3D"AppleMailSignature" dir=3D"ltr"><span style=3D"background-color: rgb=
a(255, 255, 255, 0);">Sent from my Commodore 128D</span><div><span style=3D"=
background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style=
=3D"background-color: rgba(255, 255, 255, 0);"><font class=3D"" style=3D"fon=
t-variant-ligatures: normal; font-variant-position: normal; font-variant-num=
eric: normal; font-variant-alternates: normal; font-variant-east-asian: norm=
al; line-height: normal;">PGP Fingerprint:&nbsp;</font><span class=3D"" styl=
e=3D"text-align: -webkit-auto;"><font class=3D"">63B4 FC53 680A 6B7D 1447 &n=
bsp;F2C0 74F8 ACAE 7415 0050</font></span></span></div></div><div dir=3D"ltr=
"><br>On Jan 18, 2019, at 3:50 AM, Struse, Richard J. &lt;<a href=3D"mailto:=
rjs@mitre.org">rjs@mitre.org</a>&gt; wrote:<br><br></div><blockquote type=3D=
"cite"><div dir=3D"ltr">

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>


<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">A standardized deter=
ministic canonicalization of JSON data streams is essential and as such I su=
pport the formation of a WG to tackle this problem.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p>&nbsp;</o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Thank you.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p>&nbsp;</o:p></s=
pan></p>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt">Richard J. Struse=
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt"><o:p>&nbsp;</o:p>=
</span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Co-chair, OASIS Cybe=
r Threat Intelligence Technical Committee<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Chief Strategist for=
 Cyber Threat Intelligence<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">The MITRE Corporatio=
n<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">+1-703-983-7049 (off=
ice) <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">+1-703-342-8368 (mob=
ile)</span><o:p></o:p></p>
</div>
</div>


</div></blockquote><blockquote type=3D"cite"><div dir=3D"ltr"><span>-- </spa=
n><br><span>json-canon mailing list</span><br><span><a href=3D"mailto:json-c=
anon@ietf.org">json-canon@ietf.org</a></span><br><span><a href=3D"https://ww=
w.ietf.org/mailman/listinfo/json-canon">https://www.ietf.org/mailman/listinf=
o/json-canon</a></span><br></div></blockquote></div></body></html>=

--Apple-Mail-11C99BC3-1511-4AAD-BF88-3EE96ABEC25C--


From nobody Mon Jan 21 13:18:16 2019
Return-Path: <samuel@erdtman.se>
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 2F1AF12D4E7 for <json-canon@ietfa.amsl.com>; Mon, 21 Jan 2019 13:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=erdtman-se.20150623.gappssmtp.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 MeobecIyTeo2 for <json-canon@ietfa.amsl.com>; Mon, 21 Jan 2019 13:18:11 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 302C2128CF2 for <json-canon@ietf.org>; Mon, 21 Jan 2019 13:18:10 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id u6so10655988pfh.11 for <json-canon@ietf.org>; Mon, 21 Jan 2019 13:18:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erdtman-se.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=E5hlFr4/z++f8D6446+hyfOAZxqb/UFEQ6YUf1iADKE=; b=MenNnKhthV6sfRyKalHZzEcPgPgesIccsSYBr7/yErU56e4mpCB7j56mrJAHROBzP3 xv+XxmNU60PNy7SmfsGQ5VuvanKgwvF3B4aReR+vSELMOeMAmkNINJkOVitMhzw3rnrN EneGKruJqCKGb+MhGb3OXjnm/ol7IiEgkHgDufAcrYodjYB1kEYnYBrekoObbPwvocrl QQ4FcW7hAZ0Rn2LK+k03aN9C8wHfgu2SpIMzajZTux3Xl2sWcQZwlAhptwiRMuNVf1IT S8yevU32HESWPJPUOufesCvmdqqU2Wgc6tA72dWAFn//CogD2ZMfDNiW9PStKxirNPcS ACbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E5hlFr4/z++f8D6446+hyfOAZxqb/UFEQ6YUf1iADKE=; b=MHV9Y4HU3CX0y624GyCec0O5PD6VcjA1X4ZZJAsWFhWLfLxo+fdUVdU57haZ2zd2KO SqQtGZV3tIl+Dq6PqdB7y52srn7++shxIne5c/D+VfOtBt7XLaJcOLHLl4sl7OKEh/XU 3bCzFVhLujwe9pZr32hVnsLoUdhZ8IArR6CTtxysxPGIMYWlafso9QpME+sDe9J+O6AO sABxUKcx/kybq/e+9JOJ6w22y3OVnjI3pKFSqMwau0cpgTrzrpo2y2C6ksYN0f4y94Ox U10WWUPeOes8y1zjSGLdR/+GbYeK104P38itfCC3vVcrfvftnM3i9HnCDDAX4ui/ZrH1 55Fw==
X-Gm-Message-State: AJcUukfzIYO+O4l9SmYU1pe53p9hHR2IDqH5qopE2//+rr3E66drm8y0 YjPZyeyztJzCPuEEXkiheOyNRM2IorHlYj+IqPTbFg==
X-Google-Smtp-Source: ALg8bN6Nts8CBdz/5rT2GUkEbbf5SAmRQEJ1iD8jZ8b4XoTRoM4+ewhbQXyo7Ry2ph0FRKTWItrxGGCzzluaTBCSVqU=
X-Received: by 2002:a62:444b:: with SMTP id r72mr31601777pfa.184.1548105490102;  Mon, 21 Jan 2019 13:18:10 -0800 (PST)
MIME-Version: 1.0
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <9FDFCC19-9210-4681-8726-EE8AE57C23B7@gmail.com>
In-Reply-To: <9FDFCC19-9210-4681-8726-EE8AE57C23B7@gmail.com>
From: Samuel Erdtman <samuel@erdtman.se>
Date: Mon, 21 Jan 2019 22:17:57 +0100
Message-ID: <CAF2hCbb1Yg8cb56_y-6yRHvE1g1=q4hpF837Ob78L4jDXV_32A@mail.gmail.com>
To: Bret Jordan <jordan.ietf@gmail.com>
Cc: "Struse, Richard J." <rjs@mitre.org>, "json-canon@ietf.org" <json-canon@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d00f38057ffe65da"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/Xfg6KwmJUzwGvtpypHB5EykzUfQ>
Subject: Re: [Json-canon] Support for a WG
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, 21 Jan 2019 21:18:14 -0000

--000000000000d00f38057ffe65da
Content-Type: text/plain; charset="UTF-8"

I too support the creation of a WG for JSON canonicalization.

To me the obvious use case is signing of cleartext JSON I know that is
controversial for some reason. To me it is just another tool to use. I know
the argument for not wanting to base64url encode a json-payload has not hit
home everywhere most often since it is "want" (and not need). To me there
is never (or seldom) an absolute need for a new schema e.g. one could still
do ASN1 signatures or XMLDigSig but many preferable to do a JOSE signature
and I think that to some it will be preferable to do a cleartext JSON
signature and for those JSON canonicalization is needed.

Cheers
//Samuel

On Fri, Jan 18, 2019 at 6:40 PM Bret Jordan <jordan.ietf@gmail.com> wrote:

> I fully support the creation of a WG for JSON canonicalization as well.
>
> Bret
>
> Sent from my Commodore 128D
>
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
>
> On Jan 18, 2019, at 3:50 AM, Struse, Richard J. <rjs@mitre.org> wrote:
>
> A standardized deterministic canonicalization of JSON data streams is
> essential and as such I support the formation of a WG to tackle this
> problem.
>
>
>
> Thank you.
>
>
>
> *Richard J. Struse*
>
>
>
> Co-chair, OASIS Cyber Threat Intelligence Technical Committee
>
> Chief Strategist for Cyber Threat Intelligence
>
> The MITRE Corporation
>
> +1-703-983-7049 (office)
>
> +1-703-342-8368 (mobile)
>
> --
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon
>
> --
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon
>

--000000000000d00f38057ffe65da
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I too support the creation of a WG for JSON canonical=
ization.</div><div><br></div><div>To me the obvious use case is signing of =
cleartext JSON I know that is controversial for some reason. To me it is ju=
st another tool to use. I know the argument for not wanting to base64url en=
code a json-payload has not hit home everywhere most often since it is &quo=
t;want&quot; (and not need). To me there is never (or seldom) an absolute n=
eed for a new schema e.g. one could still do ASN1 signatures or XMLDigSig b=
ut many preferable to do a JOSE signature and I think that to some it will =
be preferable to do a cleartext JSON signature and for those JSON canonical=
ization is needed.</div><div><br></div><div>Cheers</div><div>//Samuel<br></=
div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Fri, Jan 18, 2019 at 6:40 PM Bret Jordan &lt;<a href=3D"mailto:jorda=
n.ietf@gmail.com">jordan.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">I fully support th=
e creation of a WG for JSON canonicalization as well. =C2=A0<div><br></div>=
<div>Bret=C2=A0<br><br><div id=3D"gmail-m_-2719845810746159995AppleMailSign=
ature" dir=3D"ltr"><span style=3D"background-color:rgba(255,255,255,0)">Sen=
t from my Commodore 128D</span><div><span style=3D"background-color:rgba(25=
5,255,255,0)"><br></span></div><div><span style=3D"background-color:rgba(25=
5,255,255,0)"><font style=3D"font-variant-ligatures:normal;font-variant-num=
eric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;l=
ine-height:normal">PGP Fingerprint:=C2=A0</font><span><font>63B4 FC53 680A =
6B7D 1447 =C2=A0F2C0 74F8 ACAE 7415 0050</font></span></span></div></div><d=
iv dir=3D"ltr"><br>On Jan 18, 2019, at 3:50 AM, Struse, Richard J. &lt;<a h=
ref=3D"mailto:rjs@mitre.org" target=3D"_blank">rjs@mitre.org</a>&gt; wrote:=
<br><br></div><blockquote type=3D"cite"><div dir=3D"ltr">






<div class=3D"gmail-m_-2719845810746159995WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt">A standardized determ=
inistic canonicalization of JSON data streams is essential and as such I su=
pport the formation of a WG to tackle this problem.<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt">Thank you.<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11pt">Richard J. Struse<=
u></u><u></u></span></b></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11pt"><u></u>=C2=A0<u></=
u></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt">Co-chair, OASIS Cyber=
 Threat Intelligence Technical Committee<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt">Chief Strategist for =
Cyber Threat Intelligence<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt">The MITRE Corporation=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt">+1-703-983-7049 (offi=
ce) <u></u>
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt">+1-703-342-8368 (mobi=
le)</span><u></u><u></u></p>
</div>
</div>


</div></blockquote><blockquote type=3D"cite"><div dir=3D"ltr"><span>-- </sp=
an><br><span>json-canon mailing list</span><br><span><a href=3D"mailto:json=
-canon@ietf.org" target=3D"_blank">json-canon@ietf.org</a></span><br><span>=
<a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/json-canon</a></span><br></div></=
blockquote></div></div>-- <br>
json-canon mailing list<br>
<a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-canon@ietf.or=
g</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/json-canon</a>=
<br>
</blockquote></div>

--000000000000d00f38057ffe65da--


From nobody Tue Jan 22 01:29: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 C9611130E9F for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 01:29:57 -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 kB4WAn-k3iUE for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 01:29:56 -0800 (PST)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 23004130E9D for <json-canon@ietf.org>; Tue, 22 Jan 2019 01:29:56 -0800 (PST)
Received: by mail-ed1-x535.google.com with SMTP id f23so18735242edb.3 for <json-canon@ietf.org>; Tue, 22 Jan 2019 01:29:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:subject:message-id:date:to; bh=5K8IIMFzwuXcl5nFafcFa2T4urzvtF2d6p9J7BY9suU=; b=cuyVbqciU4RI0oDkPExl1y6OvCRu2ynus/pAh4mNWjhURTTc2YUlSCP1EOOvDfoWRP 7Fo4oczNNwabDa/++IZSs+5oUPT70SgrZPepOCCCTTMDc9WRrt57L3nCfitYciRKv426 801X5tqbJ10jAphOs5UEffLYi4TW/XZykfsvhGUfc3AxisGjGWcRWvQ6HqHWk7uVKqUw pictQNSDPHHT83LIkdsXNyfHQhIA10IeR9u+hZHdTBi5F+kDGH9+Nde5xlApRp5TWYtA lAua9quHqLXlGBJ6MkVuJQ80RCxjMXKbIPSu7+7uQiu9WwbbsrIxkjTcX3ni13YIi5tK VyBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=5K8IIMFzwuXcl5nFafcFa2T4urzvtF2d6p9J7BY9suU=; b=KOOaiJjiWhvNRGjKdeHANXsHI6F31vWwvLGbArWRVVKVKKnjQlWEBA5AO1yXIvmfNW G+l6CmcBkvkAL5QejsYejdAr3zWoe9g8U8OPisZp8jMDia3b/YvL+8A+hsIVbKudTZn1 sMR+hpoYKpfVyU6IAzn0o1aeSF8wDB2D5sMjXNHuy3ml+r0/cfEa9viTv2WXsxTQ8grf QzcDNbANXzBMs2yIMmqTdSSsNZ2qVQ1vJKH6foK+PLZBTZiaesp2PIj6wmImp3LYzEvA UMtsIvswbpy9IIaf/0g05lQfAt/sGGPdNf7rVhui7fuJZga5R0t/oZU0+u+dKqwQPl5n OruQ==
X-Gm-Message-State: AJcUukeMjXPPhGCmnG+Nyg5U2Ux+iD0WWQPVRgQ6BzawS8wg+nnKtoCU Xlz1DBOeV3GqGIlWPOmuciHr8x0r
X-Google-Smtp-Source: ALg8bN6nGl/xjF2dq2yJPTZ1zv3elKvOiR2B0wlBmq5f0H2LBGkNZvP7S0BcFO0ewRvtfdRfMG6dAA==
X-Received: by 2002:a50:e045:: with SMTP id g5mr30789096edl.152.1548149394434;  Tue, 22 Jan 2019 01:29:54 -0800 (PST)
Received: from [156.106.224.165] ([156.106.224.165]) by smtp.gmail.com with ESMTPSA id r8sm9111531edo.11.2019.01.22.01.29.53 for <json-canon@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Jan 2019 01:29:53 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D6E5FA58-EFB6-4B7B-8F21-43294CDF9634"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <77BA66F8-41ED-4E8E-AF38-4AFFAF27532D@gmail.com>
Date: Tue, 22 Jan 2019 10:29:42 +0100
To: json-canon@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/e31J0xk7b9TnI1_cOgWWOVWH8S8>
Subject: [Json-canon] Welcome
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, 22 Jan 2019 09:29:58 -0000

--Apple-Mail=_D6E5FA58-EFB6-4B7B-8F21-43294CDF9634
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

All,

I just wanted to welcome everyone to the email list for JSON =
Canonicalization. A quick update, I believe a proposed charter will be =
sent to the list in the coming days, so please watch for that.  Also, we =
will be making a request for a WG forming BoF for Prague.=20

If you have any comments or suggestions, please send them to the list.  =
I for one personally know of several work items in the IETF and outside =
the IETF that really need this work to be standardized. =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."


--Apple-Mail=_D6E5FA58-EFB6-4B7B-8F21-43294CDF9634
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"">All,<div class=3D""><br class=3D""></div><div class=3D"">I =
just wanted to welcome everyone to the email list for JSON =
Canonicalization. A quick update, I believe a proposed charter will be =
sent to the list in the coming days, so please watch for that. =
&nbsp;Also, we will be making a request for a WG forming BoF for =
Prague.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">If=
 you have any comments or suggestions, please send them to the list. =
&nbsp;I for one personally know of several work items in the IETF and =
outside the IETF that really need this work to be standardized. =
&nbsp;</div><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>
<br class=3D""></div></body></html>=

--Apple-Mail=_D6E5FA58-EFB6-4B7B-8F21-43294CDF9634--


From nobody Tue Jan 22 04:31:19 2019
Return-Path: <rjs@mitre.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 3D781130F50 for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 04:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.442
X-Spam-Level: 
X-Spam-Status: No, score=-4.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mitre.onmicrosoft.com header.b=ESjt4KA9; dkim=pass (1024-bit key) header.d=mitre.org header.b=hQ5mCNJ+
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 p65c_IwFrGed for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 04:31:13 -0800 (PST)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDDD5130F4F for <json-canon@ietf.org>; Tue, 22 Jan 2019 04:31:13 -0800 (PST)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id D63146C002B; Tue, 22 Jan 2019 07:31:12 -0500 (EST)
Received: from imshyb01.MITRE.ORG (unknown [129.83.29.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtpvmsrv1.mitre.org (Postfix) with ESMTPS id C857B13B812; Tue, 22 Jan 2019 07:31:12 -0500 (EST)
Received: from imshyb02.MITRE.ORG (129.83.29.3) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 22 Jan 2019 07:31:12 -0500
Received: from GCC01-DM2-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 22 Jan 2019 07:31:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com;  s=selector1-mitre-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Nk1wfo83kZQ3lPz7zriPz+1kTDiVkZKCAIzjOEwG/8M=; b=ESjt4KA9rMTHshcQdafp0ZYqbfk/0v6E+LiHtWg8/tx0UB7oo5EM7e1W1XUvw0Fhft8OTIng9wyvN4n55E/RyYwE8HTip5nHPYkbyUhMqNkBdvEDGnyZAIC6pYcjMcb5eB1LnpcqJW2fn3zzywx2z4nDHLo8H4NLA1VDbFliKAA=
Received: from BN6PR09MB1524.namprd09.prod.outlook.com (10.173.204.8) by BN6PR09MB1522.namprd09.prod.outlook.com (10.173.205.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1537.26; Tue, 22 Jan 2019 12:31:11 +0000
Received: from BN6PR09MB1524.namprd09.prod.outlook.com ([fe80::71:14d6:1ad9:1e28]) by BN6PR09MB1524.namprd09.prod.outlook.com ([fe80::71:14d6:1ad9:1e28%4]) with mapi id 15.20.1537.031; Tue, 22 Jan 2019 12:31:11 +0000
From: "Struse, Richard J." <rjs@mitre.org>
To: Carsten Bormann <cabo@tzi.org>
CC: "json-canon@ietf.org" <json-canon@ietf.org>
Thread-Topic: [EXT] Re: [Json-canon] Support for a WG
Thread-Index: AQHUrtiBAcQCRDGu4UC3Ij3FNjzyvKW0lWIAgAZV2YA=
Date: Tue, 22 Jan 2019 12:31:10 +0000
Message-ID: <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org>
In-Reply-To: <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rjs@mitre.org; 
x-originating-ip: [192.80.55.87]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR09MB1522; 6:dP/PK+uE+9Do6idUv0MA7bw35dCBVazVopSmxs2hZNeszDRDu9tICWAKk/+6lLjijdf7VZwwvdtXG/nyyUYfWAzIcaIK6mDQn7GSDJZTKcMABMjn9W8W9oEZhspZF7wyE9lXK75AT7JVPUc97ZJQTqXNsWQFl0nLmr5o2RzVIsxDTnBszTrzRaO+03IOnh50jbIZ0d9ihNyyvJwtsHl4xD6OsLYBukWdd/K1ZCQGx5HC4WIgPvd0qTbMADMfK++PEvgCZc9zUACXpHbJCkgwxeuGWsDopxf/7zsMxyxHKXBcCrzeCb5O42IYnTcTqqCjMCejTC6x+8IugLmHfIneXq0JyqE2mYuYwExRXbBmZIfd/VYojOVKzKfmLS7/qyeMeZlv6vKtVTwavJBiHtKEmar4no3+kwGbf1ilGNnjcMMZPj93/sy1BXcJ04vlo3H1mb2gqEwfLyKO1LeRG9TnKQ==; 5:5mimQpoUrs1fJnmDQzfhRqrI3Z/+BSDgYAkwD5q0XVwUj5KS8VHOx9R58y1ME1As317jYxyTSMB/n6bT6b9eILvLQ2fQ4O984rnduqgBJZieBle+OCc1e4yNdcoF3Qkpuekb63Drl951D9M79vGVQcgXCkjaVUTlCxIpnm9b86UsS42QFgswV27hRn0G2Fs1Z6gUAp/4fMPt7EhoIgRDuw==; 7:Ct1tC6w7uls1mYKrYjAfBP8oU27i7fn7uPJUSWOdk/szACzS/lF9v5Iy4AfONb9GghxdOAjuZTjJCqqk0UqAd/lNLhWsEDHRiargxhfMiOS/m433dzFXzY4iiSldIwBILmUDgyo230A7gRHuQ6Z+5Q==
x-ms-office365-filtering-correlation-id: 2facb88e-b7d0-4714-5bc9-08d680657ddd
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BN6PR09MB1522; 
x-ms-traffictypediagnostic: BN6PR09MB1522:
x-microsoft-antispam-prvs: <BN6PR09MB1522304BD471665C6E0BC52BA2980@BN6PR09MB1522.namprd09.prod.outlook.com>
x-forefront-prvs: 0925081676
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(366004)(376002)(39850400004)(396003)(189003)(199004)(8936002)(36756003)(2616005)(6512007)(86362001)(105586002)(106356001)(2906002)(11346002)(229853002)(99286004)(83716004)(8676002)(81156014)(6246003)(81166006)(66066001)(486006)(476003)(446003)(68736007)(186003)(82746002)(6436002)(4326008)(53936002)(256004)(316002)(76176011)(26005)(6916009)(25786009)(305945005)(97736004)(33656002)(478600001)(6116002)(71200400001)(3846002)(71190400001)(4744005)(14454004)(6486002)(6506007)(53546011)(7736002)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR09MB1522; H:BN6PR09MB1524.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: sr8odpSHm2rtj+efcVbSrGc0AoJeFNPs6i/ueNybXTh/mrhnE9rEsfapCdhfAt652lZOlvE9aWJtUSM7TMlPlD/e81QdDUUMhoe6gPqUAxOu9fdSpDUopCmiN8w1PRO5uq+/BmgFzzRyvbYGItyqveB1N7sR6l6ztCs6bGTFzHNk6wFh2akyS8LiN1ICiPabXAGZeCROYkStKRoc7t0PMdBDOmkv1+HuUbsWmiuYPpxG6HA3+RIkJE0XcvNQR5gsMR3fwUvEbZHxJ0T3tKOL/ZAYfetgR1rHk8m6neWAUuPNEDZsUGpOgH8z1ddVMLeInUByJre/JBqizlO+yWjbkZaKgIK3DakCiTwV1RO+YLA7xAZ1mgDvRPvKbM1M/Es9e3ZZrIVfkYH+BrUYpU7qGcN7iraJsjn4MEkaENwRuAY=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <25FC48A0B5649E48AAFA379E73036A42@namprd09.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2facb88e-b7d0-4714-5bc9-08d680657ddd
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2019 12:31:10.9743 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR09MB1522
X-OriginatorOrg: mitre.org
X-MITRE: 8GQsMWxq66rxk57w
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.org; h=from:to:cc:subject:date:message-id:references:in-reply-to:content-type:content-id:content-transfer-encoding:mime-version; s=selector1; bh=Nk1wfo83kZQ3lPz7zriPz+1kTDiVkZKCAIzjOEwG/8M=; b=hQ5mCNJ+EnXZPIM3ERhxWersFGqJfFL1N3kg1pY1OGg37scMqy8kuduZ3gwk5RsHTXAaLoasOAwcc6dRDAQRolZ1c/bR75/kglCrfy5uFmG/D+7Q47Z84h9pxEL4okwHLENRPUg2dG8DjLNM7wba0u5MzjO1xEVD33xz8Ygb2Ho=
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/li6_rfYxMIqeWZ9VXvBd1n3jrwI>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 22 Jan 2019 12:31:16 -0000

VGhlIHVzZSBjYXNlIGlzIHRvIGVuYWJsZSBvdGhlciBzdGFuZGFyZHMgdGhhdCB1c2UgYSBKU09O
IHNlcmlhbGl6YXRpb24gdG8gYmUgYWJsZSB0byBjb3VudCBvbiB0d28gb2JqZWN0cywgZWFjaCB3
aXRoIHRoZSBzYW1lIGNvbnRlbnRzLCBoYXZpbmcgdGhlIHNhbWUgaGFzaCB2YWx1ZSBiYXNlZCBv
biB0aGVpciByZXByZXNlbnRhdGlvbiBpbiBKU09OLg0KDQpEb2VzIHRoYXQgaGVscD8NCg0K77u/
T24gMS8xOC8xOSwgMTo0NyBBTSwgIkNhcnN0ZW4gQm9ybWFubiIgPGNhYm9AdHppLm9yZz4gd3Jv
dGU6DQoNCiAgICBPbiBKYW4gMTgsIDIwMTksIGF0IDAzOjUwLCBTdHJ1c2UsIFJpY2hhcmQgSi4g
PHJqc0BtaXRyZS5vcmc+IHdyb3RlOg0KICAgID4gDQogICAgPiBBIHN0YW5kYXJkaXplZCBkZXRl
cm1pbmlzdGljIGNhbm9uaWNhbGl6YXRpb24gb2YgSlNPTiBkYXRhIHN0cmVhbXMgaXMgZXNzZW50
aWFsDQogICAgDQogICAgRm9yIHdoYXQ/DQogICAgDQogICAgSSB0aGluayB3ZSB3b3VsZCBhbGwg
YmVuZWZpdCBpZiB5b3UgY291bGQgZXhwbGFpbiB5b3VyIHVzZSBjYXNlLg0KICAgIA0KICAgIEdy
w7zDn2UsIENhcnN0ZW4NCiAgICANCiAgICANCg0K


From nobody Tue Jan 22 07:19:11 2019
Return-Path: <athomson@lookingglasscyber.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 1DF4512DD85 for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 07:19:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lookingglasscyber.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 oScO0ehPKUt0 for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 07:19:07 -0800 (PST)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-eopbgr800040.outbound.protection.outlook.com [40.107.80.40]) (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 973C8126CC7 for <json-canon@ietf.org>; Tue, 22 Jan 2019 07:19:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lookingglasscyber.com;  s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XiRoUGN+c2TcAnLSw2L5HW0TJdJiUIvge5qobSX3Ae4=; b=bestrNS9OJSGBtV85tlyxE5jPmsXpxqJ6WoTtBkA5oKpRZQMtKuV5mMswXm3/YbmaUTffJwtb2VLJEs3QchXdCWTrPo7fJi4k+VheU1nQyLHOs7e8G4ptfxJfQNQ7AAdwxXI7mD1wHJUUR8nQaEAuNSPXPksi2h+ceecaFmxNUE=
Received: from MW2PR18MB2137.namprd18.prod.outlook.com (52.132.182.156) by MW2PR18MB2315.namprd18.prod.outlook.com (52.132.183.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1537.25; Tue, 22 Jan 2019 15:19:05 +0000
Received: from MW2PR18MB2137.namprd18.prod.outlook.com ([fe80::198d:2eea:38e4:3ecb]) by MW2PR18MB2137.namprd18.prod.outlook.com ([fe80::198d:2eea:38e4:3ecb%5]) with mapi id 15.20.1537.031; Tue, 22 Jan 2019 15:19:05 +0000
From: Allan Thomson <athomson@lookingglasscyber.com>
To: "Struse, Richard J." <rjs@mitre.org>, Carsten Bormann <cabo@tzi.org>
CC: "json-canon@ietf.org" <json-canon@ietf.org>
Thread-Topic: [Json-canon] [EXT] Re:  Support for a WG
Thread-Index: AQHUrtiBAcQCRDGu4UC3Ij3FNjzyvKW0lWIAgAZV2YD///yWAA==
Date: Tue, 22 Jan 2019 15:19:05 +0000
Message-ID: <E7B44CE8-CE81-4AB3-9665-12D1A52FD9C5@lookingglasscyber.com>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org>
In-Reply-To: <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.15.0.190115
authentication-results: spf=none (sender IP is ) smtp.mailfrom=athomson@lookingglasscyber.com; 
x-originating-ip: [69.181.82.213]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MW2PR18MB2315; 6:lLc881hsOwkqwkwiz5JFQNrNFbz1Ya4fYLY5EqQQSuzIlLWno5NowR5zZB5tMf2knLnF3LV9nLiKYImY2pck/ChDVdV1BJqxLLpXxvLkkj+/lyDRhp3kH0hytg69Ebs9o8vE05f5zuOXBX5as5UEvQc96wrrSxz4eA5QIGDjJ+I87oaoRp7ry82kH1tK73eRupUCCzq5ZqeMxoyuvvubtDxQsSMRvgv6TpksFfivjzfrRhzBbwu5GRxxee3L8X5OXATiIeokShrAGjATXs4RV3if+wUUDkxJ+483koml8pswP2/gczJxD5nMSJirmYQi1P5Jq10OU/+qP/yM/G+pxJRKhmtCa2gLnoMyQygHsFVo4An33tSzRZF+xNCNV7EdqctwUoduZHjZsMuwF4jmYrdRrsuJLvnxevkpZEyliy4GA5B/HHn8fGQS3V8UaboRbFbMmriV0k1MZ1OGjsVtkQ==; 5:5AXRtIw2DpxZkiVoxEDzLRwEDxAR3iZAq+ogIrQwCGj6mBdc1LGEDXRWgylCs+YoZ6wGNFc0Cf23UJDObZp6tnvlWD0HyjTNEi8qT4NLSXkdeUieU+d9aeNwtLf1wFbELr6STYD3qPBI8RkhWOJp+/qzQ+8myvv5R0pFKETLOEncpPhhCHBwmWsHxFNhTcyRDOGXfc7lgb/4nbSflltfPw==; 7:lBTesOe/A9qmzq3U4AQvXrcYdc3+cFBCEKKRg7shprJLRL6DB1VprFoxptEEaQJVTllltFRXypKaguGCckjDmofLLebBn9YvoXKXQ1l/D/qoUE5c+jEBBuf2SAN6P04T2thhDM6rc9QXNEpIoZJXhw==
x-ms-office365-filtering-correlation-id: a1d29cee-7749-4ae7-6abe-08d6807cf287
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(2017052603328)(7153060)(7193020); SRVR:MW2PR18MB2315; 
x-ms-traffictypediagnostic: MW2PR18MB2315:
x-microsoft-antispam-prvs: <MW2PR18MB23156CB72F8D89DE9DB8D7EBDA980@MW2PR18MB2315.namprd18.prod.outlook.com>
x-forefront-prvs: 0925081676
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(39850400004)(376002)(346002)(366004)(199004)(189003)(478600001)(6512007)(4326008)(256004)(14444005)(8676002)(97736004)(68736007)(86362001)(53936002)(25786009)(6246003)(110136005)(71190400001)(71200400001)(82746002)(58126008)(476003)(6306002)(83716004)(14454004)(6116002)(3846002)(966005)(36756003)(2616005)(66066001)(316002)(446003)(53546011)(6506007)(99286004)(305945005)(2906002)(102836004)(76176011)(11346002)(7736002)(33656002)(81156014)(81166006)(486006)(229853002)(105586002)(186003)(6486002)(26005)(6436002)(8936002)(106356001); DIR:OUT; SFP:1101; SCL:1; SRVR:MW2PR18MB2315; H:MW2PR18MB2137.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: lookingglasscyber.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: yU8MKa5sJwB/wWgYWjVIwBQ47RUwnLb267nHkQEvUOCHps0TaXqKveG6QgfWnGdrr/rjGaNcdAkG/Cu9PHsaqWZwwTgm+VIQx6tOCrHkPGoTJ+m2G9LS5xleqNF9NtmLQlH8SLIh08YqYOdWIv0inUb/AGeynDL/NF7WwkF1aJBq3JvSoaLkq9mo6t3230QnmXAtjRLlHkDYd67zcgidNr3+9bnWSQ1OvT/IKdATzw/lQXzdYDA5sKWfOQRLvBRiRYqWbfIOGWlhAB1VFKqlcPwxUJ1IjoEhyJXGvOr0Z44oxtgyW85oJl9CnR7B9+1nS7yZ74zvuS0c8Hh7G1dSopKg/PvKzFk+tWqXOftitThf0NOmJINMqeoixoVGUQgLtxB1PRvratmhaYuSgcegCfNGY9ehhyyeerECul1yzIA=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <3FD81D2552A4B94C9F8E7D78BB1FD351@namprd18.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: lookingglasscyber.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a1d29cee-7749-4ae7-6abe-08d6807cf287
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2019 15:19:05.1671 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 11622456-b9ab-4329-8602-bf364508a848
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR18MB2315
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/fIJ8cVOMttCIqvF-dRQaiPw8rw4>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 22 Jan 2019 15:19:10 -0000

UGFydGljdWxhcmx5IGltcG9ydGFudCBpbiB3aGF0IFJpY2ggc2F5cyBpcyBhbHNvIGlzIHRvIGVu
c3VyZSB0aGUgc2FtZSBoYXNoIGlzIGNyZWF0ZWQgd2hlcmUgdGhvc2UgSlNPTiBvYmplY3RzIGhh
dmUgb3B0aW9uYWwgb3IgZW1wdHkvbWlzc2luZyBwcm9wZXJ0aWVzIHRoYXQgYXJlIGRlZmluZWQg
aW4gdGhlIHNjaGVtYSBvZiB0aGUgb2JqZWN0Lg0KDQpSZWdhcmRzDQoNCkFsbGFuDQoNCu+7v09u
IDEvMjIvMTksIDQ6MzEgQU0sICJqc29uLWNhbm9uIG9uIGJlaGFsZiBvZiBTdHJ1c2UsIFJpY2hh
cmQgSi4iIDxqc29uLWNhbm9uLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIHJqc0BtaXRy
ZS5vcmc+IHdyb3RlOg0KDQogICAgVGhlIHVzZSBjYXNlIGlzIHRvIGVuYWJsZSBvdGhlciBzdGFu
ZGFyZHMgdGhhdCB1c2UgYSBKU09OIHNlcmlhbGl6YXRpb24gdG8gYmUgYWJsZSB0byBjb3VudCBv
biB0d28gb2JqZWN0cywgZWFjaCB3aXRoIHRoZSBzYW1lIGNvbnRlbnRzLCBoYXZpbmcgdGhlIHNh
bWUgaGFzaCB2YWx1ZSBiYXNlZCBvbiB0aGVpciByZXByZXNlbnRhdGlvbiBpbiBKU09OLg0KICAg
IA0KICAgIERvZXMgdGhhdCBoZWxwPw0KICAgIA0KICAgIE9uIDEvMTgvMTksIDE6NDcgQU0sICJD
YXJzdGVuIEJvcm1hbm4iIDxjYWJvQHR6aS5vcmc+IHdyb3RlOg0KICAgIA0KICAgICAgICBPbiBK
YW4gMTgsIDIwMTksIGF0IDAzOjUwLCBTdHJ1c2UsIFJpY2hhcmQgSi4gPHJqc0BtaXRyZS5vcmc+
IHdyb3RlOg0KICAgICAgICA+IA0KICAgICAgICA+IEEgc3RhbmRhcmRpemVkIGRldGVybWluaXN0
aWMgY2Fub25pY2FsaXphdGlvbiBvZiBKU09OIGRhdGEgc3RyZWFtcyBpcyBlc3NlbnRpYWwNCiAg
ICAgICAgDQogICAgICAgIEZvciB3aGF0Pw0KICAgICAgICANCiAgICAgICAgSSB0aGluayB3ZSB3
b3VsZCBhbGwgYmVuZWZpdCBpZiB5b3UgY291bGQgZXhwbGFpbiB5b3VyIHVzZSBjYXNlLg0KICAg
ICAgICANCiAgICAgICAgR3LDvMOfZSwgQ2Fyc3Rlbg0KICAgICAgICANCiAgICAgICAgDQogICAg
DQogICAgLS0gDQogICAganNvbi1jYW5vbiBtYWlsaW5nIGxpc3QNCiAgICBqc29uLWNhbm9uQGll
dGYub3JnDQogICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9qc29uLWNh
bm9uDQogICAgDQoNCg==


From nobody Tue Jan 22 08:37:57 2019
Return-Path: <samuel@erdtman.se>
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 2B5EA130F83 for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 08:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level: 
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=erdtman-se.20150623.gappssmtp.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 KAARpjtqThm6 for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 08:37:49 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 C8F5D130FA9 for <json-canon@ietf.org>; Tue, 22 Jan 2019 08:37:48 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id i12so12013282pfo.7 for <json-canon@ietf.org>; Tue, 22 Jan 2019 08:37:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erdtman-se.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qvSyroAGMhzxuPtx5fsUGUgH6Xkazb5sQWvPje9M4CM=; b=Ecezgsw+9u/uPLBYbZP2AX43J3GkTvFJLK0meZL7a1uUm0KlzkCHiuzwvMDaHYnay0 0GNy0Op2eacNkApjrEAR5yQzvwWAUCqf33UTHMTv7F/EADSWSsOzhxrhkERRB3R6afhA fQGpJMcFtkLy0ld9U9BUAUervJ+4LdFYmeH414w4ni0RC++OkLCXZUL4v9K5KmxWmWgQ ZPhZi/3VGmlko4iid+J1dz1lO1jkjQaSZQ0X5YlANVbFiZdeygkrzG2XHuSmmgnavsYP /Obl4hhx2E1Mg6EDMf1z4gBJa4Hmv/RtCnAIRuh9eMGnmMAT782DVp4w0UVg0Q8GK+UC rt6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qvSyroAGMhzxuPtx5fsUGUgH6Xkazb5sQWvPje9M4CM=; b=QrPVWc+iLeAlr5IgBaIl5qybkqEtcmxoeEIxuSGn4xoOSzkM6aF5wbCMkedLsr+M7H w7FQWSWy2JAhxF4qz4WWWPo5xNUgrHou0h3QMxBgLG20cfEnxWABx39B5Bfhg4hS+hAq 1xqEIyeVozPLHF7HguyG5TqEcfLQdj6DF+dGxWqWJrdTNH8q7I3W5JJpveXFC1FPQG4c sytBc5l4P4ir2r8BzOvJ3TPuitORZESK6X8XzpdpDUyQC0U5q/6eIFR8syWnnFkIOcel /JNJFrx5Y44y68tqiwapaKaYdc/kGiL4c4ma0o7EPvpfxZE/KXxDtVzc+v9EvbhMXiPi 495Q==
X-Gm-Message-State: AJcUukfMz65jOrLpt/0kCCMXbn/UTwUBN1TKtJCn6v5ZiPiHA3DfME9j Dm0lfKYiuD35S7zoC/n9wC5DCtOrFrXvbyFWo5u3k0+nckTpBw==
X-Google-Smtp-Source: ALg8bN5nfdiUrZIlKQvV+z6fHKMJAA0HA+2bujApx1uRKBXNvxUq6GCsVBli4+WrvezNk0A2d4dj1NOZS1ePwDk6Sok=
X-Received: by 2002:a62:2702:: with SMTP id n2mr34878946pfn.29.1548175068270;  Tue, 22 Jan 2019 08:37:48 -0800 (PST)
MIME-Version: 1.0
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <E7B44CE8-CE81-4AB3-9665-12D1A52FD9C5@lookingglasscyber.com>
In-Reply-To: <E7B44CE8-CE81-4AB3-9665-12D1A52FD9C5@lookingglasscyber.com>
From: Samuel Erdtman <samuel@erdtman.se>
Date: Tue, 22 Jan 2019 17:37:37 +0100
Message-ID: <CAF2hCbYSDsPf6p56i1uhSBZZQv7jgLdCQGqHmsVi+nzbW3_46A@mail.gmail.com>
To: Allan Thomson <athomson@lookingglasscyber.com>
Cc: "Struse, Richard J." <rjs@mitre.org>, Carsten Bormann <cabo@tzi.org>,  "json-canon@ietf.org" <json-canon@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fea7ca05800e98fb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/fy3Vt7kyNHAZ054-ftUxSPdMZCo>
Subject: Re: [Json-canon] [EXT] Re: Support for a WG
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, 22 Jan 2019 16:37:56 -0000

--000000000000fea7ca05800e98fb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I do not think we should go into schemas, that is one of the things that
makes XMLDigSig inconvenient. But instead keep to simple JSON stringifying
with predictable result.
On Tue, 22 Jan 2019 at 16:19, Allan Thomson <athomson@lookingglasscyber.com=
>
wrote:

> Particularly important in what Rich says is also is to ensure the same
> hash is created where those JSON objects have optional or empty/missing
> properties that are defined in the schema of the object.
>
> Regards
>
> Allan
>
> =EF=BB=BFOn 1/22/19, 4:31 AM, "json-canon on behalf of Struse, Richard J.=
" <
> json-canon-bounces@ietf.org on behalf of rjs@mitre.org> wrote:
>
>     The use case is to enable other standards that use a JSON
> serialization to be able to count on two objects, each with the same
> contents, having the same hash value based on their representation in JSO=
N.
>
>     Does that help?
>
>     On 1/18/19, 1:47 AM, "Carsten Bormann" <cabo@tzi.org> wrote:
>
>         On Jan 18, 2019, at 03:50, Struse, Richard J. <rjs@mitre.org>
> wrote:
>         >
>         > A standardized deterministic canonicalization of JSON data
> streams is essential
>
>         For what?
>
>         I think we would all benefit if you could explain your use case.
>
>         Gr=C3=BC=C3=9Fe, Carsten
>
>
>
>     --
>     json-canon mailing list
>     json-canon@ietf.org
>     https://www.ietf.org/mailman/listinfo/json-canon
>
>
> --
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon
>

--000000000000fea7ca05800e98fb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I do not think we should go into schemas, that is one of the things that ma=
kes XMLDigSig inconvenient. But instead keep to simple JSON stringifying wi=
th predictable result.<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tu=
e, 22 Jan 2019 at 16:19, Allan Thomson &lt;<a href=3D"mailto:athomson@looki=
ngglasscyber.com">athomson@lookingglasscyber.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">Particularly important in what Rich says is al=
so is to ensure the same hash is created where those JSON objects have opti=
onal or empty/missing properties that are defined in the schema of the obje=
ct.<br>
<br>
Regards<br>
<br>
Allan<br>
<br>
=EF=BB=BFOn 1/22/19, 4:31 AM, &quot;json-canon on behalf of Struse, Richard=
 J.&quot; &lt;<a href=3D"mailto:json-canon-bounces@ietf.org" target=3D"_bla=
nk">json-canon-bounces@ietf.org</a> on behalf of <a href=3D"mailto:rjs@mitr=
e.org" target=3D"_blank">rjs@mitre.org</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 The use case is to enable other standards that use a JSON ser=
ialization to be able to count on two objects, each with the same contents,=
 having the same hash value based on their representation in JSON.<br>
<br>
=C2=A0 =C2=A0 Does that help?<br>
<br>
=C2=A0 =C2=A0 On 1/18/19, 1:47 AM, &quot;Carsten Bormann&quot; &lt;<a href=
=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 On Jan 18, 2019, at 03:50, Struse, Richard J. &=
lt;<a href=3D"mailto:rjs@mitre.org" target=3D"_blank">rjs@mitre.org</a>&gt;=
 wrote:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; <br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; A standardized deterministic canonicalizat=
ion of JSON data streams is essential<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 For what?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I think we would all benefit if you could expla=
in your use case.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 -- <br>
=C2=A0 =C2=A0 json-canon mailing list<br>
=C2=A0 =C2=A0 <a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json=
-canon@ietf.org</a><br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" =
rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/=
json-canon</a><br>
<br>
<br>
-- <br>
json-canon mailing list<br>
<a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-canon@ietf.or=
g</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/json-canon</a>=
<br>
</blockquote></div>

--000000000000fea7ca05800e98fb--


From nobody Tue Jan 22 08:47:33 2019
Return-Path: <athomson@lookingglasscyber.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 18B63130F4C for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 08:47:32 -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, 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 (1024-bit key) header.d=lookingglasscyber.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 IgWxkniFn13h for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 08:47:29 -0800 (PST)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700077.outbound.protection.outlook.com [40.107.70.77]) (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 DF44D130F3C for <json-canon@ietf.org>; Tue, 22 Jan 2019 08:47:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lookingglasscyber.com;  s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9Ydyj0KIjd7aSYvB0WwuE39Laubtm+fL39ZBG6idReY=; b=gDOycyodBnXfpdyCmvZLIHAl7HaybMWy9Okqm36mJuJ2IKFhtZQ0uJ36fQpt7hqoL83sWQDRgisdKWwJurSGtfsYhyikKJwh0bpD/QvQe8inRxzKhRjc7S3as7Ng6f6NthPyRUtJNcP2CDhaPd0BsC6N0CFe+VICKU06Jq04MdI=
Received: from MW2PR18MB2137.namprd18.prod.outlook.com (52.132.182.156) by MW2PR18MB2105.namprd18.prod.outlook.com (52.132.182.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1537.29; Tue, 22 Jan 2019 16:47:25 +0000
Received: from MW2PR18MB2137.namprd18.prod.outlook.com ([fe80::198d:2eea:38e4:3ecb]) by MW2PR18MB2137.namprd18.prod.outlook.com ([fe80::198d:2eea:38e4:3ecb%5]) with mapi id 15.20.1537.031; Tue, 22 Jan 2019 16:47:25 +0000
From: Allan Thomson <athomson@lookingglasscyber.com>
To: Samuel Erdtman <samuel@erdtman.se>
CC: "Struse, Richard J." <rjs@mitre.org>, Carsten Bormann <cabo@tzi.org>, "json-canon@ietf.org" <json-canon@ietf.org>
Thread-Topic: [Json-canon] [EXT] Re: Support for a WG
Thread-Index: AQHUsnDRMhgJqKLqakO77f4+MtbyCKW6+U+A
Date: Tue, 22 Jan 2019 16:47:25 +0000
Message-ID: <866D8EB8-49F6-4353-B502-F3337ACDBF61@lookingglasscyber.com>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <E7B44CE8-CE81-4AB3-9665-12D1A52FD9C5@lookingglasscyber.com> <CAF2hCbYSDsPf6p56i1uhSBZZQv7jgLdCQGqHmsVi+nzbW3_46A@mail.gmail.com>
In-Reply-To: <CAF2hCbYSDsPf6p56i1uhSBZZQv7jgLdCQGqHmsVi+nzbW3_46A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.15.0.190115
authentication-results: spf=none (sender IP is ) smtp.mailfrom=athomson@lookingglasscyber.com; 
x-originating-ip: [69.181.82.213]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MW2PR18MB2105; 6:t7nymEbjFFYVDGUcZ2elkyKUbWe6SD9rlCjLQolG/H5VBdDt8NN+K/wvB0AL3azyknrngOzeBdmxyvdxrscjG2kzBu8DiLBMUMCP37Vw3KpYSV1Y0Kev8Tel+gIuTlUQWIVrlcV428V6KhO0A8LkUqPm/5jXulpZwqgQ3nPIzZN+RZh89tRPiJMERHf6oT8JAJIV1ppnkHQwNFFlPFgfP3+R9wHqeEl8dW8EBQGJNIfwcj5F4i6Aow7+BLPAUykwfiEeSwZ/bJGKhcL9Yi2QRj/Z+cfthqmcpyucxv3JP5Rpg1aVi+Jf/WJ4XMmnmL7e8WHSK09IBsfgVKuRYHexXjmxd9hFIY+yUNxQgvVv99exCfnzKxr/wnxCF2YeTWeWxeGcl+3QQSThgrY0nCcBVGxzGIQDwox93kY6rKouFJgQWXI7qsplywquk064pTzIG5OpqXJfZM/uyIsxnaIDBQ==; 5:BRXNnwWfyF49r85h2m7U7xf+XpLfnXBP/J3As19aFzMS4xz3EAd4jejc36+hm8bmRDCJAqs8F4duySbPPW7LxvW3dmvdCt2i4xUPYZusT4CWmbpMzeyoR3gGVjeEvj0tDCHG6Hnx4xXD4mubAUoLWPuaTXFf5xAjP4W8C/3qUz/hN1YjQjs0Zjpc+oHlfXhlNTPXO8yY3AcCM+Z9rfB/kQ==; 7:1H4RBed4MPnCno8CD4J7frARCCvFcm+xtolD7yz9VP6mVNIs3zHYpxpwkYVQ7UTRJGqvkmNdMZKVK3NP6jBVO1oBkqPwsPpgp+SrYvHdlaZRZVl/jAmjO+wBGxcRRyjEWAwSwbSN22UkekZVtxv8WQ==
x-ms-office365-filtering-correlation-id: 2696378d-f70f-4c84-5338-08d6808949e2
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(2017052603328)(7153060)(7193020); SRVR:MW2PR18MB2105; 
x-ms-traffictypediagnostic: MW2PR18MB2105:
x-microsoft-antispam-prvs: <MW2PR18MB2105F0EE822887A5A92B70F3DA980@MW2PR18MB2105.namprd18.prod.outlook.com>
x-forefront-prvs: 0925081676
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(39850400004)(346002)(376002)(366004)(199004)(189003)(53546011)(99286004)(102836004)(606006)(26005)(186003)(93886005)(36756003)(33656002)(86362001)(83716004)(71200400001)(82746002)(106356001)(71190400001)(105586002)(6506007)(76176011)(68736007)(2616005)(53936002)(54896002)(6306002)(236005)(6116002)(6436002)(6512007)(446003)(2906002)(3846002)(6486002)(11346002)(256004)(478600001)(4326008)(486006)(14454004)(229853002)(476003)(966005)(25786009)(6246003)(6916009)(8676002)(81166006)(81156014)(8936002)(316002)(54906003)(7736002)(58126008)(66066001)(97736004)(14444005); DIR:OUT; SFP:1101; SCL:1; SRVR:MW2PR18MB2105; H:MW2PR18MB2137.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: lookingglasscyber.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: eLMc/G465AFFxRR9pTpIVJedVnAaDmNKQK7LvaIJHyBaxPXAebYpvzwuvmgGSBhNBDCq6cTkkx9xsy7r3k+IpVQvBi84UFC2bPKoF/3WHcYqzsxoIVYSlC1YYl3AgF+9bVeJ0E3mwnfF5melyO8PfcyHKlRBDt6M2yK/mvYUhhkWYB9XH2Gc8mLAfPoydvnkz5Xh/YZVREkXHtPtNjMm4yjAjxq3N9d4uRKrkUS39ulXDlVMX8YZTnaqt63yuRtIaVHN2aLEyNumwQcWhod0O+xtVKMwQVEedyM/8hGOh6SQ7Y6U840PW+NHETT2SB4mNwhecklYV5cVtNfeCNE/9rGwUeHGBj6GrJNPTAiVG5t1D55OIJjtJ5ZYg9oQZoXzSNnUxJsyEPDxLeXoTMRd0EkK5+cv54wUd/Bey/4uAPE=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_866D8EB849F64353B502F3337ACDBF61lookingglasscybercom_"
MIME-Version: 1.0
X-OriginatorOrg: lookingglasscyber.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2696378d-f70f-4c84-5338-08d6808949e2
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2019 16:47:25.7010 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 11622456-b9ab-4329-8602-bf364508a848
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR18MB2105
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/oee7dR9vUV_UmqKs75hxjcOP7Ik>
Subject: Re: [Json-canon] [EXT] Re: Support for a WG
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, 22 Jan 2019 16:47:32 -0000

--_000_866D8EB849F64353B502F3337ACDBF61lookingglasscybercom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmW0gbm90IHN1cmUgaG93IHlvdSBjYW4gY3JlYXRlIGEgY29uc2lzdGVudCBoYXNoIHZhbHVl
IHdpdGhvdXQgY29uc2lkZXJpbmcgaG93IGVtcHR5L29wdGlvbmFsIGZpZWxkcyBpbiBhIEpTT04g
c3RydWN0dXJlIGFyZSB0cmVhdGVkIGNvbnNpc3RlbnRseSBhY3Jvc3MgaW1wbGVtZW50YXRpb25z
Lg0KDQpTbyBpZiB0aGUgc2FtZSBvcHRpb25hbC9lbXB0eSBmaWVsZHMgZXhpc3QgZnJvbSAyIGRp
ZmZlcmVudCB2ZW5kb3JzL2luc3RhbmNlcyB0aGVuIGRvIHRoZXkgZW5kIHVwIHdpdGggdGhlIHNh
bWUgaGFzaD8NCg0KQWxsYW4NCg0KRnJvbTogU2FtdWVsIEVyZHRtYW4gPHNhbXVlbEBlcmR0bWFu
LnNlPg0KRGF0ZTogVHVlc2RheSwgSmFudWFyeSAyMiwgMjAxOSBhdCA4OjM3IEFNDQpUbzogQWxs
YW4gVGhvbXNvbiA8YXRob21zb25AbG9va2luZ2dsYXNzY3liZXIuY29tPg0KQ2M6ICJTdHJ1c2Us
IFJpY2hhcmQgSi4iIDxyanNAbWl0cmUub3JnPiwgQ2Fyc3RlbiBCb3JtYW5uIDxjYWJvQHR6aS5v
cmc+LCAianNvbi1jYW5vbkBpZXRmLm9yZyIgPGpzb24tY2Fub25AaWV0Zi5vcmc+DQpTdWJqZWN0
OiBSZTogW0pzb24tY2Fub25dIFtFWFRdIFJlOiBTdXBwb3J0IGZvciBhIFdHDQoNCkkgZG8gbm90
IHRoaW5rIHdlIHNob3VsZCBnbyBpbnRvIHNjaGVtYXMsIHRoYXQgaXMgb25lIG9mIHRoZSB0aGlu
Z3MgdGhhdCBtYWtlcyBYTUxEaWdTaWcgaW5jb252ZW5pZW50LiBCdXQgaW5zdGVhZCBrZWVwIHRv
IHNpbXBsZSBKU09OIHN0cmluZ2lmeWluZyB3aXRoIHByZWRpY3RhYmxlIHJlc3VsdC4NCk9uIFR1
ZSwgMjIgSmFuIDIwMTkgYXQgMTY6MTksIEFsbGFuIFRob21zb24gPGF0aG9tc29uQGxvb2tpbmdn
bGFzc2N5YmVyLmNvbTxtYWlsdG86YXRob21zb25AbG9va2luZ2dsYXNzY3liZXIuY29tPj4gd3Jv
dGU6DQpQYXJ0aWN1bGFybHkgaW1wb3J0YW50IGluIHdoYXQgUmljaCBzYXlzIGlzIGFsc28gaXMg
dG8gZW5zdXJlIHRoZSBzYW1lIGhhc2ggaXMgY3JlYXRlZCB3aGVyZSB0aG9zZSBKU09OIG9iamVj
dHMgaGF2ZSBvcHRpb25hbCBvciBlbXB0eS9taXNzaW5nIHByb3BlcnRpZXMgdGhhdCBhcmUgZGVm
aW5lZCBpbiB0aGUgc2NoZW1hIG9mIHRoZSBvYmplY3QuDQoNClJlZ2FyZHMNCg0KQWxsYW4NCg0K
T24gMS8yMi8xOSwgNDozMSBBTSwgImpzb24tY2Fub24gb24gYmVoYWxmIG9mIFN0cnVzZSwgUmlj
aGFyZCBKLiIgPGpzb24tY2Fub24tYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86anNvbi1jYW5vbi1i
b3VuY2VzQGlldGYub3JnPiBvbiBiZWhhbGYgb2YgcmpzQG1pdHJlLm9yZzxtYWlsdG86cmpzQG1p
dHJlLm9yZz4+IHdyb3RlOg0KDQogICAgVGhlIHVzZSBjYXNlIGlzIHRvIGVuYWJsZSBvdGhlciBz
dGFuZGFyZHMgdGhhdCB1c2UgYSBKU09OIHNlcmlhbGl6YXRpb24gdG8gYmUgYWJsZSB0byBjb3Vu
dCBvbiB0d28gb2JqZWN0cywgZWFjaCB3aXRoIHRoZSBzYW1lIGNvbnRlbnRzLCBoYXZpbmcgdGhl
IHNhbWUgaGFzaCB2YWx1ZSBiYXNlZCBvbiB0aGVpciByZXByZXNlbnRhdGlvbiBpbiBKU09OLg0K
DQogICAgRG9lcyB0aGF0IGhlbHA/DQoNCiAgICBPbiAxLzE4LzE5LCAxOjQ3IEFNLCAiQ2Fyc3Rl
biBCb3JtYW5uIiA8Y2Fib0B0emkub3JnPG1haWx0bzpjYWJvQHR6aS5vcmc+PiB3cm90ZToNCg0K
ICAgICAgICBPbiBKYW4gMTgsIDIwMTksIGF0IDAzOjUwLCBTdHJ1c2UsIFJpY2hhcmQgSi4gPHJq
c0BtaXRyZS5vcmc8bWFpbHRvOnJqc0BtaXRyZS5vcmc+PiB3cm90ZToNCiAgICAgICAgPg0KICAg
ICAgICA+IEEgc3RhbmRhcmRpemVkIGRldGVybWluaXN0aWMgY2Fub25pY2FsaXphdGlvbiBvZiBK
U09OIGRhdGEgc3RyZWFtcyBpcyBlc3NlbnRpYWwNCg0KICAgICAgICBGb3Igd2hhdD8NCg0KICAg
ICAgICBJIHRoaW5rIHdlIHdvdWxkIGFsbCBiZW5lZml0IGlmIHlvdSBjb3VsZCBleHBsYWluIHlv
dXIgdXNlIGNhc2UuDQoNCiAgICAgICAgR3LDvMOfZSwgQ2Fyc3Rlbg0KDQoNCg0KICAgIC0tDQog
ICAganNvbi1jYW5vbiBtYWlsaW5nIGxpc3QNCiAgICBqc29uLWNhbm9uQGlldGYub3JnPG1haWx0
bzpqc29uLWNhbm9uQGlldGYub3JnPg0KICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vanNvbi1jYW5vbg0KDQoNCi0tDQpqc29uLWNhbm9uIG1haWxpbmcgbGlzdA0KanNv
bi1jYW5vbkBpZXRmLm9yZzxtYWlsdG86anNvbi1jYW5vbkBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vanNvbi1jYW5vbg0K

--_000_866D8EB849F64353B502F3337ACDBF61lookingglasscybercom_
Content-Type: text/html; charset="utf-8"
Content-ID: <A0C217E3CE56C04E901A70B6D38F1FA8@namprd18.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N
CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4g
MS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9u
MTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUi
IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPknigJltIG5vdCBzdXJlIGhvdyB5b3UgY2FuIGNyZWF0ZSBhIGNvbnNpc3RlbnQg
aGFzaCB2YWx1ZSB3aXRob3V0IGNvbnNpZGVyaW5nIGhvdyBlbXB0eS9vcHRpb25hbCBmaWVsZHMg
aW4gYSBKU09OIHN0cnVjdHVyZSBhcmUgdHJlYXRlZCBjb25zaXN0ZW50bHkgYWNyb3NzIGltcGxl
bWVudGF0aW9ucy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtjb2xvcjpibGFjayI+U28gaWYgdGhlIHNhbWUgb3B0aW9uYWwvZW1wdHkgZmllbGRzIGV4aXN0
IGZyb20gMiBkaWZmZXJlbnQgdmVuZG9ycy9pbnN0YW5jZXMgdGhlbiBkbyB0aGV5IGVuZCB1cCB3
aXRoIHRoZSBzYW1lIGhhc2g/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Y29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2NvbG9yOmJsYWNrIj5BbGxhbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPlNhbXVlbCBFcmR0bWFuICZsdDtzYW11ZWxAZXJk
dG1hbi5zZSZndDs8YnI+DQo8Yj5EYXRlOiA8L2I+VHVlc2RheSwgSmFudWFyeSAyMiwgMjAxOSBh
dCA4OjM3IEFNPGJyPg0KPGI+VG86IDwvYj5BbGxhbiBUaG9tc29uICZsdDthdGhvbXNvbkBsb29r
aW5nZ2xhc3NjeWJlci5jb20mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVvdDtTdHJ1c2UsIFJpY2hh
cmQgSi4mcXVvdDsgJmx0O3Jqc0BtaXRyZS5vcmcmZ3Q7LCBDYXJzdGVuIEJvcm1hbm4gJmx0O2Nh
Ym9AdHppLm9yZyZndDssICZxdW90O2pzb24tY2Fub25AaWV0Zi5vcmcmcXVvdDsgJmx0O2pzb24t
Y2Fub25AaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBbSnNvbi1jYW5vbl0g
W0VYVF0gUmU6IFN1cHBvcnQgZm9yIGEgV0c8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBkbyBub3QgdGhpbmsgd2Ugc2hvdWxkIGdvIGludG8g
c2NoZW1hcywgdGhhdCBpcyBvbmUgb2YgdGhlIHRoaW5ncyB0aGF0IG1ha2VzIFhNTERpZ1NpZyBp
bmNvbnZlbmllbnQuIEJ1dCBpbnN0ZWFkIGtlZXAgdG8gc2ltcGxlIEpTT04gc3RyaW5naWZ5aW5n
IHdpdGggcHJlZGljdGFibGUgcmVzdWx0LjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUdWUsIDIyIEphbiAyMDE5IGF0IDE2OjE5LCBBbGxhbiBU
aG9tc29uICZsdDs8YSBocmVmPSJtYWlsdG86YXRob21zb25AbG9va2luZ2dsYXNzY3liZXIuY29t
Ij5hdGhvbXNvbkBsb29raW5nZ2xhc3NjeWJlci5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVm
dDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBhcnRpY3Vs
YXJseSBpbXBvcnRhbnQgaW4gd2hhdCBSaWNoIHNheXMgaXMgYWxzbyBpcyB0byBlbnN1cmUgdGhl
IHNhbWUgaGFzaCBpcyBjcmVhdGVkIHdoZXJlIHRob3NlIEpTT04gb2JqZWN0cyBoYXZlIG9wdGlv
bmFsIG9yIGVtcHR5L21pc3NpbmcgcHJvcGVydGllcyB0aGF0IGFyZSBkZWZpbmVkIGluIHRoZSBz
Y2hlbWEgb2YgdGhlIG9iamVjdC48YnI+DQo8YnI+DQpSZWdhcmRzPGJyPg0KPGJyPg0KQWxsYW48
YnI+DQo8YnI+DQpPbiAxLzIyLzE5LCA0OjMxIEFNLCAmcXVvdDtqc29uLWNhbm9uIG9uIGJlaGFs
ZiBvZiBTdHJ1c2UsIFJpY2hhcmQgSi4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpqc29uLWNh
bm9uLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5qc29uLWNhbm9uLWJvdW5jZXNA
aWV0Zi5vcmc8L2E+IG9uIGJlaGFsZiBvZg0KPGEgaHJlZj0ibWFpbHRvOnJqc0BtaXRyZS5vcmci
IHRhcmdldD0iX2JsYW5rIj5yanNAbWl0cmUub3JnPC9hPiZndDsgd3JvdGU6PGJyPg0KPGJyPg0K
Jm5ic3A7ICZuYnNwOyBUaGUgdXNlIGNhc2UgaXMgdG8gZW5hYmxlIG90aGVyIHN0YW5kYXJkcyB0
aGF0IHVzZSBhIEpTT04gc2VyaWFsaXphdGlvbiB0byBiZSBhYmxlIHRvIGNvdW50IG9uIHR3byBv
YmplY3RzLCBlYWNoIHdpdGggdGhlIHNhbWUgY29udGVudHMsIGhhdmluZyB0aGUgc2FtZSBoYXNo
IHZhbHVlIGJhc2VkIG9uIHRoZWlyIHJlcHJlc2VudGF0aW9uIGluIEpTT04uPGJyPg0KPGJyPg0K
Jm5ic3A7ICZuYnNwOyBEb2VzIHRoYXQgaGVscD88YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7IE9u
IDEvMTgvMTksIDE6NDcgQU0sICZxdW90O0NhcnN0ZW4gQm9ybWFubiZxdW90OyAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmNhYm9AdHppLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmNhYm9AdHppLm9yZzwvYT4m
Z3Q7IHdyb3RlOjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBPbiBKYW4g
MTgsIDIwMTksIGF0IDAzOjUwLCBTdHJ1c2UsIFJpY2hhcmQgSi4gJmx0OzxhIGhyZWY9Im1haWx0
bzpyanNAbWl0cmUub3JnIiB0YXJnZXQ9Il9ibGFuayI+cmpzQG1pdHJlLm9yZzwvYT4mZ3Q7IHdy
b3RlOjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmZ3Q7IDxicj4NCiZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmZ3Q7IEEgc3RhbmRhcmRpemVkIGRldGVybWluaXN0aWMgY2Fu
b25pY2FsaXphdGlvbiBvZiBKU09OIGRhdGEgc3RyZWFtcyBpcyBlc3NlbnRpYWw8YnI+DQo8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgRm9yIHdoYXQ/PGJyPg0KPGJyPg0KJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEkgdGhpbmsgd2Ugd291bGQgYWxsIGJlbmVmaXQgaWYgeW91
IGNvdWxkIGV4cGxhaW4geW91ciB1c2UgY2FzZS48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgR3LDvMOfZSwgQ2Fyc3Rlbjxicj4NCjxicj4NCjxicj4NCjxicj4NCiZuYnNw
OyAmbmJzcDsgLS0gPGJyPg0KJm5ic3A7ICZuYnNwOyBqc29uLWNhbm9uIG1haWxpbmcgbGlzdDxi
cj4NCiZuYnNwOyAmbmJzcDsgPGEgaHJlZj0ibWFpbHRvOmpzb24tY2Fub25AaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj5qc29uLWNhbm9uQGlldGYub3JnPC9hPjxicj4NCiZuYnNwOyAmbmJzcDsg
PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9qc29uLWNhbm9u
IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9q
c29uLWNhbm9uPC9hPjxicj4NCjxicj4NCjxicj4NCi0tIDxicj4NCmpzb24tY2Fub24gbWFpbGlu
ZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOmpzb24tY2Fub25AaWV0Zi5vcmciIHRhcmdldD0i
X2JsYW5rIj5qc29uLWNhbm9uQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vanNvbi1jYW5vbiIgdGFyZ2V0PSJfYmxhbmsiPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vanNvbi1jYW5vbjwvYT48bzpwPjwv
bzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_866D8EB849F64353B502F3337ACDBF61lookingglasscybercom_--


From nobody Tue Jan 22 10:05:54 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 AD881128CB7 for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 10:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 x18Bwtx9XB3H for <json-canon@ietfa.amsl.com>; Tue, 22 Jan 2019 10:05:50 -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 991091277BB for <json-canon@ietf.org>; Tue, 22 Jan 2019 10:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x0MI5e4Y009610; Tue, 22 Jan 2019 19:05:46 +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 43kbtr4vk1z1Br6; Tue, 22 Jan 2019 19:05:40 +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: <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org>
Date: Tue, 22 Jan 2019 19:05:39 +0100
Cc: "json-canon@ietf.org" <json-canon@ietf.org>
X-Mao-Original-Outgoing-Id: 569873136.7985311-1f39d5313b8078dbdb333ae7654c73a7
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org>
To: "Struse, Richard J." <rjs@mitre.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/zvqPMD4gf87tWUSNfOqy1rr56XI>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 22 Jan 2019 18:05:53 -0000

Hi Richard,

> On Jan 22, 2019, at 13:31, Struse, Richard J. <rjs@mitre.org> wrote:
>=20
> The use case is to enable other standards that use a JSON =
serialization to be able to count on two objects, each with the same =
contents, having the same hash value based on their representation in =
JSON.

Well, that is the technical requirement, but what do you use this =
property for?

JSON was discovered/presented around 2002 and so far has worked quite =
well without this property.  What use cases have sprung up that now need =
it?

I=E2=80=99m asking because for many use cases I have heard, there =
actually are better technical approaches than canonicalization.  Having =
said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts.  One =
thing we found out quickly is that deterministic encoding is dependent =
on the application concept of equality, so it is hard to define a single =
variant of it for a serialization used in multiple applications.  One =
more reason to find out about use cases.

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


From nobody Wed Jan 23 01:27:57 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 109AE130E76 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 01:27:56 -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 KTdIY9acAAcV for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 01:27:53 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 3B30F130E6E for <json-canon@ietf.org>; Wed, 23 Jan 2019 01:27:53 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id g22so1114603edr.7 for <json-canon@ietf.org>; Wed, 23 Jan 2019 01:27:53 -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=kuBMTprt+u5fcSZUDjXGiEMpMiyQv23Db4/WZdeB92c=; b=T+BfsKk8CCo68A1KCv5JGQr3pn+E937indhWRA6bx5brFP8901FvsLoMX3ySuyECIy 9pLL5o5CiIhku0p3wQLTlIpaa8Tond1Anrfchra+kubUDKyK+Y04jHZ6X7p+ZLlIq169 8lUgfkQ9YRPJu+RlChEvaAIrQbRmJLzWQ5QzKD9I3WbGVmwjc9X9yPKBex7cONALl6z3 gSdRKw+kypMeHaLO5S0NkQxn3tk8bYLZXw9dcbdCbai/Y8XL8nrZbqtyLO8PNePKXkj2 0nb5N5N32SuCT8IJlN9EFGPOK7KELvcIkpf03LwYxQTmQ3kQUsMz85R1lPmPYQ47IU/V 3A7w==
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=kuBMTprt+u5fcSZUDjXGiEMpMiyQv23Db4/WZdeB92c=; b=JB2VtMafMv8T517gNF+c4BcsffxpqvUAPvoZTecr/DisXafcHdOYb1tLVPtPWpuLak Q2apwsv7RFY7CvdR8Nplj/a3JHqoQMmMx4+BhutuBgGiqB1c0snegM+PFHk0ZvFjaSjz FHt96r6RX+Gr6R51WQZ3m/0dnH9s8l8v2hkdw3ItgcpGyf5E/0BIFDjRlS3eRLGxcfLw d71qxovA6eLVt94WnnCOHp0O/r92orSL2yRdkVALq/yFE3MSe2o0MymjseZe7mZPv8lb 3E5wX9zyILaTBIejbupyAuAmBklzqC1k7OFc2TDJcU8Lxta4Qqts9C8nF+q1fIgR1o5n 4ggQ==
X-Gm-Message-State: AJcUukexuDAzdSNMzVh5b3+awGTYHJljboxyxVd7QrjHLjNccUO0IptW DumGfpT0yViF40+X/XGFsT8J9ICW
X-Google-Smtp-Source: ALg8bN7CqZLTaET4VeAhNDhGdVQcHh2p3EN8gXVQiDfKZFAnkr2OClGODwLRsnfixQBOlL33hXb4CA==
X-Received: by 2002:a50:d1d4:: with SMTP id i20mr1985696edg.268.1548235671647;  Wed, 23 Jan 2019 01:27:51 -0800 (PST)
Received: from [156.106.225.150] ([156.106.225.150]) by smtp.gmail.com with ESMTPSA id t24sm10246154edb.7.2019.01.23.01.27.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jan 2019 01:27:50 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <00243004-7200-4887-BB46-ED30D03C4545@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A150DC7E-3E9B-478A-9507-0B079540EC83"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 23 Jan 2019 10:27:37 +0100
In-Reply-To: <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org>
Cc: Richard Struse <rjs@mitre.org>, "json-canon@ietf.org" <json-canon@ietf.org>
To: Carsten Bormann <cabo@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/3X7CTTNMU7I8HinO3bMMYZOUipw>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 23 Jan 2019 09:27:56 -0000

--Apple-Mail=_A150DC7E-3E9B-478A-9507-0B079540EC83
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Carsten,

I do not see what the hang up is for doing this. There is a document =
that proposes a very nice solution.  There are libraries for various =
programming languages that can do this.  What we need is a standard that =
people can reference when they want to use it.  At the end of the day =
people, organizations, vendors, and groups need a way of dealing with =
white space, ordering, and the JSON Number type in a consistent way.  =
They do not want to use CBOR, ASN.1, XML, or anything else.  The market =
wants to use plain and simple JSON. Right now we have various groups and =
organizations going off and doing their own form of this. It will save a =
lot of pain if we could just, finally, standardize this.=20

Lets not make this overly complicated.  Organizations, vendors, other =
standards, and other working groups want the ability to use JSON =
=E2=80=9Cas-is=E2=80=9D and perform security operations on that string =
of data.  To do this, we need a canonical string of data that can be =
consistently generated.  =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 Jan 22, 2019, at 7:05 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> Hi Richard,
>=20
>> On Jan 22, 2019, at 13:31, Struse, Richard J. <rjs@mitre.org> wrote:
>>=20
>> The use case is to enable other standards that use a JSON =
serialization to be able to count on two objects, each with the same =
contents, having the same hash value based on their representation in =
JSON.
>=20
> Well, that is the technical requirement, but what do you use this =
property for?
>=20
> JSON was discovered/presented around 2002 and so far has worked quite =
well without this property.  What use cases have sprung up that now need =
it?
>=20
> I=E2=80=99m asking because for many use cases I have heard, there =
actually are better technical approaches than canonicalization.  Having =
said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts.  One =
thing we found out quickly is that deterministic encoding is dependent =
on the application concept of equality, so it is hard to define a single =
variant of it for a serialization used in multiple applications.  One =
more reason to find out about use cases.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> --=20
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon


--Apple-Mail=_A150DC7E-3E9B-478A-9507-0B079540EC83
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""><div =
class=3D"">Carsten,</div><div class=3D""><br class=3D""></div><div =
class=3D"">I do not see what the hang up is for doing this. There is a =
document that proposes a very nice solution. &nbsp;There are libraries =
for various programming languages that can do this. &nbsp;What we need =
is a standard that people can reference when they want to use it. =
&nbsp;At the end of the day people, organizations, vendors, and groups =
need a way of dealing with white space, ordering, and the JSON Number =
type in a consistent way. &nbsp;They do not want to use CBOR, ASN.1, =
XML, or anything else. &nbsp;The market wants to use plain and simple =
JSON. Right now we have various groups and organizations going off and =
doing their own form of this. It will save a lot of pain if we could =
just, finally, standardize this.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Lets not make this overly complicated. =
&nbsp;Organizations, vendors, other standards, and other working groups =
want the ability to use JSON =E2=80=9Cas-is=E2=80=9D and perform =
security operations on that string of data. &nbsp;To do this, we need a =
canonical string of data that can be consistently generated. =
&nbsp;&nbsp;</div><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><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 22, 2019, at 7:05 PM, 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"">Hi Richard,<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">On Jan 22, 2019, at 13:31, Struse, Richard J. =
&lt;<a href=3D"mailto:rjs@mitre.org" class=3D"">rjs@mitre.org</a>&gt; =
wrote:<br class=3D""><br class=3D"">The use case is to enable other =
standards that use a JSON serialization to be able to count on two =
objects, each with the same contents, having the same hash value based =
on their representation in JSON.<br class=3D""></blockquote><br =
class=3D"">Well, that is the technical requirement, but what do you use =
this property for?<br class=3D""><br class=3D"">JSON was =
discovered/presented around 2002 and so far has worked quite well =
without this property. &nbsp;What use cases have sprung up that now need =
it?<br class=3D""><br class=3D"">I=E2=80=99m asking because for many use =
cases I have heard, there actually are better technical approaches than =
canonicalization. &nbsp;Having said that, CBOR, a data format defined in =
2013, does have recommendations for deterministic encoding =
(=E2=80=9Ccanonicalization=E2=80=9D), which turned out to be useful for =
instance for test scripts. &nbsp;One thing we found out quickly is that =
deterministic encoding is dependent on the application concept of =
equality, so it is hard to define a single variant of it for a =
serialization used in multiple applications. &nbsp;One more reason to =
find out about use cases.<br class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe, =
Carsten<br class=3D""><br class=3D"">-- <br class=3D"">json-canon =
mailing list<br class=3D""><a href=3D"mailto:json-canon@ietf.org" =
class=3D"">json-canon@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/json-canon<br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_A150DC7E-3E9B-478A-9507-0B079540EC83--


From nobody Wed Jan 23 02:32:44 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 D156C124BAA for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 02:32:42 -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 Egdpdtt5kQq0 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 02:32:40 -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 01996124B0C for <json-canon@ietf.org>; Wed, 23 Jan 2019 02:32:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x0NAWUvh009390; Wed, 23 Jan 2019 11:32:35 +0100 (CET)
Received: from [192.168.217.116] (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 43l1nT63kDz1Br7; Wed, 23 Jan 2019 11:32:29 +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: <00243004-7200-4887-BB46-ED30D03C4545@gmail.com>
Date: Wed, 23 Jan 2019 11:32:28 +0100
Cc: Richard Struse <rjs@mitre.org>, "json-canon@ietf.org" <json-canon@ietf.org>
X-Mao-Original-Outgoing-Id: 569932347.21298-1682395256a043673ef712aa871b4368
Content-Transfer-Encoding: quoted-printable
Message-Id: <40731AB0-9640-4D74-99B3-EC6E7A51850B@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org> <00243004-7200-4887-BB46-ED30D03C4545@gmail.com>
To: Bret Jordan <jordan.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/ex5m9azJIQXAEtk4tuHTtF8NMMY>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 23 Jan 2019 10:32:43 -0000

Hi Bret,

I=E2=80=99ve been in your shoes.
=E2=80=9CIt=E2=80=99s not that complicated.=E2=80=9D  Yeah.

Allan already hinted at one possible complication.
You can of course declare that (very real!) issue out of scope.
But that is easier done if we know why we are doing this.

What=E2=80=99s so difficult about actually saying what the use cases =
are?
I=E2=80=99m not trying to suggest there needs to be an RFC that =
documents every single use case before there can be any work on the =
solution (I=E2=80=99m saying this because unfortunately we have had =
process hangups like this before and there simply is no need for this).
Instead, this mailing list is a great place to have some discussion on =
the use cases so the requirements are better understood.
=E2=80=9CWe want this because some people are telling us it=E2=80=99s =
easy=E2=80=9D is not the level of discussion that can help with this.

On the solution side, having a solution but not having a well-understood =
description of what it does and what it does not is dangerous.  Even =
more so when some of the use cases have security considerations.

After all, the IETF would not be doing this solution as an ultimate goal =
=E2=80=94 the point is that other protocols can build on top of this =
solution, and as we want to achieve interoperability (and maintain =
security), we need to know what the solution does and what requirements =
it places on its usage to actually achieve its desired properties.

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


> On Jan 23, 2019, at 10:27, Bret Jordan <jordan.ietf@gmail.com> wrote:
>=20
> Carsten,
>=20
> I do not see what the hang up is for doing this. There is a document =
that proposes a very nice solution.  There are libraries for various =
programming languages that can do this.  What we need is a standard that =
people can reference when they want to use it.  At the end of the day =
people, organizations, vendors, and groups need a way of dealing with =
white space, ordering, and the JSON Number type in a consistent way.  =
They do not want to use CBOR, ASN.1, XML, or anything else.  The market =
wants to use plain and simple JSON. Right now we have various groups and =
organizations going off and doing their own form of this. It will save a =
lot of pain if we could just, finally, standardize this.=20
>=20
> Lets not make this overly complicated.  Organizations, vendors, other =
standards, and other working groups want the ability to use JSON =
=E2=80=9Cas-is=E2=80=9D and perform security operations on that string =
of data.  To do this, we need a canonical string of data that can be =
consistently generated.  =20
>=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
>> On Jan 22, 2019, at 7:05 PM, Carsten Bormann <cabo@tzi.org> wrote:
>>=20
>> Hi Richard,
>>=20
>>> On Jan 22, 2019, at 13:31, Struse, Richard J. <rjs@mitre.org> wrote:
>>>=20
>>> The use case is to enable other standards that use a JSON =
serialization to be able to count on two objects, each with the same =
contents, having the same hash value based on their representation in =
JSON.
>>=20
>> Well, that is the technical requirement, but what do you use this =
property for?
>>=20
>> JSON was discovered/presented around 2002 and so far has worked quite =
well without this property.  What use cases have sprung up that now need =
it?
>>=20
>> I=E2=80=99m asking because for many use cases I have heard, there =
actually are better technical approaches than canonicalization.  Having =
said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts.  One =
thing we found out quickly is that deterministic encoding is dependent =
on the application concept of equality, so it is hard to define a single =
variant of it for a serialization used in multiple applications.  One =
more reason to find out about use cases.
>>=20
>> Gr=C3=BC=C3=9Fe, Carsten
>>=20
>> --=20
>> json-canon mailing list
>> json-canon@ietf.org
>> https://www.ietf.org/mailman/listinfo/json-canon
>=20
> --=20
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon


From nobody Wed Jan 23 02:48:16 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 DB639130E46 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 02:48:14 -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 l4AV6R6rLGoE for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 02:48:12 -0800 (PST)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 7EC2B12E04D for <json-canon@ietf.org>; Wed, 23 Jan 2019 02:48:11 -0800 (PST)
Received: by mail-ed1-x52d.google.com with SMTP id a20so1295024edc.8 for <json-canon@ietf.org>; Wed, 23 Jan 2019 02:48:11 -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=+/Afg/bc1u0unQPu6PxMV1mRhkLC/Pb0fhjVOcRfXRs=; b=b1QWSQjihTo9xJ6b7q8X68H1pE8147jiM+g4raJ1ILl/efZU1jHOe17UgEqB7lomCA nytfAxqdCvnHGH8GujZIvSh2gxuzKyS74KM3fM88OnDLlCy6zcJnq+kbzNZl1igIgaGN owN+8zV3TkCE80GvOMR+4A/JmKkeK6IE3uf+dzXrZmQZpqSxwFjVA3KiCMq8Ko12vG7U X28e2lxMPEIVbPtRgzTYSEHs3Mbb5Sz9mVZyUkDffrmbrsofTaPVNEeM7M4Xx99GiHT2 ICvv02jNNp2nseg1z0TK2L0HmdsotazEvFA30xaE+IdeimIoe1EvAtmz19Mq12gtvE9Q f3Nw==
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=+/Afg/bc1u0unQPu6PxMV1mRhkLC/Pb0fhjVOcRfXRs=; b=cX/UB9nLfFuf3P9YfmKnNPeHeOFXhuIWQFzVKZH2mPmaWlre8AJdLjEY7LSkyRx5xy LJhw+UFOwvOUA1YbXe3sqtfsrM21FddSNrNXCyuZAeheWVuxmhiweHVKp7sqn4drAZaW qLGms3IpdvTWZr7MIdcKojwaInJjbkKifK7DXYQts14ZwK0DEGkmPzcvQcHzWjbV+dxn GZ1T8yvbqhrwKL/oBObW/K/VslX9cyLsaBw8xsZsUXF/HXX+nxoALQkvhYzMYLlFxGCk DRiflRO0oxDyMHxMLfaK3yU0odmeSkINj5JA70h8Y/0KFwiKJrMQtZzUwkR2K+dXlSO6 FnJw==
X-Gm-Message-State: AJcUukdW2qn6ZhlW8oIUHbwX3gvvHJkX3ffkts0oCFRPcq3w2h5WofTM JChvztBensmiEMjQvfhEpjh0tA2p
X-Google-Smtp-Source: ALg8bN5w6C7y6ss3QORfAIHWA8PAW7YJmlfJm6LpshkBfCy9RdANcXye2XJl8m31a1s0qvWavx3jLA==
X-Received: by 2002:a50:afa3:: with SMTP id h32mr2222333edd.150.1548240489792;  Wed, 23 Jan 2019 02:48:09 -0800 (PST)
Received: from [156.106.225.150] ([156.106.225.150]) by smtp.gmail.com with ESMTPSA id i46sm10156373eda.37.2019.01.23.02.48.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jan 2019 02:48:09 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <FA88BB03-ADA7-49EB-AE71-7750BFE71013@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4EFC3AE0-8BDC-4252-AA4A-5E98EC757240"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 23 Jan 2019 11:47:56 +0100
In-Reply-To: <40731AB0-9640-4D74-99B3-EC6E7A51850B@tzi.org>
Cc: Richard Struse <rjs@mitre.org>, "json-canon@ietf.org" <json-canon@ietf.org>
To: Carsten Bormann <cabo@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org> <00243004-7200-4887-BB46-ED30D03C4545@gmail.com> <40731AB0-9640-4D74-99B3-EC6E7A51850B@tzi.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/ABee9TTf7afsUSlORQOH0ir8aBs>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 23 Jan 2019 10:48:15 -0000

--Apple-Mail=_4EFC3AE0-8BDC-4252-AA4A-5E98EC757240
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Carsten,

Here are two examples=E2=80=A6

1) Creating deterministic IDs for STIX Cyber Observables.  STIX Cyber =
Observables are simple JSON blobs (think network traffic, file data, =
email data, etc) of data and we define for each object what properties =
should be used for the ID.  And when you build out your graph, you do =
not want a million vertices for the same thing.  You want to be able to =
just relate things together in a deterministic way.=20

So say you have something super super simple like this file object:

{
  "type": "file",
  "hashes": {
    "SHA-256": =
"fe90a7e910cb3a4739bed9180e807e93fa70c90f25a8915476f5e4bfbac681db"
  },
  "size": 25536,
  "name": "foo.dll"
}

You would want to be able to treat this as a string that you could pipe =
in to some hashing algorithm.  So you would want something like this:

Id :=3D Sha256hash(<JSON DATA>)


2) Creating digital signatures for JSON objects using the JSON data =
=E2=80=9Cas-is=E2=80=9D. =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 Jan 23, 2019, at 11:32 AM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> Hi Bret,
>=20
> I=E2=80=99ve been in your shoes.
> =E2=80=9CIt=E2=80=99s not that complicated.=E2=80=9D  Yeah.
>=20
> Allan already hinted at one possible complication.
> You can of course declare that (very real!) issue out of scope.
> But that is easier done if we know why we are doing this.
>=20
> What=E2=80=99s so difficult about actually saying what the use cases =
are?
> I=E2=80=99m not trying to suggest there needs to be an RFC that =
documents every single use case before there can be any work on the =
solution (I=E2=80=99m saying this because unfortunately we have had =
process hangups like this before and there simply is no need for this).
> Instead, this mailing list is a great place to have some discussion on =
the use cases so the requirements are better understood.
> =E2=80=9CWe want this because some people are telling us it=E2=80=99s =
easy=E2=80=9D is not the level of discussion that can help with this.
>=20
> On the solution side, having a solution but not having a =
well-understood description of what it does and what it does not is =
dangerous.  Even more so when some of the use cases have security =
considerations.
>=20
> After all, the IETF would not be doing this solution as an ultimate =
goal =E2=80=94 the point is that other protocols can build on top of =
this solution, and as we want to achieve interoperability (and maintain =
security), we need to know what the solution does and what requirements =
it places on its usage to actually achieve its desired properties.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
>=20
>> On Jan 23, 2019, at 10:27, Bret Jordan <jordan.ietf@gmail.com> wrote:
>>=20
>> Carsten,
>>=20
>> I do not see what the hang up is for doing this. There is a document =
that proposes a very nice solution.  There are libraries for various =
programming languages that can do this.  What we need is a standard that =
people can reference when they want to use it.  At the end of the day =
people, organizations, vendors, and groups need a way of dealing with =
white space, ordering, and the JSON Number type in a consistent way.  =
They do not want to use CBOR, ASN.1, XML, or anything else.  The market =
wants to use plain and simple JSON. Right now we have various groups and =
organizations going off and doing their own form of this. It will save a =
lot of pain if we could just, finally, standardize this.=20
>>=20
>> Lets not make this overly complicated.  Organizations, vendors, other =
standards, and other working groups want the ability to use JSON =
=E2=80=9Cas-is=E2=80=9D and perform security operations on that string =
of data.  To do this, we need a canonical string of data that can be =
consistently generated.  =20
>>=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
>>> On Jan 22, 2019, at 7:05 PM, Carsten Bormann <cabo@tzi.org> wrote:
>>>=20
>>> Hi Richard,
>>>=20
>>>> On Jan 22, 2019, at 13:31, Struse, Richard J. <rjs@mitre.org> =
wrote:
>>>>=20
>>>> The use case is to enable other standards that use a JSON =
serialization to be able to count on two objects, each with the same =
contents, having the same hash value based on their representation in =
JSON.
>>>=20
>>> Well, that is the technical requirement, but what do you use this =
property for?
>>>=20
>>> JSON was discovered/presented around 2002 and so far has worked =
quite well without this property.  What use cases have sprung up that =
now need it?
>>>=20
>>> I=E2=80=99m asking because for many use cases I have heard, there =
actually are better technical approaches than canonicalization.  Having =
said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts.  One =
thing we found out quickly is that deterministic encoding is dependent =
on the application concept of equality, so it is hard to define a single =
variant of it for a serialization used in multiple applications.  One =
more reason to find out about use cases.
>>>=20
>>> Gr=C3=BC=C3=9Fe, Carsten
>>>=20
>>> --=20
>>> json-canon mailing list
>>> json-canon@ietf.org
>>> https://www.ietf.org/mailman/listinfo/json-canon
>>=20
>> --=20
>> json-canon mailing list
>> json-canon@ietf.org
>> https://www.ietf.org/mailman/listinfo/json-canon
>=20


--Apple-Mail=_4EFC3AE0-8BDC-4252-AA4A-5E98EC757240
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"">Carsten,<div class=3D""><br class=3D""></div><div =
class=3D"">Here are two examples=E2=80=A6</div><div class=3D""><br =
class=3D""></div><div class=3D"">1) Creating deterministic IDs for STIX =
Cyber Observables. &nbsp;STIX Cyber Observables are simple JSON blobs =
(think network traffic, file data, email data, etc) of data and we =
define for each object what properties should be used for the ID. =
&nbsp;And when you build out your graph, you do not want a million =
vertices for the same thing. &nbsp;You want to be able to just relate =
things together in a deterministic way.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">So say you have something super super =
simple like this file object:</div><div class=3D""><br =
class=3D""></div><div class=3D"">{<br class=3D"">&nbsp; "type": =
"file",<br class=3D"">&nbsp; "hashes": {<br class=3D"">&nbsp; &nbsp; =
"SHA-256": =
"fe90a7e910cb3a4739bed9180e807e93fa70c90f25a8915476f5e4bfbac681db"<br =
class=3D"">&nbsp; },<br class=3D"">&nbsp; "size": 25536,<br =
class=3D"">&nbsp; "name": "foo.dll"<br class=3D"">}<br class=3D""><br =
class=3D""></div><div class=3D"">You would want to be able to treat this =
as a string that you could pipe in to some hashing algorithm. &nbsp;So =
you would want something like this:</div><div class=3D""><br =
class=3D""></div><div class=3D"">Id :=3D Sha256hash(&lt;JSON =
DATA&gt;)</div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">2) Creating digital signatures for JSON =
objects using the JSON data =E2=80=9Cas-is=E2=80=9D. &nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D""><br class=3D""></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;">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><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 23, 2019, at 11:32 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"">Hi Bret,<br class=3D""><br class=3D"">I=E2=80=99ve been in =
your shoes.<br class=3D"">=E2=80=9CIt=E2=80=99s not that complicated.=E2=80=
=9D &nbsp;Yeah.<br class=3D""><br class=3D"">Allan already hinted at one =
possible complication.<br class=3D"">You can of course declare that =
(very real!) issue out of scope.<br class=3D"">But that is easier done =
if we know why we are doing this.<br class=3D""><br class=3D"">What=E2=80=99=
s so difficult about actually saying what the use cases are?<br =
class=3D"">I=E2=80=99m not trying to suggest there needs to be an RFC =
that documents every single use case before there can be any work on the =
solution (I=E2=80=99m saying this because unfortunately we have had =
process hangups like this before and there simply is no need for =
this).<br class=3D"">Instead, this mailing list is a great place to have =
some discussion on the use cases so the requirements are better =
understood.<br class=3D"">=E2=80=9CWe want this because some people are =
telling us it=E2=80=99s easy=E2=80=9D is not the level of discussion =
that can help with this.<br class=3D""><br class=3D"">On the solution =
side, having a solution but not having a well-understood description of =
what it does and what it does not is dangerous. &nbsp;Even more so when =
some of the use cases have security considerations.<br class=3D""><br =
class=3D"">After all, the IETF would not be doing this solution as an =
ultimate goal =E2=80=94 the point is that other protocols can build on =
top of this solution, and as we want to achieve interoperability (and =
maintain security), we need to know what the solution does and what =
requirements it places on its usage to actually achieve its desired =
properties.<br class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe, Carsten<br =
class=3D""><br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">On Jan 23, 2019, at 10:27, Bret Jordan &lt;<a =
href=3D"mailto:jordan.ietf@gmail.com" =
class=3D"">jordan.ietf@gmail.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">Carsten,<br class=3D""><br class=3D"">I do not see what the =
hang up is for doing this. There is a document that proposes a very nice =
solution. &nbsp;There are libraries for various programming languages =
that can do this. &nbsp;What we need is a standard that people can =
reference when they want to use it. &nbsp;At the end of the day people, =
organizations, vendors, and groups need a way of dealing with white =
space, ordering, and the JSON Number type in a consistent way. =
&nbsp;They do not want to use CBOR, ASN.1, XML, or anything else. =
&nbsp;The market wants to use plain and simple JSON. Right now we have =
various groups and organizations going off and doing their own form of =
this. It will save a lot of pain if we could just, finally, standardize =
this. <br class=3D""><br class=3D"">Lets not make this overly =
complicated. &nbsp;Organizations, vendors, other standards, and other =
working groups want the ability to use JSON =E2=80=9Cas-is=E2=80=9D and =
perform security operations on that string of data. &nbsp;To do this, we =
need a canonical string of data that can be consistently generated. =
&nbsp;&nbsp;<br class=3D""><br class=3D"">Thanks,<br class=3D"">Bret<br =
class=3D"">PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 &nbsp;F2C0 74F8 =
ACAE 7415 0050<br class=3D"">"Without cryptography vihv vivc ce xhrnrw, =
however, the only thing that can not be unscrambled is an egg."<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On Jan =
22, 2019, at 7:05 PM, Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org" =
class=3D"">cabo@tzi.org</a>&gt; wrote:<br class=3D""><br class=3D"">Hi =
Richard,<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">On Jan 22, 2019, at 13:31, Struse, Richard J. &lt;<a =
href=3D"mailto:rjs@mitre.org" class=3D"">rjs@mitre.org</a>&gt; wrote:<br =
class=3D""><br class=3D"">The use case is to enable other standards that =
use a JSON serialization to be able to count on two objects, each with =
the same contents, having the same hash value based on their =
representation in JSON.<br class=3D""></blockquote><br class=3D"">Well, =
that is the technical requirement, but what do you use this property =
for?<br class=3D""><br class=3D"">JSON was discovered/presented around =
2002 and so far has worked quite well without this property. &nbsp;What =
use cases have sprung up that now need it?<br class=3D""><br =
class=3D"">I=E2=80=99m asking because for many use cases I have heard, =
there actually are better technical approaches than canonicalization. =
&nbsp;Having said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts. =
&nbsp;One thing we found out quickly is that deterministic encoding is =
dependent on the application concept of equality, so it is hard to =
define a single variant of it for a serialization used in multiple =
applications. &nbsp;One more reason to find out about use cases.<br =
class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe, Carsten<br class=3D""><br =
class=3D"">-- <br class=3D"">json-canon mailing list<br class=3D""><a =
href=3D"mailto:json-canon@ietf.org" class=3D"">json-canon@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/json-canon<br =
class=3D""></blockquote><br class=3D"">-- <br class=3D"">json-canon =
mailing list<br class=3D""><a href=3D"mailto:json-canon@ietf.org" =
class=3D"">json-canon@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/json-canon<br =
class=3D""></blockquote><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_4EFC3AE0-8BDC-4252-AA4A-5E98EC757240--


From nobody Wed Jan 23 04:23:03 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 1214512DF71 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 04:23:02 -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 KLVXXdjvupO4 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 04:23:00 -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 DDF8D128CE4 for <json-canon@ietf.org>; Wed, 23 Jan 2019 04:22:59 -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 x0NCMnOi004135; Wed, 23 Jan 2019 13:22:54 +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 43l4Dn297jz1Br6; Wed, 23 Jan 2019 13:22:49 +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: <FA88BB03-ADA7-49EB-AE71-7750BFE71013@gmail.com>
Date: Wed, 23 Jan 2019 13:22:48 +0100
Cc: Richard Struse <rjs@mitre.org>, "json-canon@ietf.org" <json-canon@ietf.org>
X-Mao-Original-Outgoing-Id: 569938966.496702-23d1621dde10c882ad5f4363d5773098
Content-Transfer-Encoding: quoted-printable
Message-Id: <100898B7-CCA6-4B00-895F-AD39AAAEF052@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org> <00243004-7200-4887-BB46-ED30D03C4545@gmail.com> <40731AB0-9640-4D74-99B3-EC6E7A51850B@tzi.org> <FA88BB03-ADA7-49EB-AE71-7750BFE71013@gmail.com>
To: Bret Jordan <jordan.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/Px9noQZRvEvTJ7pNNbfP6hHxdTo>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 23 Jan 2019 12:23:02 -0000

Hi Bret,

> 1) Creating deterministic IDs for STIX Cyber Observables. =20

Now that is very concrete!  Thank you.
What would be the best reference I could use to learn how STIX uses =
JSON?

> 2) Creating digital signatures for JSON objects using the JSON data =
=E2=80=9Cas-is=E2=80=9D. =20

Right, that is one very general use case, but as Allan and I hinted, it =
may be worth looking at the JSON data in a bit more detail.  Using =
Richard=E2=80=99s problem statement:

=E2=80=9Ctwo objects, each with the same contents, having the same hash =
value based on their representation in JSON.=E2=80=9D

This has this gaping hole what =E2=80=9Csame contents=E2=80=9D actually =
mean.
So far, I-JSON (RFC 7493) is the closest we have to a specification of =
the generic data model with which we are using JSON as an interchange =
format.
Maybe that is all we need, but that remains to be verified =E2=80=94 =
best in the context of the applications that actually have a concept of =
what =E2=80=9Csame contents=E2=80=9D would be.

So I still think analyzing a few applications would be a good thing =
before we can claim the generic use case (2) is covered.

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


>=20
>=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
>> On Jan 23, 2019, at 11:32 AM, Carsten Bormann <cabo@tzi.org> wrote:
>>=20
>> Hi Bret,
>>=20
>> I=E2=80=99ve been in your shoes.
>> =E2=80=9CIt=E2=80=99s not that complicated.=E2=80=9D  Yeah.
>>=20
>> Allan already hinted at one possible complication.
>> You can of course declare that (very real!) issue out of scope.
>> But that is easier done if we know why we are doing this.
>>=20
>> What=E2=80=99s so difficult about actually saying what the use cases =
are?
>> I=E2=80=99m not trying to suggest there needs to be an RFC that =
documents every single use case before there can be any work on the =
solution (I=E2=80=99m saying this because unfortunately we have had =
process hangups like this before and there simply is no need for this).
>> Instead, this mailing list is a great place to have some discussion =
on the use cases so the requirements are better understood.
>> =E2=80=9CWe want this because some people are telling us it=E2=80=99s =
easy=E2=80=9D is not the level of discussion that can help with this.
>>=20
>> On the solution side, having a solution but not having a =
well-understood description of what it does and what it does not is =
dangerous.  Even more so when some of the use cases have security =
considerations.
>>=20
>> After all, the IETF would not be doing this solution as an ultimate =
goal =E2=80=94 the point is that other protocols can build on top of =
this solution, and as we want to achieve interoperability (and maintain =
security), we need to know what the solution does and what requirements =
it places on its usage to actually achieve its desired properties.
>>=20
>> Gr=C3=BC=C3=9Fe, Carsten
>>=20
>>=20
>>> On Jan 23, 2019, at 10:27, Bret Jordan <jordan.ietf@gmail.com> =
wrote:
>>>=20
>>> Carsten,
>>>=20
>>> I do not see what the hang up is for doing this. There is a document =
that proposes a very nice solution.  There are libraries for various =
programming languages that can do this.  What we need is a standard that =
people can reference when they want to use it.  At the end of the day =
people, organizations, vendors, and groups need a way of dealing with =
white space, ordering, and the JSON Number type in a consistent way.  =
They do not want to use CBOR, ASN.1, XML, or anything else.  The market =
wants to use plain and simple JSON. Right now we have various groups and =
organizations going off and doing their own form of this. It will save a =
lot of pain if we could just, finally, standardize this.=20
>>>=20
>>> Lets not make this overly complicated.  Organizations, vendors, =
other standards, and other working groups want the ability to use JSON =
=E2=80=9Cas-is=E2=80=9D and perform security operations on that string =
of data.  To do this, we need a canonical string of data that can be =
consistently generated.  =20
>>>=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
>>>> On Jan 22, 2019, at 7:05 PM, Carsten Bormann <cabo@tzi.org> wrote:
>>>>=20
>>>> Hi Richard,
>>>>=20
>>>>> On Jan 22, 2019, at 13:31, Struse, Richard J. <rjs@mitre.org> =
wrote:
>>>>>=20
>>>>> The use case is to enable other standards that use a JSON =
serialization to be able to count on two objects, each with the same =
contents, having the same hash value based on their representation in =
JSON.
>>>>=20
>>>> Well, that is the technical requirement, but what do you use this =
property for?
>>>>=20
>>>> JSON was discovered/presented around 2002 and so far has worked =
quite well without this property.  What use cases have sprung up that =
now need it?
>>>>=20
>>>> I=E2=80=99m asking because for many use cases I have heard, there =
actually are better technical approaches than canonicalization.  Having =
said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts.  One =
thing we found out quickly is that deterministic encoding is dependent =
on the application concept of equality, so it is hard to define a single =
variant of it for a serialization used in multiple applications.  One =
more reason to find out about use cases.
>>>>=20
>>>> Gr=C3=BC=C3=9Fe, Carsten
>>>>=20
>>>> --=20
>>>> json-canon mailing list
>>>> json-canon@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>=20
>>> --=20
>>> json-canon mailing list
>>> json-canon@ietf.org
>>> https://www.ietf.org/mailman/listinfo/json-canon
>>=20
>=20
> --=20
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon


From nobody Wed Jan 23 05:09:32 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 2D73E126F72 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 05:09:31 -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 9J52eJGYkPG0 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 05:09:27 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 456DE1228B7 for <json-canon@ietf.org>; Wed, 23 Jan 2019 05:09:27 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id b3so1670472ede.1 for <json-canon@ietf.org>; Wed, 23 Jan 2019 05:09: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=PvxwcU3HbnqsdtCrsBObwNJaIJs7lWeJGp1Lqs2eFfY=; b=jsv+T9cyqiFYoJa7e1W4zKnS6qWX5iTrjA3bmDinjcsxT9GmDbvKExc1IbNX0y31oJ nfFXfjqnyKncTPNQ/tXJEIgFLkyL0R/MCF7V9ZOss8qUTJGIz7yqR+DYlpzSmbe1jPPU 9giJ9FlHjTKrRYap5OlDQl3SC7Z1MY+CupaPkOgvjCoPzPnB4+z1M/4tGbxm05UPI/pN /lNacoUVwRO5sPVsj4e8x6WCKuUVdy8/3WCYzM3QztO4PtdwFAHTkun9lZbFWB+1tGFr neAE2jfnPj1mylfOKevbBE1oEzeiFKPzqH66uK7q6Qsgf+gXEVYptBbVhtJYXfvJLh2w e5DA==
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=PvxwcU3HbnqsdtCrsBObwNJaIJs7lWeJGp1Lqs2eFfY=; b=c/Z6HJjUPDhD9oy2RcDKS7GbxrNp+1tt6tb8iIUuVIagOZ09Lzntf3MYaaEJeC0Ywr FBpnsI+n7Pr8kyNAoB0XV6Gm5Tju5tFJ9zmxY3HXe5Gsbxw/BE49rexWyZ3s5C4/LSrh NxuPXdWcHEIoF1Fz+qC7ekEcH02bcV9imDmw4VV7aos44QzgOpNBBRqIpgoSB8vWiWJm OyLmDpsGS+aP0Rz7SKFAFuBa2VUJwn3SaKdID+hHE/Lcd8Dx/QPWfLTsQoDLzLBsLqOY PlkgvvUejGDRgQU2W38fUi8DiJZ9xERj/XtqzZcwPJSklMVmk8yZEBG2l/2u9iJDoL9p VU9w==
X-Gm-Message-State: AJcUukfIHjVHRKyvLSFDgW7AA9GEEtXIhLBZTHg0KiOeGvr9thUPXHiw kWgR0QbbrlLLQZtqbM4LQCEC+KQx
X-Google-Smtp-Source: ALg8bN5RZ8uq4aIaj5OMk1+9I3+4TqjoooXx1BfmseiNOombGWi9EvHPFaDZY5QrCjaxs17NckGK0w==
X-Received: by 2002:a17:906:2287:: with SMTP id p7mr1584481eja.173.1548248965688;  Wed, 23 Jan 2019 05:09:25 -0800 (PST)
Received: from [156.106.225.150] ([156.106.225.150]) by smtp.gmail.com with ESMTPSA id p24sm6799ejz.46.2019.01.23.05.09.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jan 2019 05:09:24 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <A37C3DD6-65F9-4B6B-BCAC-FE0DCC10D1FB@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B0C11E98-54B8-4F99-82CE-BBEBE70022EF"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 23 Jan 2019 14:09:08 +0100
In-Reply-To: <100898B7-CCA6-4B00-895F-AD39AAAEF052@tzi.org>
Cc: "json-canon@ietf.org" <json-canon@ietf.org>
To: Carsten Bormann <cabo@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org> <00243004-7200-4887-BB46-ED30D03C4545@gmail.com> <40731AB0-9640-4D74-99B3-EC6E7A51850B@tzi.org> <FA88BB03-ADA7-49EB-AE71-7750BFE71013@gmail.com> <100898B7-CCA6-4B00-895F-AD39AAAEF052@tzi.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/fTD4AbwC25f1p1ZxARPD2k4PI70>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 23 Jan 2019 13:09:31 -0000

--Apple-Mail=_B0C11E98-54B8-4F99-82CE-BBEBE70022EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I would probably point you to this site that we put together. However, =
if there is something specific you would like to know, I can answer =
that.  Or we can schedule a WebEx and I can walk you through it.=20

https://oasis-open.github.io/cti-documentation/ =
<https://oasis-open.github.io/cti-documentation/>


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 Jan 23, 2019, at 1:22 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> Hi Bret,
>=20
>> 1) Creating deterministic IDs for STIX Cyber Observables. =20
>=20
> Now that is very concrete!  Thank you.
> What would be the best reference I could use to learn how STIX uses =
JSON?
>=20
>> 2) Creating digital signatures for JSON objects using the JSON data =
=E2=80=9Cas-is=E2=80=9D. =20
>=20
> Right, that is one very general use case, but as Allan and I hinted, =
it may be worth looking at the JSON data in a bit more detail.  Using =
Richard=E2=80=99s problem statement:
>=20
> =E2=80=9Ctwo objects, each with the same contents, having the same =
hash value based on their representation in JSON.=E2=80=9D
>=20
> This has this gaping hole what =E2=80=9Csame contents=E2=80=9D =
actually mean.
> So far, I-JSON (RFC 7493) is the closest we have to a specification of =
the generic data model with which we are using JSON as an interchange =
format.
> Maybe that is all we need, but that remains to be verified =E2=80=94 =
best in the context of the applications that actually have a concept of =
what =E2=80=9Csame contents=E2=80=9D would be.
>=20
> So I still think analyzing a few applications would be a good thing =
before we can claim the generic use case (2) is covered.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
>=20
>>=20
>>=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
>>> On Jan 23, 2019, at 11:32 AM, Carsten Bormann <cabo@tzi.org> wrote:
>>>=20
>>> Hi Bret,
>>>=20
>>> I=E2=80=99ve been in your shoes.
>>> =E2=80=9CIt=E2=80=99s not that complicated.=E2=80=9D  Yeah.
>>>=20
>>> Allan already hinted at one possible complication.
>>> You can of course declare that (very real!) issue out of scope.
>>> But that is easier done if we know why we are doing this.
>>>=20
>>> What=E2=80=99s so difficult about actually saying what the use cases =
are?
>>> I=E2=80=99m not trying to suggest there needs to be an RFC that =
documents every single use case before there can be any work on the =
solution (I=E2=80=99m saying this because unfortunately we have had =
process hangups like this before and there simply is no need for this).
>>> Instead, this mailing list is a great place to have some discussion =
on the use cases so the requirements are better understood.
>>> =E2=80=9CWe want this because some people are telling us it=E2=80=99s =
easy=E2=80=9D is not the level of discussion that can help with this.
>>>=20
>>> On the solution side, having a solution but not having a =
well-understood description of what it does and what it does not is =
dangerous.  Even more so when some of the use cases have security =
considerations.
>>>=20
>>> After all, the IETF would not be doing this solution as an ultimate =
goal =E2=80=94 the point is that other protocols can build on top of =
this solution, and as we want to achieve interoperability (and maintain =
security), we need to know what the solution does and what requirements =
it places on its usage to actually achieve its desired properties.
>>>=20
>>> Gr=C3=BC=C3=9Fe, Carsten
>>>=20
>>>=20
>>>> On Jan 23, 2019, at 10:27, Bret Jordan <jordan.ietf@gmail.com> =
wrote:
>>>>=20
>>>> Carsten,
>>>>=20
>>>> I do not see what the hang up is for doing this. There is a =
document that proposes a very nice solution.  There are libraries for =
various programming languages that can do this.  What we need is a =
standard that people can reference when they want to use it.  At the end =
of the day people, organizations, vendors, and groups need a way of =
dealing with white space, ordering, and the JSON Number type in a =
consistent way.  They do not want to use CBOR, ASN.1, XML, or anything =
else.  The market wants to use plain and simple JSON. Right now we have =
various groups and organizations going off and doing their own form of =
this. It will save a lot of pain if we could just, finally, standardize =
this.=20
>>>>=20
>>>> Lets not make this overly complicated.  Organizations, vendors, =
other standards, and other working groups want the ability to use JSON =
=E2=80=9Cas-is=E2=80=9D and perform security operations on that string =
of data.  To do this, we need a canonical string of data that can be =
consistently generated.  =20
>>>>=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
>>>>> On Jan 22, 2019, at 7:05 PM, Carsten Bormann <cabo@tzi.org> wrote:
>>>>>=20
>>>>> Hi Richard,
>>>>>=20
>>>>>> On Jan 22, 2019, at 13:31, Struse, Richard J. <rjs@mitre.org> =
wrote:
>>>>>>=20
>>>>>> The use case is to enable other standards that use a JSON =
serialization to be able to count on two objects, each with the same =
contents, having the same hash value based on their representation in =
JSON.
>>>>>=20
>>>>> Well, that is the technical requirement, but what do you use this =
property for?
>>>>>=20
>>>>> JSON was discovered/presented around 2002 and so far has worked =
quite well without this property.  What use cases have sprung up that =
now need it?
>>>>>=20
>>>>> I=E2=80=99m asking because for many use cases I have heard, there =
actually are better technical approaches than canonicalization.  Having =
said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts.  One =
thing we found out quickly is that deterministic encoding is dependent =
on the application concept of equality, so it is hard to define a single =
variant of it for a serialization used in multiple applications.  One =
more reason to find out about use cases.
>>>>>=20
>>>>> Gr=C3=BC=C3=9Fe, Carsten
>>>>>=20
>>>>> --=20
>>>>> json-canon mailing list
>>>>> json-canon@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>>=20
>>>> --=20
>>>> json-canon mailing list
>>>> json-canon@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>=20
>>=20
>> --=20
>> json-canon mailing list
>> json-canon@ietf.org
>> https://www.ietf.org/mailman/listinfo/json-canon
>=20


--Apple-Mail=_B0C11E98-54B8-4F99-82CE-BBEBE70022EF
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 =
would probably point you to this site that we put together. However, if =
there is something specific you would like to know, I can answer that. =
&nbsp;Or we can schedule a WebEx and I can walk you through =
it.&nbsp;<div class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://oasis-open.github.io/cti-documentation/" =
class=3D"">https://oasis-open.github.io/cti-documentation/</a></div><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><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 23, 2019, at 1:22 PM, 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"">Hi Bret,<br class=3D""><br class=3D""><blockquote type=3D"cite"=
 class=3D"">1) Creating deterministic IDs for STIX Cyber Observables. =
&nbsp;<br class=3D""></blockquote><br class=3D"">Now that is very =
concrete! &nbsp;Thank you.<br class=3D"">What would be the best =
reference I could use to learn how STIX uses JSON?<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">2) Creating digital =
signatures for JSON objects using the JSON data =E2=80=9Cas-is=E2=80=9D. =
&nbsp;<br class=3D""></blockquote><br class=3D"">Right, that is one very =
general use case, but as Allan and I hinted, it may be worth looking at =
the JSON data in a bit more detail. &nbsp;Using Richard=E2=80=99s =
problem statement:<br class=3D""><br class=3D"">=E2=80=9Ctwo objects, =
each with the same contents, having the same hash value based on their =
representation in JSON.=E2=80=9D<br class=3D""><br class=3D"">This has =
this gaping hole what =E2=80=9Csame contents=E2=80=9D actually mean.<br =
class=3D"">So far, I-JSON (RFC 7493) is the closest we have to a =
specification of the generic data model with which we are using JSON as =
an interchange format.<br class=3D"">Maybe that is all we need, but that =
remains to be verified =E2=80=94 best in the context of the applications =
that actually have a concept of what =E2=80=9Csame contents=E2=80=9D =
would be.<br class=3D""><br class=3D"">So I still think analyzing a few =
applications would be a good thing before we can claim the generic use =
case (2) is covered.<br class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe, =
Carsten<br class=3D""><br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D""><br class=3D"">Thanks,<br =
class=3D"">Bret<br class=3D"">PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 =
&nbsp;F2C0 74F8 ACAE 7415 0050<br class=3D"">"Without cryptography vihv =
vivc ce xhrnrw, however, the only thing that can not be unscrambled is =
an egg."<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">On Jan 23, 2019, at 11:32 AM, Carsten Bormann &lt;<a =
href=3D"mailto:cabo@tzi.org" class=3D"">cabo@tzi.org</a>&gt; wrote:<br =
class=3D""><br class=3D"">Hi Bret,<br class=3D""><br class=3D"">I=E2=80=99=
ve been in your shoes.<br class=3D"">=E2=80=9CIt=E2=80=99s not that =
complicated.=E2=80=9D &nbsp;Yeah.<br class=3D""><br class=3D"">Allan =
already hinted at one possible complication.<br class=3D"">You can of =
course declare that (very real!) issue out of scope.<br class=3D"">But =
that is easier done if we know why we are doing this.<br class=3D""><br =
class=3D"">What=E2=80=99s so difficult about actually saying what the =
use cases are?<br class=3D"">I=E2=80=99m not trying to suggest there =
needs to be an RFC that documents every single use case before there can =
be any work on the solution (I=E2=80=99m saying this because =
unfortunately we have had process hangups like this before and there =
simply is no need for this).<br class=3D"">Instead, this mailing list is =
a great place to have some discussion on the use cases so the =
requirements are better understood.<br class=3D"">=E2=80=9CWe want this =
because some people are telling us it=E2=80=99s easy=E2=80=9D is not the =
level of discussion that can help with this.<br class=3D""><br =
class=3D"">On the solution side, having a solution but not having a =
well-understood description of what it does and what it does not is =
dangerous. &nbsp;Even more so when some of the use cases have security =
considerations.<br class=3D""><br class=3D"">After all, the IETF would =
not be doing this solution as an ultimate goal =E2=80=94 the point is =
that other protocols can build on top of this solution, and as we want =
to achieve interoperability (and maintain security), we need to know =
what the solution does and what requirements it places on its usage to =
actually achieve its desired properties.<br class=3D""><br =
class=3D"">Gr=C3=BC=C3=9Fe, Carsten<br class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">On Jan 23, 2019, at =
10:27, Bret Jordan &lt;<a href=3D"mailto:jordan.ietf@gmail.com" =
class=3D"">jordan.ietf@gmail.com</a>&gt; wrote:<br class=3D""><br =
class=3D"">Carsten,<br class=3D""><br class=3D"">I do not see what the =
hang up is for doing this. There is a document that proposes a very nice =
solution. &nbsp;There are libraries for various programming languages =
that can do this. &nbsp;What we need is a standard that people can =
reference when they want to use it. &nbsp;At the end of the day people, =
organizations, vendors, and groups need a way of dealing with white =
space, ordering, and the JSON Number type in a consistent way. =
&nbsp;They do not want to use CBOR, ASN.1, XML, or anything else. =
&nbsp;The market wants to use plain and simple JSON. Right now we have =
various groups and organizations going off and doing their own form of =
this. It will save a lot of pain if we could just, finally, standardize =
this. <br class=3D""><br class=3D"">Lets not make this overly =
complicated. &nbsp;Organizations, vendors, other standards, and other =
working groups want the ability to use JSON =E2=80=9Cas-is=E2=80=9D and =
perform security operations on that string of data. &nbsp;To do this, we =
need a canonical string of data that can be consistently generated. =
&nbsp;&nbsp;<br class=3D""><br class=3D"">Thanks,<br class=3D"">Bret<br =
class=3D"">PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 &nbsp;F2C0 74F8 =
ACAE 7415 0050<br class=3D"">"Without cryptography vihv vivc ce xhrnrw, =
however, the only thing that can not be unscrambled is an egg."<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">On Jan =
22, 2019, at 7:05 PM, Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org" =
class=3D"">cabo@tzi.org</a>&gt; wrote:<br class=3D""><br class=3D"">Hi =
Richard,<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">On Jan 22, 2019, at 13:31, Struse, Richard J. &lt;<a =
href=3D"mailto:rjs@mitre.org" class=3D"">rjs@mitre.org</a>&gt; wrote:<br =
class=3D""><br class=3D"">The use case is to enable other standards that =
use a JSON serialization to be able to count on two objects, each with =
the same contents, having the same hash value based on their =
representation in JSON.<br class=3D""></blockquote><br class=3D"">Well, =
that is the technical requirement, but what do you use this property =
for?<br class=3D""><br class=3D"">JSON was discovered/presented around =
2002 and so far has worked quite well without this property. &nbsp;What =
use cases have sprung up that now need it?<br class=3D""><br =
class=3D"">I=E2=80=99m asking because for many use cases I have heard, =
there actually are better technical approaches than canonicalization. =
&nbsp;Having said that, CBOR, a data format defined in 2013, does have =
recommendations for deterministic encoding (=E2=80=9Ccanonicalization=E2=80=
=9D), which turned out to be useful for instance for test scripts. =
&nbsp;One thing we found out quickly is that deterministic encoding is =
dependent on the application concept of equality, so it is hard to =
define a single variant of it for a serialization used in multiple =
applications. &nbsp;One more reason to find out about use cases.<br =
class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe, Carsten<br class=3D""><br =
class=3D"">-- <br class=3D"">json-canon mailing list<br class=3D""><a =
href=3D"mailto:json-canon@ietf.org" class=3D"">json-canon@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/json-canon<br =
class=3D""></blockquote><br class=3D"">-- <br class=3D"">json-canon =
mailing list<br class=3D""><a href=3D"mailto:json-canon@ietf.org" =
class=3D"">json-canon@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/json-canon<br =
class=3D""></blockquote><br class=3D""></blockquote><br class=3D"">-- =
<br class=3D"">json-canon mailing list<br class=3D""><a =
href=3D"mailto:json-canon@ietf.org" class=3D"">json-canon@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/json-canon<br =
class=3D""></blockquote><br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_B0C11E98-54B8-4F99-82CE-BBEBE70022EF--


From nobody Wed Jan 23 05:10:54 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 78DC712D84C for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 05:10:53 -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 MbPqzCEdJKze for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 05:10:51 -0800 (PST)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 26D6C1228B7 for <json-canon@ietf.org>; Wed, 23 Jan 2019 05:10:51 -0800 (PST)
Received: by mail-ed1-x52a.google.com with SMTP id d39so1615484edb.12 for <json-canon@ietf.org>; Wed, 23 Jan 2019 05:10:51 -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=/v0RiuOhcBwo7Aw//P2T48vaJ7vo8HTktxW77o4SaDw=; b=JOKgk3qHoUYl+NpHQ3iH/wur4c5yubybrxZdUCpSQnPH4SxOJK6wIIaFEHPYLakaQL FTBoeq9+4zjAJgjC1fWDuDxjb+KIhnGU64ycTWinOoR4TVYJoiIas8asu5QLZ4wq/xC0 uWsjPMnJxGtww4W21YFz3JycBTuHdufQZgND9ulCqDjE9joYKoDNEDygcXsChcDBxV/y E2VEdg2+tEPTcH8prLFce9H8Y/vgfoamm2Z2iExbNIc0OtkHZ9ncwtlgAd8VV87nfeCu Vdu5uCE1JHgX1wS+rNKvSnx/ZhR9KJwtQrSRUPfG0b7c5vOg/or+aQRRTMGM0ZTASL7d 61VA==
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=/v0RiuOhcBwo7Aw//P2T48vaJ7vo8HTktxW77o4SaDw=; b=juI/pakYKhhfOCMwQyEnEtq6cL9l3TSvo2wKPqBnBkiXNNjlsHdqyz7hdjUz3MpORy w9coiVTBEeZ3RNrB0azmL/6lmjBHcBm7cOfnHM412YMAt8q6quVT+v6Af7SeK5r0yBjb m+TGGEa5w1lcWloYt6tiNr70yCmQpLpe0kfmfy9xW4FJjDO9FrLEVeecZmkFhzIxEmHJ WrDur3rQ6wAbLI8nuEJcrlQDeqh3h5sf6OIxRlufEJvM0AWFjKmVJ/fV1qa0ycWGo1F7 JyxBOEjnatOtkTg2prtaTkmRlvVJoYkNCcj+RUDHg6LR4rkEGeuCW9EassYfcBbzvV6s 2Pmw==
X-Gm-Message-State: AJcUukfryVklH9bQJPhuX55PnJcu9MiIclkI5RBL5QLvpRz4aOkNsPzU C3r6DhepRWGwTQJLpGyNPNUTJVpb
X-Google-Smtp-Source: ALg8bN6+3U9eQiP4iYfuPZrCqf4vq2vy7k8zYdSBu+ZM9pbtZMYHmKvkzgjWEUrz9wBi1SsTy5lxyw==
X-Received: by 2002:a50:9dc1:: with SMTP id l1mr2671972edk.272.1548249049649;  Wed, 23 Jan 2019 05:10:49 -0800 (PST)
Received: from [156.106.225.150] ([156.106.225.150]) by smtp.gmail.com with ESMTPSA id f20sm10980099edf.19.2019.01.23.05.10.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jan 2019 05:10:49 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Message-Id: <812520D8-E504-41C8-8F5C-538E7F716ACC@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A97FD119-536A-4508-B734-78999D380199"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 23 Jan 2019 14:10:35 +0100
In-Reply-To: <100898B7-CCA6-4B00-895F-AD39AAAEF052@tzi.org>
Cc: "json-canon@ietf.org" <json-canon@ietf.org>
To: Carsten Bormann <cabo@tzi.org>
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <CBC45241-0BBB-410C-AF8C-9D49C642566B@tzi.org> <00243004-7200-4887-BB46-ED30D03C4545@gmail.com> <40731AB0-9640-4D74-99B3-EC6E7A51850B@tzi.org> <FA88BB03-ADA7-49EB-AE71-7750BFE71013@gmail.com> <100898B7-CCA6-4B00-895F-AD39AAAEF052@tzi.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/c7ScfI7Azv1dq32nivIKxRo4o8M>
Subject: Re: [Json-canon] [EXT] Re:  Support for a WG
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, 23 Jan 2019 13:10:53 -0000

--Apple-Mail=_A97FD119-536A-4508-B734-78999D380199
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Another use-case I have is for the digital signatures that we need for =
CACAO, and WG that we are trying to get setup in the IETF.  I have some =
slides that talk about the layers of digital signatures that we need to =
be able to do for that work. I can share them with you, or we can have a =
call and I can walk you through it.=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."



--Apple-Mail=_A97FD119-536A-4508-B734-78999D380199
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""><div =
class=3D"">Another use-case I have is for the digital signatures that we =
need for CACAO, and WG that we are trying to get setup in the IETF. =
&nbsp;I have some slides that talk about the layers of digital =
signatures that we need to be able to do for that work. I can share them =
with you, or we can have a call and I can walk you through =
it.&nbsp;</div><div class=3D""><br class=3D""></div><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><br class=3D""></div><br class=3D""></body></html>=

--Apple-Mail=_A97FD119-536A-4508-B734-78999D380199--


From nobody Wed Jan 23 22:17:38 2019
Return-Path: <samuel@erdtman.se>
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 6FEDA1310AC for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 22:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level: 
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=erdtman-se.20150623.gappssmtp.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 dyr3wSFJnsGJ for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 22:17:33 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 94CDD130E1C for <json-canon@ietf.org>; Wed, 23 Jan 2019 22:17:33 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id c25so2223251pgb.4 for <json-canon@ietf.org>; Wed, 23 Jan 2019 22:17:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erdtman-se.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bmzk79wLgILO92+BJ1c+DZDfHJPkepzdLIuBFUcZnf8=; b=vQOI/Z4KaMCEL28b9neCh6Ysub/v5DRSObbkOR09y7XDgFTWo4xfO1rEh8V3zcE7te X1V3XmrF79J2IERxLkN4ShWbOQJTI5+Rx4Mj2yj87vqRy13rE/Q45gpT8xA11KFx9Eyt c1eRInyHlktAxVdeWFF89Zf6x2w+2Emmc1XJAtmCwqF5gsWD6xPOg9O44dnxetvMfblS /5xkxIVdt6njjfhLhZ6iFw8BMFAp8zPjWb2qB/SaMiwlloei/3vKmkREuWf3m//d/86t ln9pNbZVnd8K0bl6TG92i6urfT3bfnQg464PTbSS15WVp5kkCXzVjUW3KJjO+xsdsBrK 1eKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bmzk79wLgILO92+BJ1c+DZDfHJPkepzdLIuBFUcZnf8=; b=ewIRzu2w9CVSLJ5pUQwoYOPd3UWcSchUxVjl6Uqlkhd0yST6sJXFZHKTOJLU32y03D EIdORXRX80msWQTMCxcxkHoHQ/Gip4uIJZgUyaK8TvsmZppDqnFYAwzjXF+D+TjgENaK 5ThzcBHjFzjXKHYzGiyZ7evru0EdXdewEHlyBuG/5rSYKAHAmwa+pfP2IEd3Iab450Zs murNlQgozNg4l8MK6G0LvGMp4JA7lDXYwE7pdmoqzNdBkghEbRm2kHfO2OCHTBAJb0cE hm3vBvYRxsrzBPARJMhjkEKljBhZ91uhGpECgEWI77qWHfQQrNsiiUrgagCgh7zUPerx 15ew==
X-Gm-Message-State: AJcUukdG4URZ7CAz4zzasSJVYEYAhpJwzPbdA/M5rnJasmy8FNQojTu0 SbCrLcukcWKwP13utkiSnWOYqLfcSy8Mf7ujLIBYpA==
X-Google-Smtp-Source: ALg8bN5Xa5xCIG6imPpof/GK1FdESknJm4snLFRNmu9r+Kjp4PNOGDGC57qlP4M1WBWzKH4bsxN4miNE0EXmQJHaJjQ=
X-Received: by 2002:a62:1f97:: with SMTP id l23mr5130711pfj.13.1548310652659;  Wed, 23 Jan 2019 22:17:32 -0800 (PST)
MIME-Version: 1.0
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <E7B44CE8-CE81-4AB3-9665-12D1A52FD9C5@lookingglasscyber.com> <CAF2hCbYSDsPf6p56i1uhSBZZQv7jgLdCQGqHmsVi+nzbW3_46A@mail.gmail.com> <866D8EB8-49F6-4353-B502-F3337ACDBF61@lookingglasscyber.com>
In-Reply-To: <866D8EB8-49F6-4353-B502-F3337ACDBF61@lookingglasscyber.com>
From: Samuel Erdtman <samuel@erdtman.se>
Date: Thu, 24 Jan 2019 07:17:21 +0100
Message-ID: <CAF2hCbZCxCL7CxtFWYwp-hwEio_PQev=jFgX9K_7NQneNLMzXQ@mail.gmail.com>
To: Allan Thomson <athomson@lookingglasscyber.com>
Cc: "Struse, Richard J." <rjs@mitre.org>, Carsten Bormann <cabo@tzi.org>,  "json-canon@ietf.org" <json-canon@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000074415a05802e2a9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/yI2bzg7yu5Rmr2GnpQiHbijoFmw>
Subject: Re: [Json-canon] [EXT] Re: Support for a WG
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, 24 Jan 2019 06:17:37 -0000

--00000000000074415a05802e2a9d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for the followup Allan.

In my opinion the application layer schemas for defining what the JSON can
look like (optional values different values meaning the same thing etc),
should be verified by application layer. I would like to keep the
canonicalization (and potential signatures) at the level where they say the
JSON has not changed.

When it comes to empty empty values I think those are values too, they
might convey some meaning to the application layer.and with empty I mean
{"empty": ""}. And since I do not want the canonicalization to be involved
with application level details optional attributes are not a concept.

Does that make sense?

Cheers
//Samuel





On Tue, Jan 22, 2019 at 5:47 PM Allan Thomson <
athomson@lookingglasscyber.com> wrote:

> I=E2=80=99m not sure how you can create a consistent hash value without
> considering how empty/optional fields in a JSON structure are treated
> consistently across implementations.
>
>
>
> So if the same optional/empty fields exist from 2 different
> vendors/instances then do they end up with the same hash?
>
>
>
> Allan
>
>
>
> *From: *Samuel Erdtman <samuel@erdtman.se>
> *Date: *Tuesday, January 22, 2019 at 8:37 AM
> *To: *Allan Thomson <athomson@lookingglasscyber.com>
> *Cc: *"Struse, Richard J." <rjs@mitre.org>, Carsten Bormann <cabo@tzi.org=
>,
> "json-canon@ietf.org" <json-canon@ietf.org>
> *Subject: *Re: [Json-canon] [EXT] Re: Support for a WG
>
>
>
> I do not think we should go into schemas, that is one of the things that
> makes XMLDigSig inconvenient. But instead keep to simple JSON stringifyin=
g
> with predictable result.
>
> On Tue, 22 Jan 2019 at 16:19, Allan Thomson <
> athomson@lookingglasscyber.com> wrote:
>
> Particularly important in what Rich says is also is to ensure the same
> hash is created where those JSON objects have optional or empty/missing
> properties that are defined in the schema of the object.
>
> Regards
>
> Allan
>
> On 1/22/19, 4:31 AM, "json-canon on behalf of Struse, Richard J." <
> json-canon-bounces@ietf.org on behalf of rjs@mitre.org> wrote:
>
>     The use case is to enable other standards that use a JSON
> serialization to be able to count on two objects, each with the same
> contents, having the same hash value based on their representation in JSO=
N.
>
>     Does that help?
>
>     On 1/18/19, 1:47 AM, "Carsten Bormann" <cabo@tzi.org> wrote:
>
>         On Jan 18, 2019, at 03:50, Struse, Richard J. <rjs@mitre.org>
> wrote:
>         >
>         > A standardized deterministic canonicalization of JSON data
> streams is essential
>
>         For what?
>
>         I think we would all benefit if you could explain your use case.
>
>         Gr=C3=BC=C3=9Fe, Carsten
>
>
>
>     --
>     json-canon mailing list
>     json-canon@ietf.org
>     https://www.ietf.org/mailman/listinfo/json-canon
>
>
> --
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon
>
>

--00000000000074415a05802e2a9d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks for the followup Allan.</div><div><br></div><d=
iv>In my opinion the application layer schemas for defining what the JSON c=
an look like (optional values different values meaning the same thing etc),=
 should be verified by application layer. I would like to keep the canonica=
lization (and potential signatures) at the level where they say the JSON ha=
s not changed.<br></div><div></div><div><br></div><div>When it comes to emp=
ty empty values I think those are values too, they might convey some meanin=
g to the application layer.and with empty I mean</div><div>{&quot;empty&quo=
t;: &quot;&quot;}. And since I do not want the canonicalization to be invol=
ved with application level details optional attributes are not a concept.<b=
r></div><div><br></div><div>Does that make sense?</div><div><br></div><div>=
Cheers<br></div><div>//Samuel<br></div><div><br></div><div><br></div><div><=
br></div><div>=C2=A0 </div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail-m_7417236643903423541gmail_attr">On Tue, Jan 22, 2019 =
at 5:47 PM Allan Thomson &lt;<a href=3D"mailto:athomson@lookingglasscyber.c=
om" target=3D"_blank">athomson@lookingglasscyber.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_7417236643903423541gmail-m_4179555633589711005WordSec=
tion1">
<p class=3D"MsoNormal">I=E2=80=99m not sure how you can create a consistent=
 hash value without considering how empty/optional fields in a JSON structu=
re are treated consistently across implementations.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">So if the=
 same optional/empty fields exist from 2 different vendors/instances then d=
o they end up with the same hash?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">Allan<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-color:rgb(181,196,223) currentcolor currentcolor;borde=
r-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in"=
>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt;color:black">From: =
</span></b><span style=3D"font-size:12pt;color:black">Samuel Erdtman &lt;<a=
 href=3D"mailto:samuel@erdtman.se" target=3D"_blank">samuel@erdtman.se</a>&=
gt;<br>
<b>Date: </b>Tuesday, January 22, 2019 at 8:37 AM<br>
<b>To: </b>Allan Thomson &lt;<a href=3D"mailto:athomson@lookingglasscyber.c=
om" target=3D"_blank">athomson@lookingglasscyber.com</a>&gt;<br>
<b>Cc: </b>&quot;Struse, Richard J.&quot; &lt;<a href=3D"mailto:rjs@mitre.o=
rg" target=3D"_blank">rjs@mitre.org</a>&gt;, Carsten Bormann &lt;<a href=3D=
"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;, &quot;<a href=
=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-canon@ietf.org</a>&q=
uot; &lt;<a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-cano=
n@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: [Json-canon] [EXT] Re: Support for a WG<u></u><u></u></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">I do not think we should go into schemas, that is on=
e of the things that makes XMLDigSig inconvenient. But instead keep to simp=
le JSON stringifying with predictable result.<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Tue, 22 Jan 2019 at 16:19, Allan Thomson &lt;<a h=
ref=3D"mailto:athomson@lookingglasscyber.com" target=3D"_blank">athomson@lo=
okingglasscyber.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-color:currentcolor currentcolor currentcolor rg=
b(204,204,204);border-style:none none none solid;border-width:medium medium=
 medium 1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal">Particularly important in what Rich says is also is =
to ensure the same hash is created where those JSON objects have optional o=
r empty/missing properties that are defined in the schema of the object.<br=
>
<br>
Regards<br>
<br>
Allan<br>
<br>
On 1/22/19, 4:31 AM, &quot;json-canon on behalf of Struse, Richard J.&quot;=
 &lt;<a href=3D"mailto:json-canon-bounces@ietf.org" target=3D"_blank">json-=
canon-bounces@ietf.org</a> on behalf of
<a href=3D"mailto:rjs@mitre.org" target=3D"_blank">rjs@mitre.org</a>&gt; wr=
ote:<br>
<br>
=C2=A0 =C2=A0 The use case is to enable other standards that use a JSON ser=
ialization to be able to count on two objects, each with the same contents,=
 having the same hash value based on their representation in JSON.<br>
<br>
=C2=A0 =C2=A0 Does that help?<br>
<br>
=C2=A0 =C2=A0 On 1/18/19, 1:47 AM, &quot;Carsten Bormann&quot; &lt;<a href=
=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 On Jan 18, 2019, at 03:50, Struse, Richard J. &=
lt;<a href=3D"mailto:rjs@mitre.org" target=3D"_blank">rjs@mitre.org</a>&gt;=
 wrote:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; <br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; A standardized deterministic canonicalizat=
ion of JSON data streams is essential<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 For what?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I think we would all benefit if you could expla=
in your use case.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 -- <br>
=C2=A0 =C2=A0 json-canon mailing list<br>
=C2=A0 =C2=A0 <a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json=
-canon@ietf.org</a><br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/json-canon</a><br>
<br>
<br>
-- <br>
json-canon mailing list<br>
<a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-canon@ietf.or=
g</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/json-canon</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>

--00000000000074415a05802e2a9d--


From nobody Wed Jan 23 23:13:47 2019
Return-Path: <samuel@erdtman.se>
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 48F1B1310D5 for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 23:13:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level: 
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=erdtman-se.20150623.gappssmtp.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 I1hX8rHHJava for <json-canon@ietfa.amsl.com>; Wed, 23 Jan 2019 23:13:41 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 923C4130EA9 for <json-canon@ietf.org>; Wed, 23 Jan 2019 23:13:41 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id n2so2284214pgm.3 for <json-canon@ietf.org>; Wed, 23 Jan 2019 23:13:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=erdtman-se.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZX3SCeTmdnwi9QfXQ7RH4oAOdaKxWlrOIr22AYGEwZY=; b=AMUh/n/qd5YL9wp8DBTyklqaOLq3VqjFSOp+IUzAmcrM/qJBU7M5M7FejjQEVOeeTz ChYHZS/i0LqXznKcn5RGGR8sDMNJy/Qu6Gp/iOJ3m8xkOxmCPfALeeGm/M/wEmzZ+TBi S1JKfTCkIK84JKK9k9RyD9OGpxwLgsdt/0CM7skGEoWJ4p2SPOD0B8an3ISNiifCbgMl J/HqNE5kloon+W55DiegSdtnnaJJ9o0X6lAjRHOhlARhw19zcaIZ3tvwPaPNV+w2d/Da elJtJspcqxHp+Exf9MNFm34IZYJrm6d4SsrzRXgBI8BqbZh0a3ixP3JdMs1szLY9OsCx /6pw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZX3SCeTmdnwi9QfXQ7RH4oAOdaKxWlrOIr22AYGEwZY=; b=rDvM5yjxr5M6XrBB/O1N6LzfPGQstQY0OJHpJ3Z+niAC2BMb2Amts+r/hQcedoyioH Sdmnup6WOwKV43/9W3MdZT5Yk05U1Ywgyp16MIxNsea79cCvefy9dikc1OZ4U3aXuY0D AAc5zaWhlw63pi8ROV11LY77EqttvCgTF6IXHf7SKqYzzWhVAas54WyfxdNjh+d9wght /O//S/3gBpPoDvc4oTZ0LvRqbfd2Py5rzX4Qp8dDIeCK54A2NblKj+ZcthBsPtVEFZ3D lUVAWqtFu3RFGZk4TkI9VeC+odUjL+mXJBBz63B/htTeP0L9aejJcwFo5/bCmz1F29wh uycQ==
X-Gm-Message-State: AJcUukd9g81KrBCxGEeX3Vc7GYTmW1cTngguIA16Wohu37Jz8SYmXdzx P2qlC+Ofk6cTe9UupaztWK5jSt93VuxJ4ggmiJWuYydbKrr0/1AG
X-Google-Smtp-Source: ALg8bN5vwxkdBpjc2glbFkH/FzqjSnF7frVSusFiEudlTdyerzAJB8+4GrmGPlfz/FLTOX/286tKurSMI2oXv2nrj64=
X-Received: by 2002:a62:2292:: with SMTP id p18mr5481617pfj.9.1548314020929; Wed, 23 Jan 2019 23:13:40 -0800 (PST)
MIME-Version: 1.0
References: <38C84459-3D2E-4E78-BF48-FE277388E33A@contoso.com> <21415_1547794000_5C417650_21415_473_1_34A23FAA-C8F5-40E3-8358-FD42C5F78126@tzi.org> <60B977A0-0958-4DDF-A666-A44F074E5946@mitre.org> <E7B44CE8-CE81-4AB3-9665-12D1A52FD9C5@lookingglasscyber.com> <CAF2hCbYSDsPf6p56i1uhSBZZQv7jgLdCQGqHmsVi+nzbW3_46A@mail.gmail.com> <866D8EB8-49F6-4353-B502-F3337ACDBF61@lookingglasscyber.com> <CAF2hCbZCxCL7CxtFWYwp-hwEio_PQev=jFgX9K_7NQneNLMzXQ@mail.gmail.com>
In-Reply-To: <CAF2hCbZCxCL7CxtFWYwp-hwEio_PQev=jFgX9K_7NQneNLMzXQ@mail.gmail.com>
From: Samuel Erdtman <samuel@erdtman.se>
Date: Thu, 24 Jan 2019 08:13:29 +0100
Message-ID: <CAF2hCbZ1DHGd=NQLHekGn7q-8nYpdUn3LRdATTT3wBr=rf4H7A@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: "Struse, Richard J." <rjs@mitre.org>, "json-canon@ietf.org" <json-canon@ietf.org>,  Allan Thomson <athomson@lookingglasscyber.com>
Content-Type: multipart/alternative; boundary="00000000000038166305802ef3a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/ugh5WohE3dXyHu1kOIDxf-bLXcI>
Subject: Re: [Json-canon] [EXT] Re: Support for a WG
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, 24 Jan 2019 07:13:44 -0000

--00000000000038166305802ef3a5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Carsten, Here comes a few another concrete example where canonical JSON
would be beneficial (not an absolute need).

Open Banking (
https://openbanking.atlassian.net/wiki/spaces/DZ/pages/5785171/Account+and+=
Transaction+API+Specification+-+v1.1.0#AccountandTransactionAPISpecificatio=
n-v1.1.0-Processforsigningapayload
)
In this case RFC 7797 is used to keep the payload separated form the
signature and headers.
If you look at the processing steps the HTTP body (josn) is Base64 encoded
and used as payload for the JWS calculation, it is however not the base64
encoded payload that is sent in the HTTP body but the cleartext json (as
can be seen in the verification steps). This is a workable but brittle
solution. With a canonical JOSN format this solution could be made stable.
(I have no personal contact with this group so I do not know if they
formally would be interested, but it is a case here cleartext JSON is
signed)

Then there are the TEEP usecase (
https://tools.ietf.org/id/draft-ietf-teep-opentrustprotocol)
In this case JOSE is used and there is several layers of signing (and
encryption) being done, since the payload is always base64 encode and then
wrapped the messages becomes very opaque. So to me they have a workable
solution but would benefit from canonical JOSN in combination with RFC
7797. (Once again I have no personal contact with this group so I do not
know if they formally would be interested)

Then there is the Signing HTTP Messages case (
https://tools.ietf.org/html/draft-cavage-http-signatures)
This one is a bit more far fetched, but instead of defining how to
canonicalize the HTTP headers they could do a simple mapping form https
headers to JOSN and have it canonicalized and then signed using RFC 7797.
(Once again I have no personal contact with this group so I do not know if
they formally would be interested)

Best regards
//Samuel




On Thu, Jan 24, 2019 at 7:17 AM Samuel Erdtman <samuel@erdtman.se> wrote:

> Thanks for the followup Allan.
>
> In my opinion the application layer schemas for defining what the JSON ca=
n
> look like (optional values different values meaning the same thing etc),
> should be verified by application layer. I would like to keep the
> canonicalization (and potential signatures) at the level where they say t=
he
> JSON has not changed.
>
> When it comes to empty empty values I think those are values too, they
> might convey some meaning to the application layer.and with empty I mean
> {"empty": ""}. And since I do not want the canonicalization to be involve=
d
> with application level details optional attributes are not a concept.
>
> Does that make sense?
>
> Cheers
> //Samuel
>
>
>
>
>
> On Tue, Jan 22, 2019 at 5:47 PM Allan Thomson <
> athomson@lookingglasscyber.com> wrote:
>
>> I=E2=80=99m not sure how you can create a consistent hash value without
>> considering how empty/optional fields in a JSON structure are treated
>> consistently across implementations.
>>
>>
>>
>> So if the same optional/empty fields exist from 2 different
>> vendors/instances then do they end up with the same hash?
>>
>>
>>
>> Allan
>>
>>
>>
>> *From: *Samuel Erdtman <samuel@erdtman.se>
>> *Date: *Tuesday, January 22, 2019 at 8:37 AM
>> *To: *Allan Thomson <athomson@lookingglasscyber.com>
>> *Cc: *"Struse, Richard J." <rjs@mitre.org>, Carsten Bormann <cabo@tzi.or=
g>,
>> "json-canon@ietf.org" <json-canon@ietf.org>
>> *Subject: *Re: [Json-canon] [EXT] Re: Support for a WG
>>
>>
>>
>> I do not think we should go into schemas, that is one of the things that
>> makes XMLDigSig inconvenient. But instead keep to simple JSON stringifyi=
ng
>> with predictable result.
>>
>> On Tue, 22 Jan 2019 at 16:19, Allan Thomson <
>> athomson@lookingglasscyber.com> wrote:
>>
>> Particularly important in what Rich says is also is to ensure the same
>> hash is created where those JSON objects have optional or empty/missing
>> properties that are defined in the schema of the object.
>>
>> Regards
>>
>> Allan
>>
>> On 1/22/19, 4:31 AM, "json-canon on behalf of Struse, Richard J." <
>> json-canon-bounces@ietf.org on behalf of rjs@mitre.org> wrote:
>>
>>     The use case is to enable other standards that use a JSON
>> serialization to be able to count on two objects, each with the same
>> contents, having the same hash value based on their representation in JS=
ON.
>>
>>     Does that help?
>>
>>     On 1/18/19, 1:47 AM, "Carsten Bormann" <cabo@tzi.org> wrote:
>>
>>         On Jan 18, 2019, at 03:50, Struse, Richard J. <rjs@mitre.org>
>> wrote:
>>         >
>>         > A standardized deterministic canonicalization of JSON data
>> streams is essential
>>
>>         For what?
>>
>>         I think we would all benefit if you could explain your use case.
>>
>>         Gr=C3=BC=C3=9Fe, Carsten
>>
>>
>>
>>     --
>>     json-canon mailing list
>>     json-canon@ietf.org
>>     https://www.ietf.org/mailman/listinfo/json-canon
>>
>>
>> --
>> json-canon mailing list
>> json-canon@ietf.org
>> https://www.ietf.org/mailman/listinfo/json-canon
>>
>>

--00000000000038166305802ef3a5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Carsten, Here comes a few =
another concrete example where canonical JSON would be beneficial (not an a=
bsolute need).<br></div><div><br></div><div>Open Banking (<a href=3D"https:=
//openbanking.atlassian.net/wiki/spaces/DZ/pages/5785171/Account+and+Transa=
ction+API+Specification+-+v1.1.0#AccountandTransactionAPISpecification-v1.1=
.0-Processforsigningapayload">https://openbanking.atlassian.net/wiki/spaces=
/DZ/pages/5785171/Account+and+Transaction+API+Specification+-+v1.1.0#Accoun=
tandTransactionAPISpecification-v1.1.0-Processforsigningapayload</a>)<br></=
div><div>In this case RFC 7797 is used to keep the payload separated form t=
he signature and headers.</div><div>If you look at the processing steps the=
 HTTP body (josn) is Base64 encoded and used as payload for the JWS calcula=
tion, it is however not the base64 encoded payload that is sent in the HTTP=
 body but the cleartext json (as can be seen in the verification steps). Th=
is is a workable but brittle solution. With a canonical JOSN format this so=
lution could be made stable. (I have no personal contact with this group so=
 I do not know if they formally would be interested, but it is a case here =
cleartext JSON is signed)<br></div><div><br></div><div>Then there are the T=
EEP usecase (<a href=3D"https://tools.ietf.org/id/draft-ietf-teep-opentrust=
protocol">https://tools.ietf.org/id/draft-ietf-teep-opentrustprotocol</a>)<=
/div><div>In this case JOSE is used and there is several layers of signing =
(and encryption) being done, since the payload is always base64 encode and =
then wrapped the messages becomes very opaque. So to me they have a workabl=
e solution but would benefit from canonical JOSN in combination with RFC 77=
97. (Once again I have no personal contact with this group so I do not know=
 if they formally would be interested)</div><div><br></div><div>Then there =
is the Signing HTTP Messages case (<a href=3D"https://tools.ietf.org/html/d=
raft-cavage-http-signatures">https://tools.ietf.org/html/draft-cavage-http-=
signatures</a>)<br></div><div>This one is a bit more far fetched, but inste=
ad of defining how to canonicalize the HTTP headers they could do a simple =
mapping form https headers to JOSN and have it canonicalized and then signe=
d using RFC 7797. (Once again I have no personal contact with this group so=
 I do not know if they formally would be interested)</div><div><br></div><d=
iv>Best regards</div><div>//Samuel<br></div><div><br></div><div><br></div><=
div><br></div></div></div></div></div></div></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 24, 2019 at 7=
:17 AM Samuel Erdtman &lt;<a href=3D"mailto:samuel@erdtman.se">samuel@erdtm=
an.se</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div>Thanks for the followup Allan.</div><div><br></d=
iv><div>In my opinion the application layer schemas for defining what the J=
SON can look like (optional values different values meaning the same thing =
etc), should be verified by application layer. I would like to keep the can=
onicalization (and potential signatures) at the level where they say the JS=
ON has not changed.<br></div><div></div><div><br></div><div>When it comes t=
o empty empty values I think those are values too, they might convey some m=
eaning to the application layer.and with empty I mean</div><div>{&quot;empt=
y&quot;: &quot;&quot;}. And since I do not want the canonicalization to be =
involved with application level details optional attributes are not a conce=
pt.<br></div><div><br></div><div>Does that make sense?</div><div><br></div>=
<div>Cheers<br></div><div>//Samuel<br></div><div><br></div><div><br></div><=
div><br></div><div>=C2=A0 </div></div><br><div class=3D"gmail_quote"><div d=
ir=3D"ltr" class=3D"gmail-m_-7169100751549600614gmail-m_7417236643903423541=
gmail_attr">On Tue, Jan 22, 2019 at 5:47 PM Allan Thomson &lt;<a href=3D"ma=
ilto:athomson@lookingglasscyber.com" target=3D"_blank">athomson@lookingglas=
scyber.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-7169100751549600614gmail-m_7417236643903423541gmail-=
m_4179555633589711005WordSection1">
<p class=3D"MsoNormal">I=E2=80=99m not sure how you can create a consistent=
 hash value without considering how empty/optional fields in a JSON structu=
re are treated consistently across implementations.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">So if the=
 same optional/empty fields exist from 2 different vendors/instances then d=
o they end up with the same hash?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">Allan<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-color:rgb(181,196,223) currentcolor currentcolor;borde=
r-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in"=
>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt;color:black">From: =
</span></b><span style=3D"font-size:12pt;color:black">Samuel Erdtman &lt;<a=
 href=3D"mailto:samuel@erdtman.se" target=3D"_blank">samuel@erdtman.se</a>&=
gt;<br>
<b>Date: </b>Tuesday, January 22, 2019 at 8:37 AM<br>
<b>To: </b>Allan Thomson &lt;<a href=3D"mailto:athomson@lookingglasscyber.c=
om" target=3D"_blank">athomson@lookingglasscyber.com</a>&gt;<br>
<b>Cc: </b>&quot;Struse, Richard J.&quot; &lt;<a href=3D"mailto:rjs@mitre.o=
rg" target=3D"_blank">rjs@mitre.org</a>&gt;, Carsten Bormann &lt;<a href=3D=
"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;, &quot;<a href=
=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-canon@ietf.org</a>&q=
uot; &lt;<a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-cano=
n@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: [Json-canon] [EXT] Re: Support for a WG<u></u><u></u></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">I do not think we should go into schemas, that is on=
e of the things that makes XMLDigSig inconvenient. But instead keep to simp=
le JSON stringifying with predictable result.<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Tue, 22 Jan 2019 at 16:19, Allan Thomson &lt;<a h=
ref=3D"mailto:athomson@lookingglasscyber.com" target=3D"_blank">athomson@lo=
okingglasscyber.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-color:currentcolor currentcolor currentcolor rg=
b(204,204,204);border-style:none none none solid;border-width:medium medium=
 medium 1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal">Particularly important in what Rich says is also is =
to ensure the same hash is created where those JSON objects have optional o=
r empty/missing properties that are defined in the schema of the object.<br=
>
<br>
Regards<br>
<br>
Allan<br>
<br>
On 1/22/19, 4:31 AM, &quot;json-canon on behalf of Struse, Richard J.&quot;=
 &lt;<a href=3D"mailto:json-canon-bounces@ietf.org" target=3D"_blank">json-=
canon-bounces@ietf.org</a> on behalf of
<a href=3D"mailto:rjs@mitre.org" target=3D"_blank">rjs@mitre.org</a>&gt; wr=
ote:<br>
<br>
=C2=A0 =C2=A0 The use case is to enable other standards that use a JSON ser=
ialization to be able to count on two objects, each with the same contents,=
 having the same hash value based on their representation in JSON.<br>
<br>
=C2=A0 =C2=A0 Does that help?<br>
<br>
=C2=A0 =C2=A0 On 1/18/19, 1:47 AM, &quot;Carsten Bormann&quot; &lt;<a href=
=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 On Jan 18, 2019, at 03:50, Struse, Richard J. &=
lt;<a href=3D"mailto:rjs@mitre.org" target=3D"_blank">rjs@mitre.org</a>&gt;=
 wrote:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; <br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; A standardized deterministic canonicalizat=
ion of JSON data streams is essential<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 For what?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I think we would all benefit if you could expla=
in your use case.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 -- <br>
=C2=A0 =C2=A0 json-canon mailing list<br>
=C2=A0 =C2=A0 <a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json=
-canon@ietf.org</a><br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/json-canon</a><br>
<br>
<br>
-- <br>
json-canon mailing list<br>
<a href=3D"mailto:json-canon@ietf.org" target=3D"_blank">json-canon@ietf.or=
g</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/json-canon" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/json-canon</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>
</blockquote></div>

--00000000000038166305802ef3a5--


From nobody Thu Jan 24 10:57:09 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 BBE39131383 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 10:57:07 -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 w23opXXE01xI for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 10:57:06 -0800 (PST)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 7CDB7131381 for <json-canon@ietf.org>; Thu, 24 Jan 2019 10:57:05 -0800 (PST)
Received: by mail-ed1-x530.google.com with SMTP id g22so5448263edr.7 for <json-canon@ietf.org>; Thu, 24 Jan 2019 10:57:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:subject:message-id:date:to; bh=qxV3qa/EQcmkUwPAUMFthid+p5pCQwemdoQFpIPoOnc=; b=I994YT+jqZkvGnAzmBgLxlEMy30BfXftkSFmmA8QBEaRtES058243IL6UulClDMXPr nGbks9CNXE2d0TzG+FQoq83SA3kYswOnm9qG3Lsfdi6G2xbt5KaCny6YE6F0hmO6J6M4 AT4ds+/gU5NKDrNgIWhtH/7t+aiIBU242igozBGwujl3YWwO6Es0uw29hyHWKQVlgCbW M2PuIgUkzxojMwosyGhcpegxWrJYUwrTRdR2XjckwugEXpSDsvRXdFelZ6PdLqMzaHiX GW6T9VX5NUqxhd6ru5phriDfy3wT315iSP0lb0pl/Z7LKb4vo3I27dsBpJrVpA6n02aC Ijkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=qxV3qa/EQcmkUwPAUMFthid+p5pCQwemdoQFpIPoOnc=; b=Jg9XE/XBL4L4AME82tGEqjfCUBZ3irU2LgOl3H/eO54iOeJ1Rnw0Vs2mevjyEREp6/ U13Bg5xKKHYZnjtULNcscEUDWVCOPIU1v3enBgROlfEmphY86/Oh6+IK94/hwEKkxc6J U/V/It2a8Q4zq5SRiXr5cFqxK0vE0njukmsObkwaeQlgqjafgz/BcjBioT3/PgjDVzzR vT5iMy54lRx2pjKX4aP+O2tX3CfN97UDrOjZcQw/Uw9YCSwoYkmLCgkQ8HXKBsx5ofA1 brsAIjHvaT8br7HCIgMIJdl/15tCjoi5dVKRPf6Ch64v8KSPswxBe/p9f1opKTe8VMr6 2G/A==
X-Gm-Message-State: AJcUukfsq9fJ+CHJLwB4sunJHqibi1yY0/aX/SP9SjJ0rU2vI7UC8oI0 1H35hMQtw8MbR4iWcbwqlnBl+T6x
X-Google-Smtp-Source: ALg8bN4xi16OqkZvycJ1fHejVDqV1/+gdVQycCKHcwSphjBkP7kIzQKm+GE8dC3g3ORI/vL/91iKdg==
X-Received: by 2002:a17:906:20c2:: with SMTP id c2-v6mr6992509ejc.241.1548356223448;  Thu, 24 Jan 2019 10:57:03 -0800 (PST)
Received: from [156.106.225.238] ([156.106.225.238]) by smtp.gmail.com with ESMTPSA id h51sm12123545edh.17.2019.01.24.10.57.02 for <json-canon@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 10:57:02 -0800 (PST)
From: Bret Jordan <jordan.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_48427516-EC9F-40CC-BC13-B8E79F72B7C1"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com>
Date: Thu, 24 Jan 2019 19:56:48 +0100
To: json-canon@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/MrIIEgIG3g3IYEb7eoSrj3aedqU>
Subject: [Json-canon] Proposed Charter
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, 24 Jan 2019 18:57:08 -0000

--Apple-Mail=_48427516-EC9F-40CC-BC13-B8E79F72B7C1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

All,

Here is a proposed charter for this WG.  Please send any comments on =
this charter to this email list.=20



### BEGIN

JavaScript Object Notation (JSON) is a text format for the serialization =
of structured data described in RFC 8259. The JSON format is often used =
for serializing and transmitting structured data over a network =
connection. With the increased usage of JSON in protocols in the IETF =
and elsewhere, there is now a need to define a canonical representation =
of JSON objects to enable comparison operations and security services on =
plain text JSON.=20

Different proposals for providing such security services have already =
been defined and implemented. The goal of the Working Group is to define =
and standardize a mechanism for creating a canonical representation of =
plain text JSON objects.

This group is chartered to work on the following deliverable:

- A Standards Track document specifying a canonical representation of =
JSON data.

In order to promote interoperability and ease of implementation, the =
current proposal builds on I-JSON (RFC 7493), the serialization methods =
for JSON primitives defined by EcmaScript version 6, and a =
platform-independent method for sorting object properties.  By doing =
that, JSON parsers will not need modifications, enabling the described =
mechanism to ultimately be reduced to an option in JSON serializers.

The proposed work-item is tentatively named JSON Canonicalization Scheme =
(JCS)

### END



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."


--Apple-Mail=_48427516-EC9F-40CC-BC13-B8E79F72B7C1
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"">All,<div class=3D""><br class=3D""></div><div class=3D"">Here =
is a proposed charter for this WG. &nbsp;Please send any comments on =
this charter to this email list.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">### BEGIN</div><div class=3D""><br =
class=3D""></div><div class=3D"">JavaScript Object Notation (JSON) is a =
text format for the serialization of structured data described in RFC =
8259. The JSON format is often used for serializing and transmitting =
structured data over a network connection. With the increased usage of =
JSON in protocols in the IETF and elsewhere, there is now a need to =
define a canonical representation of JSON objects to enable comparison =
operations and security services on plain text JSON.&nbsp;<br =
class=3D""><br class=3D"">Different proposals for providing such =
security services have already been defined and implemented. The goal of =
the Working Group is to define and standardize a mechanism for creating =
a canonical representation of plain text JSON objects.<br class=3D""><br =
class=3D"">This group is chartered to work on the following =
deliverable:<br class=3D""><br class=3D"">- A Standards Track document =
specifying a canonical representation of JSON data.<br class=3D""><br =
class=3D"">In order to promote interoperability and ease of =
implementation, the current proposal builds on I-JSON (RFC&nbsp;7493), =
the serialization methods for JSON primitives defined by EcmaScript =
version 6, and a platform-independent method for sorting object =
properties. &nbsp;By doing that, JSON parsers will not need =
modifications, enabling the described mechanism to ultimately be reduced =
to an option in JSON serializers.<br class=3D""><br class=3D"">The =
proposed work-item is tentatively named JSON Canonicalization Scheme =
(JCS)<br class=3D""><br class=3D""></div><div class=3D"">### =
END</div><div class=3D""><br class=3D""></div><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>

<br class=3D""></div></body></html>=

--Apple-Mail=_48427516-EC9F-40CC-BC13-B8E79F72B7C1--


From nobody Thu Jan 24 13:48:20 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 36DD61311CD for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 13:48:19 -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 bI0rbe7-R9H0 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 13:48:16 -0800 (PST)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 464781311D7 for <json-canon@ietf.org>; Thu, 24 Jan 2019 13:48:16 -0800 (PST)
Received: by mail-wr1-x42b.google.com with SMTP id l9so8091513wrt.13 for <json-canon@ietf.org>; Thu, 24 Jan 2019 13:48:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=eT6reoeh+fi5KDuVhy76dm8n8H4nwl11IvwloTUwi7Q=; b=Q5XnMKoOSEf1J9tjSQKu5I/BBjC7vay7h75beQGzh9tJkxbyyXHGpbwzKOeaQj4f4P B+ad7JAPeG4ZEDEcXMun/ljcn0eC1iIneyDiIttNhHnlV6EfJaJGKKJaAd1SUT+6L2Yu IJ+LrCPkVIqQLDis7ICHaBNs9+VgjZblWb0Z7iJ2jsJ1+KTvX1sx3G5BJO+Hk9AgEn+H 6j9n58r+rgKRL+41qUPZ5xl6ZZYIJoYZ0dKLRng+RF7i5WyzfBq2RmL9fCw5y27jpwpZ EOE0aJPzP8bL4MmfX1lgoN+FgumskAqOKPan59RJTt2fqt/UKSiQ5T9As81NH37aGgGa ACGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eT6reoeh+fi5KDuVhy76dm8n8H4nwl11IvwloTUwi7Q=; b=PmHMbzvGbIPQiBM/5a3xv+uPbsc3zq2+nbi4rja266VkcvVng/IFy9TcN5hJrmT9t8 zDUWSncIrCbVztMs+j2V7E/euwziZ4PWsIEFsZrqbJ3H2O9hPBWrVtDzMe5XxzmU9Ycn 75AYDx/8xW6aZxSnashWtULLM0hPCdnELfXciajKHj+VvhzECByrzplslJMrfbJa80Dc c1MgpendWGEJS/3TAT68g0+UBKERX9gbncNsSlko0BWeoLKhtvcH4XX14uDt1OKleuqc BgVdJMYH5twhQCmrl8atBJ0oZvpi5QEeQ97NnnNMH/zU7HQgWSOqir+/qKkYjpBZyTSH gmXg==
X-Gm-Message-State: AJcUukc5WNQCArmUmT3swL4X4tm0GVDfoj/vYn/sx50ac1jk/F2aRuXn n62qoZBNnTbVatwyxgMILbBNF4l8
X-Google-Smtp-Source: ALg8bN71kw97GB/ng9jJnQv9IpiVPZO3j1NB0S0MEs66nOUa2miP/FMsI8EX+Ge09GjDK4+ceeOt9w==
X-Received: by 2002:a5d:558a:: with SMTP id i10mr8505035wrv.287.1548366494279;  Thu, 24 Jan 2019 13:48:14 -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 g67sm129029734wmd.38.2019.01.24.13.48.11 for <json-canon@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 13:48:13 -0800 (PST)
To: json-canon@ietf.org
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <041f70bb-672e-6e7c-cd6f-a8caa7de9f87@gmail.com>
Date: Thu, 24 Jan 2019 22:48:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/giQe9sH35qLNKyUZIZIriYrZoxw>
Subject: [Json-canon] I-D: 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: Thu, 24 Jan 2019 21:48:19 -0000

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


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 serialization formats for JSON
    primitives as 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.

Enjoy!

Anders for the team


From nobody Thu Jan 24 13:55:22 2019
Return-Path: <mnot@mnot.net>
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 8676313117B for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 13:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=mnot.net header.b=39J4wqdI; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JqzouenZ
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 njuRrZg5kNxh for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 13:55:17 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4106B130F21 for <json-canon@ietf.org>; Thu, 24 Jan 2019 13:55:17 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 25C5A221B8; Thu, 24 Jan 2019 16:55:16 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 24 Jan 2019 16:55:16 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=I XmXubeFV0dEcBeoZrOsvB0XXmlp57TJVlIpqoQ9VC4=; b=39J4wqdIXZy3zhnQd nkDm0N4/7PDzGuwdS2LIjyNsZJKvKoM1O++hnz2j8Qcb7uvLmfVbGCnrh9qeg7M7 hWjFr5ITScrM21sRR2HPS3SrEqGyPGQDkjWCoVJHmVEBUpadhsDofrH3zfyIG1ao D6PsxGsp9YQKAckdqMuCCLJe7b5ZzjrfDgLN8GSgMpYoZB4lkP835JeJgk2U+gyT DmzskNxoMF4u8W5QHVrXKUmnPu5FoEjC62+Fvuo8qFBQOXEbgCJuTDhl+wfy/4zB YHlPwA640G04P/i2afV85hwlPSqjt1gb0L1bBVomiQZUfkg+hwc6VgtvyB+tO2ji +MzwA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=IXmXubeFV0dEcBeoZrOsvB0XXmlp57TJVlIpqoQ9V C4=; b=JqzouenZj+saN/k0Bag+VwY+fzowEdzAODspmuQW3rlrf2uvr4IJojwjN wtHqweDDjF+QzldnXf47CFQcyYFl6EIHsLDRZfkNTICHhar0uWGbHa4+hnhHxYot QtW70cb7niPYKlSUx5dfEQf2HZwyyP384pm15IaFynNXIA3ZpzYqBxDdT99SG9HF 0wQJCMkN6OrcbjTy9NRdexeK0x+4nORe8NzdSYR68xzgP+X+u/qawgVKmLo8mtZx M83WeoVoryTgPQ/d80M8fashF66vsM93zryUj4ymnNl39mY60pXHiwZQqh7aoE1z 8aRXXd86McIDEuRzddKTKx/T/rz3w==
X-ME-Sender: <xms:QjRKXLhlbkI3u3ANeH_E75PXDbYRJ3_PSIKRlbsLXqyB6dnsfjDJzg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledriedvgdduheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjff fgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghm uceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpehivghtfhdrohhrghdpmh hnohhtrdhnvghtnecukfhppeekrddukedrvddujedrvddtvdenucfrrghrrghmpehmrghi lhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:QzRKXAlSorzyZ6X23cFW_NuXG5fEvHhE6BhvtiPjch-zQdd_66ko8g> <xmx:QzRKXC3AxMxDiAb1uUAMTKfKemPAtrZ9qPg0p8iQnzZxbPAEg7UBXQ> <xmx:QzRKXBOmwj1_-JtKiU2ZLs5aKkuN-X9dKug10zUsU3Qd1LYRwHmyLA> <xmx:RDRKXB_kO05jXO0A1vVcZ6vl9HfbgNSNYhXaZYLgIVpj56WvDs-6Aw>
Received: from [10.100.20.187] (unknown [8.18.217.202]) by mail.messagingengine.com (Postfix) with ESMTPA id 540F0100E4; Thu, 24 Jan 2019 16:55:14 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com>
Date: Thu, 24 Jan 2019 13:55:10 -0800
Cc: json-canon@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net>
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com>
To: Bret Jordan <jordan.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/Rr2KYeWCFWVf8OUd7iWWa2PqaH8>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 21:55:21 -0000

Will the Working Group limit itself to canonicalising the data model =
that's described by JSON's native data types (object, array, number, =
string, boolean, null), or will it attempt to canonicalise subtypes -- =
for example, inside strings (whether they be key or value)?

I'd be much more comfortable if this were addressed explicitly in the =
charter.

Cheers,


> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> =
wrote:
>=20
> All,
>=20
> Here is a proposed charter for this WG.  Please send any comments on =
this charter to this email list.=20
>=20
>=20
>=20
> ### BEGIN
>=20
> JavaScript Object Notation (JSON) is a text format for the =
serialization of structured data described in RFC 8259. The JSON format =
is often used for serializing and transmitting structured data over a =
network connection. With the increased usage of JSON in protocols in the =
IETF and elsewhere, there is now a need to define a canonical =
representation of JSON objects to enable comparison operations and =
security services on plain text JSON.=20
>=20
> Different proposals for providing such security services have already =
been defined and implemented. The goal of the Working Group is to define =
and standardize a mechanism for creating a canonical representation of =
plain text JSON objects.
>=20
> This group is chartered to work on the following deliverable:
>=20
> - A Standards Track document specifying a canonical representation of =
JSON data.
>=20
> In order to promote interoperability and ease of implementation, the =
current proposal builds on I-JSON (RFC 7493), the serialization methods =
for JSON primitives defined by EcmaScript version 6, and a =
platform-independent method for sorting object properties.  By doing =
that, JSON parsers will not need modifications, enabling the described =
mechanism to ultimately be reduced to an option in JSON serializers.
>=20
> The proposed work-item is tentatively named JSON Canonicalization =
Scheme (JCS)
>=20
> ### END
>=20
>=20
>=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
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon

--
Mark Nottingham   https://www.mnot.net/


From nobody Thu Jan 24 14:06:32 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 745CF130EE1 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:06: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, 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 rEA2-tWltjks for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:06:28 -0800 (PST)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 C85A9128AFB for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:06:27 -0800 (PST)
Received: by mail-wr1-x42b.google.com with SMTP id u4so8205118wrp.3 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:06:27 -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=n5wTszjkms6Cd1DkQXjMLTFn6bLIeU8cprbdfSnvWN0=; b=CFbwBOUzlOCSVrlfsuzVXwbyClaEIdDTzDxsghbKoZb0qFD/y1MzJJgmoTfwdAvTx7 nABN4xeqjubmkE8ojTtQ2TxWacz+nO8d0tdZEYBmeBSDbb/wI2dXQ8cPTzc2RX/a0ogH fX6KGW6GP6QdQVYFvz19Q2L6YSOo/ycTS3aYDMyzaMeJuCHAqFMgleMu21JkyzI8OSZP RVfw+v+h9FfzBtvikPxdWaYz/nkf4xyfSEC/iaKLqE6fkMoFRPmvgt1HNtmaUDvIXPQh 4cQ5pJsKwwNwTVjWDjAXPiG+AVIXpk213cqpgPU/+cDtkbglcq75f7LO87EdGEiJS/bD dz8Q==
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=n5wTszjkms6Cd1DkQXjMLTFn6bLIeU8cprbdfSnvWN0=; b=DXu0bl5f8MhVCNbd67JcQ7vXO41ojHGuAzriiCi9kM9JtNmsmwoLEk50LSFa++hHak thuxNLZxtvK+7+NYfIFWEcGoyoHodUp0oEfQwhlhqWUNhd9ohX1Yl3ivdi+T1U8VVBHP JcbdzOcMDEidlMrU8KLPzO1hgpJe00o2obwB27DqXIV3M2DRhtEBtJN/ISkbDRM/DDxT TSut+HXL2yziYtQx432H3S5trLv9krsT4GGO50bJPNFT4uEsXHSZ6RNSA4+ZrSCCt/B3 D4qD7mIDA8u3SB0bO4F+nddj+FbtxbHOMQQp4AO71YQ+Xo8TDpBxCUXh8bBU85ZD2Qbd GDyQ==
X-Gm-Message-State: AJcUukdMbZatIVe86LgqD+xQtlCw7uL+UUz6Ymf9+WzdKJJoqIQPxlyO 5wWodMdZLab/mz6r/AQEeli8LY9F
X-Google-Smtp-Source: ALg8bN5KJ4T0JHNzljSrmKqmLxjtfxmvreTm9Qw5uiuV1oek0gU7KzWrY6np2/aODPaMw6bt6flCYQ==
X-Received: by 2002:a5d:6aca:: with SMTP id u10mr8600320wrw.310.1548367585838;  Thu, 24 Jan 2019 14:06:25 -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 k23sm39248836wmj.32.2019.01.24.14.06.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 14:06:24 -0800 (PST)
To: Mark Nottingham <mnot@mnot.net>, Bret Jordan <jordan.ietf@gmail.com>
Cc: json-canon@ietf.org
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com>
Date: Thu, 24 Jan 2019 23:06:19 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net>
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/H6y_zeyXdEPlOM2cyaCLPXNscPA>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 22:06:30 -0000

On 2019-01-24 22:55, Mark Nottingham wrote:
> Will the Working Group limit itself to canonicalising the data model that's described by JSON's native data types (object, array, number, string, boolean, null), or will it attempt to canonicalise subtypes -- for example, inside strings (whether they be key or value)?

It is possible that I misunderstand your question but the charter talks about using

"...the serialization methods for JSON primitives defined by EcmaScript version 6"

which means that strings and numbers are normalized (null and boolean already have a fixed form).

Is this the explanation you miss?

thanx,
Anders

> 
> I'd be much more comfortable if this were addressed explicitly in the charter.
> 
> Cheers,
> 
> 
>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> wrote:
>>
>> All,
>>
>> Here is a proposed charter for this WG.  Please send any comments on this charter to this email list.
>>
>>
>>
>> ### BEGIN
>>
>> JavaScript Object Notation (JSON) is a text format for the serialization of structured data described in RFC 8259. The JSON format is often used for serializing and transmitting structured data over a network connection. With the increased usage of JSON in protocols in the IETF and elsewhere, there is now a need to define a canonical representation of JSON objects to enable comparison operations and security services on plain text JSON.
>>
>> Different proposals for providing such security services have already been defined and implemented. The goal of the Working Group is to define and standardize a mechanism for creating a canonical representation of plain text JSON objects.
>>
>> This group is chartered to work on the following deliverable:
>>
>> - A Standards Track document specifying a canonical representation of JSON data.
>>
>> In order to promote interoperability and ease of implementation, the current proposal builds on I-JSON (RFC 7493), the serialization methods for JSON primitives defined by EcmaScript version 6, and a platform-independent method for sorting object properties.  By doing that, JSON parsers will not need modifications, enabling the described mechanism to ultimately be reduced to an option in JSON serializers.
>>
>> The proposed work-item is tentatively named JSON Canonicalization Scheme (JCS)
>>
>> ### END
>>
>>
>>
>> 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."
>>
>> -- 
>> json-canon mailing list
>> json-canon@ietf.org
>> https://www.ietf.org/mailman/listinfo/json-canon
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 


From nobody Thu Jan 24 14:14:49 2019
Return-Path: <mnot@mnot.net>
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 C55D2130F2A for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:14:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=mnot.net header.b=WgGF58dQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MeCN1BFv
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 B_KHM-xJID_7 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:14:45 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93BDC130EE1 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:14:45 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 9157021F3C; Thu, 24 Jan 2019 17:14:43 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 24 Jan 2019 17:14:43 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=V TIodqmoBKMoekeIGO2oQnHgasj60qVj+ExFHpqGJYY=; b=WgGF58dQqxi6rOH5X zrYgZmlwzI0zOudIa9sFXh/u00UmjRtaT14BF8hdAwJp0Cw0AviXe8mUpIROALJI 2Tfpmgm1l5WYvAIO4ouEjoV/k4CqNJs56/1Vu9EYjLWEJWTPPtyV3i6kU7NL2EVc VLBg/m4ond4d6l1IUpTytHev6vScRV+jgARQmuMgX2PiWuN+65Pa7c8CphLxued5 +otaHQNb1dF/zFBojPZt9pf2teEJGPBKy74Z2s5zy6zsimjh2oAyUC2TPxH4OmcR rwW05exgcMr0CRlXc3SnsWtHTixuffx37btvbO4I3KU9SPMxC/r3vPPtxlf/2GRY 5Q04w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=VTIodqmoBKMoekeIGO2oQnHgasj60qVj+ExFHpqGJ YY=; b=MeCN1BFvfbgx1iHnstIPpryWfZ/1subn1fD9aHwLmPrNwCIogpbi7Bd95 7AylcqUltuVhf84/30K4AecYPptj06yvxUlPRKpgTKShAjd28ydR+86PIy5VfMRi vsATO+z6XK2NvYwSIYc1XsHzthxIstDaP47oNDv+/CYN77vLoFUmTAe5nWcuXtwm w4ifO2ZhRvtmM2YF+vX/c5bKapF6Bi+nNuY+RyS+WgOGYoVYqjGRUHu9HKC05h9B ZO6Cbnj8X7o4fVkHJlQEEne+1n9QKfXeKDW1ylZ4AbVSw7X7egDAT5dLXU+lfuvD 5XuU13hRu/revy2TT7Fb/CxMOUnwg==
X-ME-Sender: <xms:0jhKXEuJLSNPsu5znXBDYeix_7LbBSh6K5v7v69y_ovVDPC1LzFlPQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledriedvgdduheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjff fgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghm uceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpehivghtfhdrohhrghdpmh hnohhtrdhnvghtnecukfhppeekrddukedrvddujedrvddtvdenucfrrghrrghmpehmrghi lhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:0jhKXDTCiYQeaxSzzOW3ulCNw8Di6PIfYkKnseQmLSdwuF-6Rn7aDg> <xmx:0jhKXBiSd_FofNaIIukFqaZsH_hrOsM1qMGwas2yhIhZDjggnyzXuA> <xmx:0jhKXIaObIMu_8PDd_0tjUpYonYhds11FUyO5FHSqZZ5wfD1PMJ2Lg> <xmx:0zhKXObqW3HSCnHMlZNwQVt85Gs4CpupVwn3NL6DR4cfhF6tdIiZhQ>
Received: from [10.100.20.187] (unknown [8.18.217.202]) by mail.messagingengine.com (Postfix) with ESMTPA id 94D3DE4511; Thu, 24 Jan 2019 17:14:41 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com>
Date: Thu, 24 Jan 2019 14:14:38 -0800
Cc: Bret Jordan <jordan.ietf@gmail.com>, json-canon@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net>
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/iQVsfN9SZned2Lmu1fkyLhbZHhQ>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 22:14:48 -0000

I saw that, but it wasn't clear whether that was a starting point, or a =
limit.

Cheers,


> On 24 Jan 2019, at 2:06 pm, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>=20
> On 2019-01-24 22:55, Mark Nottingham wrote:
>> Will the Working Group limit itself to canonicalising the data model =
that's described by JSON's native data types (object, array, number, =
string, boolean, null), or will it attempt to canonicalise subtypes -- =
for example, inside strings (whether they be key or value)?
>=20
> It is possible that I misunderstand your question but the charter =
talks about using
>=20
> "...the serialization methods for JSON primitives defined by =
EcmaScript version 6"
>=20
> which means that strings and numbers are normalized (null and boolean =
already have a fixed form).
>=20
> Is this the explanation you miss?
>=20
> thanx,
> Anders
>=20
>> I'd be much more comfortable if this were addressed explicitly in the =
charter.
>> Cheers,
>>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> =
wrote:
>>>=20
>>> All,
>>>=20
>>> Here is a proposed charter for this WG.  Please send any comments on =
this charter to this email list.
>>>=20
>>>=20
>>>=20
>>> ### BEGIN
>>>=20
>>> JavaScript Object Notation (JSON) is a text format for the =
serialization of structured data described in RFC 8259. The JSON format =
is often used for serializing and transmitting structured data over a =
network connection. With the increased usage of JSON in protocols in the =
IETF and elsewhere, there is now a need to define a canonical =
representation of JSON objects to enable comparison operations and =
security services on plain text JSON.
>>>=20
>>> Different proposals for providing such security services have =
already been defined and implemented. The goal of the Working Group is =
to define and standardize a mechanism for creating a canonical =
representation of plain text JSON objects.
>>>=20
>>> This group is chartered to work on the following deliverable:
>>>=20
>>> - A Standards Track document specifying a canonical representation =
of JSON data.
>>>=20
>>> In order to promote interoperability and ease of implementation, the =
current proposal builds on I-JSON (RFC 7493), the serialization methods =
for JSON primitives defined by EcmaScript version 6, and a =
platform-independent method for sorting object properties.  By doing =
that, JSON parsers will not need modifications, enabling the described =
mechanism to ultimately be reduced to an option in JSON serializers.
>>>=20
>>> The proposed work-item is tentatively named JSON Canonicalization =
Scheme (JCS)
>>>=20
>>> ### END
>>>=20
>>>=20
>>>=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
>>> json-canon mailing list
>>> json-canon@ietf.org
>>> https://www.ietf.org/mailman/listinfo/json-canon
>> --
>> Mark Nottingham   https://www.mnot.net/
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Thu Jan 24 14:40:22 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 6F42E13117B for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:40:20 -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 CS9O2wl-6kEt for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:40:18 -0800 (PST)
Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (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 A7428130EE1 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:40:17 -0800 (PST)
Received: by mail-wr1-x442.google.com with SMTP id u4so8281962wrp.3 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:40:17 -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=zD/f0mJQ7VMSH/PetD9ZIwtFjVJl5Pd0Qc9I7SxyNx4=; b=YQT0n341g8ZzXvNibcZHy+stLYGyq9Ws4tMfcQN+gBHFcFLXQNZ/4rkKxbwyQQBsVF QqvBEzNtzpAiGL0XY9pSEvlu0b/Ra2CFlik4SBqi0p3d7SlfQUnihD3mniapiO/eDXCE 9XFB/ovHRpG5y8VhKASmPmWNkcRO1zW/X0Np8h0+kV3Q5chi1XtiPqzJJ/l1FvdhqhV4 f7R26VoVPr8KE3ohXnu2cmv4qPKSnphupWMWlfG5Pt3F2w9RdlBJ4WaW6unuwtghi5fJ 00NHNcEaF8vJSysgIEjEkngd29x2JQXVoGPkn6if4EN8BbNqNLR+iUJcqDfkEeMl3dpn 6rSw==
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=zD/f0mJQ7VMSH/PetD9ZIwtFjVJl5Pd0Qc9I7SxyNx4=; b=Xar/wSG4oZ/z86I51iQfINx/6894b/MdPlrO57cQ6i3V5wUGt06ezcTrMJPH+WP8bz SKXdeolteltoW1cgMOiwtE7zqGmP+FYZzz7zIV4yPL0FZFVgyGx/PhjAfncKq4CtTaZC ZScxANG7PNwOo8ar7c58tybazcQMOiDvgwOAkyaUn4StYJw9/fZGD/GxkFnbdBoIhXNO 1WslNG1+JDd7b6l7lUJs5VB/h9RPhRmGmlrsAqJtuiBygQeyZGFbtAyeSIbK8Uv0Ms6+ FnWuK9XuQHBRiyANTrEjcfbS6niDKiMrxATy1nvZb4Wai4C9mSwo12jSgrP+Qe4rES0V XAdA==
X-Gm-Message-State: AJcUukfUVtqO5SkZ65BvRV7y9nQ12RMhmM+F22VYEUFH5lm24BA60w/g 3VuZV+RVgiJ8r1rzuKdKQO7836zS
X-Google-Smtp-Source: ALg8bN61c+86J/fyI78eFTbHhYWt4q7hPwPOg//3krjBF7HnJTnpnsTf4+WI2vrjP0M76IOwlvOjyA==
X-Received: by 2002:adf:fe43:: with SMTP id m3mr8716711wrs.290.1548369615658;  Thu, 24 Jan 2019 14:40:15 -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 202sm73630911wmt.8.2019.01.24.14.40.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 14:40:14 -0800 (PST)
To: Mark Nottingham <mnot@mnot.net>
Cc: Bret Jordan <jordan.ietf@gmail.com>, json-canon@ietf.org
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com> <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com>
Date: Thu, 24 Jan 2019 23:40:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net>
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/4-_STT-XZZnI9qvwc8D3PZlf_Gw>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 22:40:20 -0000

On 2019-01-24 23:14, Mark Nottingham wrote:
> I saw that, but it wasn't clear whether that was a starting point, or a limit.

It is the current proposal/definition.  It limits the JSON Number type to IEEE-754 double precision (=strict I-JSON).

https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-03#section-3.2.2.3

Do you think this should be in the charter?

thanx,
Anders

> 
> Cheers,
> 
> 
>> On 24 Jan 2019, at 2:06 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>
>> On 2019-01-24 22:55, Mark Nottingham wrote:
>>> Will the Working Group limit itself to canonicalising the data model that's described by JSON's native data types (object, array, number, string, boolean, null), or will it attempt to canonicalise subtypes -- for example, inside strings (whether they be key or value)?
>>
>> It is possible that I misunderstand your question but the charter talks about using
>>
>> "...the serialization methods for JSON primitives defined by EcmaScript version 6"
>>
>> which means that strings and numbers are normalized (null and boolean already have a fixed form).
>>
>> Is this the explanation you miss?
>>
>> thanx,
>> Anders
>>
>>> I'd be much more comfortable if this were addressed explicitly in the charter.
>>> Cheers,
>>>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> wrote:
>>>>
>>>> All,
>>>>
>>>> Here is a proposed charter for this WG.  Please send any comments on this charter to this email list.
>>>>
>>>>
>>>>
>>>> ### BEGIN
>>>>
>>>> JavaScript Object Notation (JSON) is a text format for the serialization of structured data described in RFC 8259. The JSON format is often used for serializing and transmitting structured data over a network connection. With the increased usage of JSON in protocols in the IETF and elsewhere, there is now a need to define a canonical representation of JSON objects to enable comparison operations and security services on plain text JSON.
>>>>
>>>> Different proposals for providing such security services have already been defined and implemented. The goal of the Working Group is to define and standardize a mechanism for creating a canonical representation of plain text JSON objects.
>>>>
>>>> This group is chartered to work on the following deliverable:
>>>>
>>>> - A Standards Track document specifying a canonical representation of JSON data.
>>>>
>>>> In order to promote interoperability and ease of implementation, the current proposal builds on I-JSON (RFC 7493), the serialization methods for JSON primitives defined by EcmaScript version 6, and a platform-independent method for sorting object properties.  By doing that, JSON parsers will not need modifications, enabling the described mechanism to ultimately be reduced to an option in JSON serializers.
>>>>
>>>> The proposed work-item is tentatively named JSON Canonicalization Scheme (JCS)
>>>>
>>>> ### END
>>>>
>>>>
>>>>
>>>> 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."
>>>>
>>>> -- 
>>>> json-canon mailing list
>>>> json-canon@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>> --
>>> Mark Nottingham   https://www.mnot.net/
>>
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 


From nobody Thu Jan 24 14:42:35 2019
Return-Path: <mnot@mnot.net>
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 DB9DE1311D7 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:42:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=mnot.net header.b=1BNrRYd+; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=E8c+rEc/
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 AF0dEAmFWBx5 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:42:30 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D331813117B for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:42:29 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D0AC022158; Thu, 24 Jan 2019 17:42:28 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 24 Jan 2019 17:42:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=4 ZTktssK+g2GPKbuoPKjhtedM6w6/Q10CvfJmXpXHLE=; b=1BNrRYd+xPXsXe2Dk o37WZQGIzYyqMGgTC0Za5MqAtJE01o26v1HOZfpFq2QyTly5vQtHVQ3iaFz0wcfn 3UNIhZYpeZby5M6WNlFarhVOI3KGQw+PARbuV9I1h6nY6PoKgbbOMJZS2lVP0Wjh 6GGX1yuUjftOIwA2A7JDoGbOuJT2ZT0MVCCyHl2MzZEOOe6MNUL+fsdvlwmsnPNd etB9sy6wTEtOqSpYTL/UcI0S2Z/bkNENI2BB8J8rbYcgkIAfGI3Iw2Xy55YyPL6g e6DilwPRMMPnhyI3lj8blJSHUwGY23DDuxInrLw8bOFgdQAxbhwb+GI7J8Bp4b14 Uss+g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=4ZTktssK+g2GPKbuoPKjhtedM6w6/Q10CvfJmXpXH LE=; b=E8c+rEc/ni8nVrtOQj+d0ek2NTsEV+inZ9xsJmwUIuB9MsWpJZCds+Ej5 Mc/l7IAEP6P5UrOIqHXi0iIds7IZW6WZpZBGsHgU/88lnGm/ebNmfH58tiQABxaQ 7q8me6YW7hbYAgO/lYSj5mNa9Z6fNvqk+zlXRC2EgEdF9BtV1aCp5RvxN8ejEiLH 6uWjkox4JMZ5dX8Q/xVOn5dQPaHlDY+7+DVGn83oKyasgJ34mqGwBEOeieSCLYGz BExt4yXsQmnbsHOpzIqCfZVIn6I3In4nkmAiOwrDA4BrNVEqV02lTSnAqyIS9A3V aLVAM3DVWQTdNSebmu/L9jyPX7LNA==
X-ME-Sender: <xms:Uz9KXPTrm4iipRTRDkiZA2YcvNEM43ammCf4fORmEJ39YqWpLZgPnA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrieefgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurheptggguffhjgffgf fkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcu oehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepihgvthhfrdhorhhgpdhmnh hothdrnhgvthenucfkphepkedrudekrddvudejrddvtddvnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:Uz9KXFZQf9IsFAyEseQn_yvv3N1dl7q-aYBGRp3z5WMgvTXpC1lIVw> <xmx:Uz9KXM8PO2FCyv3e_G0iPFCF9X5WV9bysiPYGB21HPPLBLE-XK53iQ> <xmx:Uz9KXJLDCt822QoXg8H_lK-pCXAtA9F9DG3O-ATnbotvwA8rtEvOgw> <xmx:VD9KXHkcLpdqmirPHkrvRAnboeR5dcq2ZvIkgNBe_LpZvl_ajZ0JLQ>
Received: from [10.100.20.187] (unknown [8.18.217.202]) by mail.messagingengine.com (Postfix) with ESMTPA id EC840E4394; Thu, 24 Jan 2019 17:42:26 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com>
Date: Thu, 24 Jan 2019 14:42:23 -0800
Cc: Bret Jordan <jordan.ietf@gmail.com>, json-canon@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net>
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com> <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net> <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/4ch8ojN5qt8xtJ3i8WmI9Jmy33M>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 22:42:33 -0000

I'm primarily concerned that people will want to invite new subtypes, =
e.g. "base64'd binary in a string." A good charter would make that =
clearly in or out of scope.

Cheers,


> On 24 Jan 2019, at 2:40 pm, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>=20
> On 2019-01-24 23:14, Mark Nottingham wrote:
>> I saw that, but it wasn't clear whether that was a starting point, or =
a limit.
>=20
> It is the current proposal/definition.  It limits the JSON Number type =
to IEEE-754 double precision (=3Dstrict I-JSON).
>=20
> =
https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-03=
#section-3.2.2.3
>=20
> Do you think this should be in the charter?
>=20
> thanx,
> Anders
>=20
>> Cheers,
>>> On 24 Jan 2019, at 2:06 pm, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>>>=20
>>> On 2019-01-24 22:55, Mark Nottingham wrote:
>>>> Will the Working Group limit itself to canonicalising the data =
model that's described by JSON's native data types (object, array, =
number, string, boolean, null), or will it attempt to canonicalise =
subtypes -- for example, inside strings (whether they be key or value)?
>>>=20
>>> It is possible that I misunderstand your question but the charter =
talks about using
>>>=20
>>> "...the serialization methods for JSON primitives defined by =
EcmaScript version 6"
>>>=20
>>> which means that strings and numbers are normalized (null and =
boolean already have a fixed form).
>>>=20
>>> Is this the explanation you miss?
>>>=20
>>> thanx,
>>> Anders
>>>=20
>>>> I'd be much more comfortable if this were addressed explicitly in =
the charter.
>>>> Cheers,
>>>>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> =
wrote:
>>>>>=20
>>>>> All,
>>>>>=20
>>>>> Here is a proposed charter for this WG.  Please send any comments =
on this charter to this email list.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> ### BEGIN
>>>>>=20
>>>>> JavaScript Object Notation (JSON) is a text format for the =
serialization of structured data described in RFC 8259. The JSON format =
is often used for serializing and transmitting structured data over a =
network connection. With the increased usage of JSON in protocols in the =
IETF and elsewhere, there is now a need to define a canonical =
representation of JSON objects to enable comparison operations and =
security services on plain text JSON.
>>>>>=20
>>>>> Different proposals for providing such security services have =
already been defined and implemented. The goal of the Working Group is =
to define and standardize a mechanism for creating a canonical =
representation of plain text JSON objects.
>>>>>=20
>>>>> This group is chartered to work on the following deliverable:
>>>>>=20
>>>>> - A Standards Track document specifying a canonical representation =
of JSON data.
>>>>>=20
>>>>> In order to promote interoperability and ease of implementation, =
the current proposal builds on I-JSON (RFC 7493), the serialization =
methods for JSON primitives defined by EcmaScript version 6, and a =
platform-independent method for sorting object properties.  By doing =
that, JSON parsers will not need modifications, enabling the described =
mechanism to ultimately be reduced to an option in JSON serializers.
>>>>>=20
>>>>> The proposed work-item is tentatively named JSON Canonicalization =
Scheme (JCS)
>>>>>=20
>>>>> ### END
>>>>>=20
>>>>>=20
>>>>>=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
>>>>> json-canon mailing list
>>>>> json-canon@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>> --
>>>> Mark Nottingham   https://www.mnot.net/
>>>=20
>> --
>> Mark Nottingham   https://www.mnot.net/
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Thu Jan 24 14:46:52 2019
Return-Path: <athomson@lookingglasscyber.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 9A9761311EA for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level: 
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lookingglasscyber.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 2KhMBchAVswH for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:46:47 -0800 (PST)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-co1nam04on0611.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe4d::611]) (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 9DBFB1311D7 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:46:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lookingglasscyber.com;  s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QeJIhK5WZDrAi9qKROivbC/lvouOwZoIHs4fRBhGmSQ=; b=h8ZaGu/kM1NR32vmrBjY+539pelh4vcddNWXScJKOOBjel5s5nc8l3CuO+lAZpMLInsEX8q0tHrq/IuAAucUB10d9wrd4jIS4WWMLq2TjmLpGmxRTyxkWIZ606JIlp7UAvBs1Rvb88Z8+xk307Iud36kIrUfnDFz6TwW0j7Mtvk=
Received: from MW2PR18MB2137.namprd18.prod.outlook.com (52.132.182.156) by MW2PR18MB2121.namprd18.prod.outlook.com (52.132.182.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1537.27; Thu, 24 Jan 2019 22:46:44 +0000
Received: from MW2PR18MB2137.namprd18.prod.outlook.com ([fe80::198d:2eea:38e4:3ecb]) by MW2PR18MB2137.namprd18.prod.outlook.com ([fe80::198d:2eea:38e4:3ecb%5]) with mapi id 15.20.1537.032; Thu, 24 Jan 2019 22:46:44 +0000
From: Allan Thomson <athomson@lookingglasscyber.com>
To: Mark Nottingham <mnot@mnot.net>, Anders Rundgren <anders.rundgren.net@gmail.com>
CC: Bret Jordan <jordan.ietf@gmail.com>, "json-canon@ietf.org" <json-canon@ietf.org>
Thread-Topic: [Json-canon] Proposed Charter
Thread-Index: AQHUtBaefNxtoK7zqUiixF77CTBhlKW+9sYAgAADHYCAAAJTAIAAByAAgAAAoYD//3sagA==
Date: Thu, 24 Jan 2019 22:46:44 +0000
Message-ID: <741572B2-8826-41F4-B15D-E538141771BF@lookingglasscyber.com>
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com> <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net> <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com> <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net>
In-Reply-To: <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.15.0.190115
authentication-results: spf=none (sender IP is ) smtp.mailfrom=athomson@lookingglasscyber.com; 
x-originating-ip: [144.202.253.180]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MW2PR18MB2121; 6:XvDtR1onvDaoJjxRuCDBUKxKKhA/C0MBHsZFziLbq0jqL9w79s37tPUWxan0HCkPGM+XkATZ51lvkC69EOuNLRCpTLS+zK8UxXpxmis9uHT/2vzw3b3gKDEKS3VcW0KiNlrC41fuMDFWucAvFLggO3vUrrKSmH35s5wqcxwJtEc3edMkNhyD+oHrPmyXclWVqU/EwEXC635f/WgmVcp0zLMBD3na6esUy+W19BO4TNTJBj4CA8Ug4EsmqaKoAWSWYFBO7ksfw3YB6Qt58T28BW47GjaHcIj/RnlOaatYVXzzQ89ge687LS0bCYxhKmfY+SJi6Zhyo9Nc1jFFfchsvKpDUjp5HeHE7+rf4TO8fIogPvxQtiTtpnQXTBfonWfZVlxAoYgaZ1BWb9W6LkKhPXMFEk9YpFE883Q3775Sz5a+qxjsFx4o1tkg0G4o6ZQ7+xW+hS9hcOp3cEJVgNsuNg==; 5:2lVJQiGeMhV/L6Rb2L2lWPD/tUGRbdLZT0CenskDzYtYjhUedbt5/bFnRgKnQG3GKfVBK4AG/jm/g/3uRlSUcRZxjDEFef80dJe4azXw8+hICxMhSEnRmMU7kMXRMGV7f1wJLOlCrglz3TWeQB18gqbbi3dQXO0bipfwYYful4Eax5lq25MDQ5HysZScJPOdPDhCV1IdMw7vb0dNB5oPvQ==; 7:EiyUjIU0PKqmtOudPi7bdHRep9ET4UyDZgWU3n4Hq47QJtrLBfDbVBRIruqzbFTmEu2pQ1ycmPDr5+JvAme7MSpu7FanoaLe0apMWc9xQT7NyoRrWQu4xbQ1AsAHHGcYq/GXQyTlmrPZHQHl9r8n+Q==
x-ms-office365-filtering-correlation-id: a32e1153-7d72-4c42-177b-08d6824dd0f5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600110)(711020)(4605077)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:MW2PR18MB2121; 
x-ms-traffictypediagnostic: MW2PR18MB2121:
x-microsoft-antispam-prvs: <MW2PR18MB2121ED884D7E7E0B4E2984C3DA9A0@MW2PR18MB2121.namprd18.prod.outlook.com>
x-forefront-prvs: 0927AA37C7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(136003)(376002)(39850400004)(396003)(346002)(189003)(199004)(8676002)(97736004)(229853002)(2616005)(102836004)(6486002)(476003)(82746002)(81166006)(8936002)(7736002)(36756003)(86362001)(6436002)(11346002)(53936002)(305945005)(76176011)(966005)(81156014)(68736007)(6306002)(6512007)(478600001)(99286004)(105586002)(446003)(14454004)(106356001)(93886005)(256004)(58126008)(186003)(110136005)(53546011)(14444005)(39060400002)(316002)(6506007)(66066001)(6116002)(54906003)(71190400001)(25786009)(33656002)(26005)(486006)(4326008)(2906002)(6246003)(561944003)(83716004)(71200400001)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:MW2PR18MB2121; H:MW2PR18MB2137.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: lookingglasscyber.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: iR8IVXURhMwnAZ0MPPdRKL4FFh4Hk6yD2Qyls0xd/e4H/P04wANyTq8XnFy2zk4FnCUB961iC/Hv8FMnQZJ/cMuExfpYQ2AURrY7cW8judImbOKG+KrsZ5i8B/ZZcgktAWpwDE3TkJCT+qgp/Z4thA+NN3ZQT+p3dgMAaQnsoTiP4j9DCFBGscVudXCx2Wm5hmkh/SPGxVIwbskLaZZVjBG7gKu3lCVVVhNtDvQMHFC5qIlF030WOf/Vv60ozYAI5CXKCYmyBNIeaiOkYmuuO3CNEQUTHKaKOot2RiYfsnyDEP8s9opIQ7guqnNHYNk8Wv92Z9R1NGe019OUrB8Udr3iq7jL1VUI4dSX8wIm0uAbsxJeJ67V/7gZN16dq0gsYuj8PboCilrIO1nr3j5YUJRRo+NrrhfyJ1s4YYjG9XQ=
Content-Type: text/plain; charset="utf-8"
Content-ID: <4DF245AB50CDA343BE307D045DCFA66E@namprd18.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: lookingglasscyber.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a32e1153-7d72-4c42-177b-08d6824dd0f5
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jan 2019 22:46:44.7600 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 11622456-b9ab-4329-8602-bf364508a848
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR18MB2121
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/nbev_RcQdNSK1L70D5i_FRH0KMU>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 22:46:50 -0000

Q3VycmVudGx5LCBtYW55ICpkbyogZGVmaW5lIGJhc2U2NCBiaW5hcnkgYXMgc3RyaW5ncyBpbiBK
U09OIGFuZCB0aGlzIGVmZm9ydCB3b3VsZCBiZSBtb3JlIHVzZWZ1bCB0byB0aGVtIGlmIGl0IGlu
Y2x1ZGVkIHRoZW0uDQoNCkknbSBub3Qgc3VyZSB3aHkgd2Ugd291bGQgd2FudCB0byBiZSBzbyBw
cmVzY3JpcHRpdmUgb3IgcmVzdHJpY3RpdmUgb24gZXZlcnkgbGFzdCBkYXRhIHR5cGUuIEl0IHNl
ZW1zIGxpa2UgaWYgYSByZWFzb25hYmxlIHVzZSBjYXNlIHJlcXVpcmVzIGEgZGF0YSB0eXBlIGJl
aW5nIGluY2x1ZGVkIHRoZW4gaGF2aW5nIHRvIHJlZG8gdGhlIGNoYXJ0ZXIganVzdCB0byBpbmNs
dWRlIGl0IHNlZW1zIGN1bWJlcnNvbWUuDQoNCkFsbGFuDQoNCu+7v09uIDEvMjQvMTksIDI6NDIg
UE0sICJqc29uLWNhbm9uIG9uIGJlaGFsZiBvZiBNYXJrIE5vdHRpbmdoYW0iIDxqc29uLWNhbm9u
LWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIG1ub3RAbW5vdC5uZXQ+IHdyb3RlOg0KDQog
ICAgSSdtIHByaW1hcmlseSBjb25jZXJuZWQgdGhhdCBwZW9wbGUgd2lsbCB3YW50IHRvIGludml0
ZSBuZXcgc3VidHlwZXMsIGUuZy4gImJhc2U2NCdkIGJpbmFyeSBpbiBhIHN0cmluZy4iIEEgZ29v
ZCBjaGFydGVyIHdvdWxkIG1ha2UgdGhhdCBjbGVhcmx5IGluIG9yIG91dCBvZiBzY29wZS4NCiAg
ICANCiAgICBDaGVlcnMsDQogICAgDQogICAgDQogICAgPiBPbiAyNCBKYW4gMjAxOSwgYXQgMjo0
MCBwbSwgQW5kZXJzIFJ1bmRncmVuIDxhbmRlcnMucnVuZGdyZW4ubmV0QGdtYWlsLmNvbT4gd3Jv
dGU6DQogICAgPiANCiAgICA+IE9uIDIwMTktMDEtMjQgMjM6MTQsIE1hcmsgTm90dGluZ2hhbSB3
cm90ZToNCiAgICA+PiBJIHNhdyB0aGF0LCBidXQgaXQgd2Fzbid0IGNsZWFyIHdoZXRoZXIgdGhh
dCB3YXMgYSBzdGFydGluZyBwb2ludCwgb3IgYSBsaW1pdC4NCiAgICA+IA0KICAgID4gSXQgaXMg
dGhlIGN1cnJlbnQgcHJvcG9zYWwvZGVmaW5pdGlvbi4gIEl0IGxpbWl0cyB0aGUgSlNPTiBOdW1i
ZXIgdHlwZSB0byBJRUVFLTc1NCBkb3VibGUgcHJlY2lzaW9uICg9c3RyaWN0IEktSlNPTikuDQog
ICAgPiANCiAgICA+IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ydW5kZ3Jlbi1q
c29uLWNhbm9uaWNhbGl6YXRpb24tc2NoZW1lLTAzI3NlY3Rpb24tMy4yLjIuMw0KICAgID4gDQog
ICAgPiBEbyB5b3UgdGhpbmsgdGhpcyBzaG91bGQgYmUgaW4gdGhlIGNoYXJ0ZXI/DQogICAgPiAN
CiAgICA+IHRoYW54LA0KICAgID4gQW5kZXJzDQogICAgPiANCiAgICA+PiBDaGVlcnMsDQogICAg
Pj4+IE9uIDI0IEphbiAyMDE5LCBhdCAyOjA2IHBtLCBBbmRlcnMgUnVuZGdyZW4gPGFuZGVycy5y
dW5kZ3Jlbi5uZXRAZ21haWwuY29tPiB3cm90ZToNCiAgICA+Pj4gDQogICAgPj4+IE9uIDIwMTkt
MDEtMjQgMjI6NTUsIE1hcmsgTm90dGluZ2hhbSB3cm90ZToNCiAgICA+Pj4+IFdpbGwgdGhlIFdv
cmtpbmcgR3JvdXAgbGltaXQgaXRzZWxmIHRvIGNhbm9uaWNhbGlzaW5nIHRoZSBkYXRhIG1vZGVs
IHRoYXQncyBkZXNjcmliZWQgYnkgSlNPTidzIG5hdGl2ZSBkYXRhIHR5cGVzIChvYmplY3QsIGFy
cmF5LCBudW1iZXIsIHN0cmluZywgYm9vbGVhbiwgbnVsbCksIG9yIHdpbGwgaXQgYXR0ZW1wdCB0
byBjYW5vbmljYWxpc2Ugc3VidHlwZXMgLS0gZm9yIGV4YW1wbGUsIGluc2lkZSBzdHJpbmdzICh3
aGV0aGVyIHRoZXkgYmUga2V5IG9yIHZhbHVlKT8NCiAgICA+Pj4gDQogICAgPj4+IEl0IGlzIHBv
c3NpYmxlIHRoYXQgSSBtaXN1bmRlcnN0YW5kIHlvdXIgcXVlc3Rpb24gYnV0IHRoZSBjaGFydGVy
IHRhbGtzIGFib3V0IHVzaW5nDQogICAgPj4+IA0KICAgID4+PiAiLi4udGhlIHNlcmlhbGl6YXRp
b24gbWV0aG9kcyBmb3IgSlNPTiBwcmltaXRpdmVzIGRlZmluZWQgYnkgRWNtYVNjcmlwdCB2ZXJz
aW9uIDYiDQogICAgPj4+IA0KICAgID4+PiB3aGljaCBtZWFucyB0aGF0IHN0cmluZ3MgYW5kIG51
bWJlcnMgYXJlIG5vcm1hbGl6ZWQgKG51bGwgYW5kIGJvb2xlYW4gYWxyZWFkeSBoYXZlIGEgZml4
ZWQgZm9ybSkuDQogICAgPj4+IA0KICAgID4+PiBJcyB0aGlzIHRoZSBleHBsYW5hdGlvbiB5b3Ug
bWlzcz8NCiAgICA+Pj4gDQogICAgPj4+IHRoYW54LA0KICAgID4+PiBBbmRlcnMNCiAgICA+Pj4g
DQogICAgPj4+PiBJJ2QgYmUgbXVjaCBtb3JlIGNvbWZvcnRhYmxlIGlmIHRoaXMgd2VyZSBhZGRy
ZXNzZWQgZXhwbGljaXRseSBpbiB0aGUgY2hhcnRlci4NCiAgICA+Pj4+IENoZWVycywNCiAgICA+
Pj4+PiBPbiAyNCBKYW4gMjAxOSwgYXQgMTA6NTYgYW0sIEJyZXQgSm9yZGFuIDxqb3JkYW4uaWV0
ZkBnbWFpbC5jb20+IHdyb3RlOg0KICAgID4+Pj4+IA0KICAgID4+Pj4+IEFsbCwNCiAgICA+Pj4+
PiANCiAgICA+Pj4+PiBIZXJlIGlzIGEgcHJvcG9zZWQgY2hhcnRlciBmb3IgdGhpcyBXRy4gIFBs
ZWFzZSBzZW5kIGFueSBjb21tZW50cyBvbiB0aGlzIGNoYXJ0ZXIgdG8gdGhpcyBlbWFpbCBsaXN0
Lg0KICAgID4+Pj4+IA0KICAgID4+Pj4+IA0KICAgID4+Pj4+IA0KICAgID4+Pj4+ICMjIyBCRUdJ
Tg0KICAgID4+Pj4+IA0KICAgID4+Pj4+IEphdmFTY3JpcHQgT2JqZWN0IE5vdGF0aW9uIChKU09O
KSBpcyBhIHRleHQgZm9ybWF0IGZvciB0aGUgc2VyaWFsaXphdGlvbiBvZiBzdHJ1Y3R1cmVkIGRh
dGEgZGVzY3JpYmVkIGluIFJGQyA4MjU5LiBUaGUgSlNPTiBmb3JtYXQgaXMgb2Z0ZW4gdXNlZCBm
b3Igc2VyaWFsaXppbmcgYW5kIHRyYW5zbWl0dGluZyBzdHJ1Y3R1cmVkIGRhdGEgb3ZlciBhIG5l
dHdvcmsgY29ubmVjdGlvbi4gV2l0aCB0aGUgaW5jcmVhc2VkIHVzYWdlIG9mIEpTT04gaW4gcHJv
dG9jb2xzIGluIHRoZSBJRVRGIGFuZCBlbHNld2hlcmUsIHRoZXJlIGlzIG5vdyBhIG5lZWQgdG8g
ZGVmaW5lIGEgY2Fub25pY2FsIHJlcHJlc2VudGF0aW9uIG9mIEpTT04gb2JqZWN0cyB0byBlbmFi
bGUgY29tcGFyaXNvbiBvcGVyYXRpb25zIGFuZCBzZWN1cml0eSBzZXJ2aWNlcyBvbiBwbGFpbiB0
ZXh0IEpTT04uDQogICAgPj4+Pj4gDQogICAgPj4+Pj4gRGlmZmVyZW50IHByb3Bvc2FscyBmb3Ig
cHJvdmlkaW5nIHN1Y2ggc2VjdXJpdHkgc2VydmljZXMgaGF2ZSBhbHJlYWR5IGJlZW4gZGVmaW5l
ZCBhbmQgaW1wbGVtZW50ZWQuIFRoZSBnb2FsIG9mIHRoZSBXb3JraW5nIEdyb3VwIGlzIHRvIGRl
ZmluZSBhbmQgc3RhbmRhcmRpemUgYSBtZWNoYW5pc20gZm9yIGNyZWF0aW5nIGEgY2Fub25pY2Fs
IHJlcHJlc2VudGF0aW9uIG9mIHBsYWluIHRleHQgSlNPTiBvYmplY3RzLg0KICAgID4+Pj4+IA0K
ICAgID4+Pj4+IFRoaXMgZ3JvdXAgaXMgY2hhcnRlcmVkIHRvIHdvcmsgb24gdGhlIGZvbGxvd2lu
ZyBkZWxpdmVyYWJsZToNCiAgICA+Pj4+PiANCiAgICA+Pj4+PiAtIEEgU3RhbmRhcmRzIFRyYWNr
IGRvY3VtZW50IHNwZWNpZnlpbmcgYSBjYW5vbmljYWwgcmVwcmVzZW50YXRpb24gb2YgSlNPTiBk
YXRhLg0KICAgID4+Pj4+IA0KICAgID4+Pj4+IEluIG9yZGVyIHRvIHByb21vdGUgaW50ZXJvcGVy
YWJpbGl0eSBhbmQgZWFzZSBvZiBpbXBsZW1lbnRhdGlvbiwgdGhlIGN1cnJlbnQgcHJvcG9zYWwg
YnVpbGRzIG9uIEktSlNPTiAoUkZDIDc0OTMpLCB0aGUgc2VyaWFsaXphdGlvbiBtZXRob2RzIGZv
ciBKU09OIHByaW1pdGl2ZXMgZGVmaW5lZCBieSBFY21hU2NyaXB0IHZlcnNpb24gNiwgYW5kIGEg
cGxhdGZvcm0taW5kZXBlbmRlbnQgbWV0aG9kIGZvciBzb3J0aW5nIG9iamVjdCBwcm9wZXJ0aWVz
LiAgQnkgZG9pbmcgdGhhdCwgSlNPTiBwYXJzZXJzIHdpbGwgbm90IG5lZWQgbW9kaWZpY2F0aW9u
cywgZW5hYmxpbmcgdGhlIGRlc2NyaWJlZCBtZWNoYW5pc20gdG8gdWx0aW1hdGVseSBiZSByZWR1
Y2VkIHRvIGFuIG9wdGlvbiBpbiBKU09OIHNlcmlhbGl6ZXJzLg0KICAgID4+Pj4+IA0KICAgID4+
Pj4+IFRoZSBwcm9wb3NlZCB3b3JrLWl0ZW0gaXMgdGVudGF0aXZlbHkgbmFtZWQgSlNPTiBDYW5v
bmljYWxpemF0aW9uIFNjaGVtZSAoSkNTKQ0KICAgID4+Pj4+IA0KICAgID4+Pj4+ICMjIyBFTkQN
CiAgICA+Pj4+PiANCiAgICA+Pj4+PiANCiAgICA+Pj4+PiANCiAgICA+Pj4+PiBUaGFua3MsDQog
ICAgPj4+Pj4gQnJldA0KICAgID4+Pj4+IFBHUCBGaW5nZXJwcmludDogNjNCNCBGQzUzIDY4MEEg
NkI3RCAxNDQ3ICBGMkMwIDc0RjggQUNBRSA3NDE1IDAwNTANCiAgICA+Pj4+PiAiV2l0aG91dCBj
cnlwdG9ncmFwaHkgdmlodiB2aXZjIGNlIHhocm5ydywgaG93ZXZlciwgdGhlIG9ubHkgdGhpbmcg
dGhhdCBjYW4gbm90IGJlIHVuc2NyYW1ibGVkIGlzIGFuIGVnZy4iDQogICAgPj4+Pj4gDQogICAg
Pj4+Pj4gLS0gDQogICAgPj4+Pj4ganNvbi1jYW5vbiBtYWlsaW5nIGxpc3QNCiAgICA+Pj4+PiBq
c29uLWNhbm9uQGlldGYub3JnDQogICAgPj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9qc29uLWNhbm9uDQogICAgPj4+PiAtLQ0KICAgID4+Pj4gTWFyayBOb3R0aW5n
aGFtICAgaHR0cHM6Ly93d3cubW5vdC5uZXQvDQogICAgPj4+IA0KICAgID4+IC0tDQogICAgPj4g
TWFyayBOb3R0aW5naGFtICAgaHR0cHM6Ly93d3cubW5vdC5uZXQvDQogICAgPiANCiAgICANCiAg
ICAtLQ0KICAgIE1hcmsgTm90dGluZ2hhbSAgIGh0dHBzOi8vd3d3Lm1ub3QubmV0Lw0KICAgIA0K
ICAgIC0tIA0KICAgIGpzb24tY2Fub24gbWFpbGluZyBsaXN0DQogICAganNvbi1jYW5vbkBpZXRm
Lm9yZw0KICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vanNvbi1jYW5v
bg0KICAgIA0KDQo=


From nobody Thu Jan 24 14:49:18 2019
Return-Path: <mnot@mnot.net>
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 AE60C1311DE for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=mnot.net header.b=VuGCXC+r; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=wgjeBN1O
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 px-xQBPq2c7C for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:49:14 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B4BB13117B for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:49:14 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id AA5DA21DE0; Thu, 24 Jan 2019 17:49:12 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 24 Jan 2019 17:49:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=P UNmhC+5Qgx8iJPg3/DhFH8er35PwGakDRBBVXEj8KM=; b=VuGCXC+r20+o7XCuB JoKXTI1dNhLlyYkoPC+v11SjtNMJm9GkP9xcA0VkZoau0x1FCXDWz2MP+PJWcTfp qF8qI6sozW7vA1AGoIyOvQsS1A1lvzDaYSF3jxPsMl8DJ9pE319EyMUjIBbEBHWA sZ/Y7+RWFAnNS7t6rb7Z8klM84MkT5CMVTWzVt0//tX6vki/lQriraKgF8t4b0Yp JqhU2FN6/Ytuz08WBw+5wCmamSLM1ng/dYNTlhqBcsRO2Sh8YsAzTOq/L9T7Opck f0gNNP+cp5ji2oY0z37Qg5GapH0YC1KBJbxiaHh+uQA93FmMQ3yVYrvq6huqKCED IWFww==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=PUNmhC+5Qgx8iJPg3/DhFH8er35PwGakDRBBVXEj8 KM=; b=wgjeBN1Oon92qBAh42mi0te03aCNuavw7S/LNxiJuGMZFhd8BKmbXDsS8 fuqM8gMf5ecoBlbnWNFNbxWxQeK77vC3KEx20OlSrzPTfDPUGgunAPIesIP3RiIf vwIApu8NA3KNXgeKH/8/EtfIq2PnxGlcCA1y9f/CwtkAf8CfRa7lPnd1m+iQQJJp Cy1XRK/1W5SX4i+4XAqAgnJjwaLDlRI9317uiovSVkR5XZ2yEcLLWxkc/WmUpJk1 yzHQRnh8ZWgoNf5xbCbBfFcM51nxPH/YVfDnfr0ak+NpRxoBMsaYzy4bJ9PXuVcE p6XSKxDovdwl9EYc1N8VWFhwb7nNQ==
X-ME-Sender: <xms:50BKXKCbjj2epEIqjJzA926rqL2pfOkNxhM6qprDWDF0K1FzkSSyaQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrieefgddtfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurheptggguffhjgffgf fkfhfvofesthhqmhdthhdtjeenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcu oehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepihgvthhfrdhorhhgpdhmnh hothdrnhgvthenucfkphepkedrudekrddvudejrddvtddvnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:50BKXIz4Li73Or6brOMtSRkjdkrzG0o_Sd4v3yNufVsoe4QsALO_Pg> <xmx:50BKXImICCgKvlD5ashinPJWQv5ArhP63vxR1cy-LAnKZ43p1AqyaA> <xmx:50BKXNFBmHEcs6Gk4I3ROTGeBGjG8K7645MekWDn1A95rVP0Zm0Ujw> <xmx:6EBKXNqGyapG8G-6TKd7dPRXFxQuyh2FGPSlMHqiZ5Z8GnnHzX4teg>
Received: from [10.100.20.187] (unknown [8.18.217.202]) by mail.messagingengine.com (Postfix) with ESMTPA id AB493100BA; Thu, 24 Jan 2019 17:49:10 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <741572B2-8826-41F4-B15D-E538141771BF@lookingglasscyber.com>
Date: Thu, 24 Jan 2019 14:49:06 -0800
Cc: Anders Rundgren <anders.rundgren.net@gmail.com>, Bret Jordan <jordan.ietf@gmail.com>, "json-canon@ietf.org" <json-canon@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <80F418FE-277C-4B02-894D-95D3A23437DD@mnot.net>
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com> <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net> <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com> <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net> <741572B2-8826-41F4-B15D-E538141771BF@lookingglasscyber.com>
To: Allan Thomson <athomson@lookingglasscyber.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/YYYphuvV5JdLBLUUXO8aIAh65Ck>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 22:49:17 -0000

I wasn't suggesting that every possible data type be in the charter; it =
just seems good to set expectations about whether they're allowed at =
*all* (and if they are, perhaps some sort of general parameters for =
what's in-scope).


> On 24 Jan 2019, at 2:46 pm, Allan Thomson =
<athomson@lookingglasscyber.com> wrote:
>=20
> Currently, many *do* define base64 binary as strings in JSON and this =
effort would be more useful to them if it included them.
>=20
> I'm not sure why we would want to be so prescriptive or restrictive on =
every last data type. It seems like if a reasonable use case requires a =
data type being included then having to redo the charter just to include =
it seems cumbersome.
>=20
> Allan
>=20
> =EF=BB=BFOn 1/24/19, 2:42 PM, "json-canon on behalf of Mark =
Nottingham" <json-canon-bounces@ietf.org on behalf of mnot@mnot.net> =
wrote:
>=20
>    I'm primarily concerned that people will want to invite new =
subtypes, e.g. "base64'd binary in a string." A good charter would make =
that clearly in or out of scope.
>=20
>    Cheers,
>=20
>=20
>> On 24 Jan 2019, at 2:40 pm, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>>=20
>> On 2019-01-24 23:14, Mark Nottingham wrote:
>>> I saw that, but it wasn't clear whether that was a starting point, =
or a limit.
>>=20
>> It is the current proposal/definition.  It limits the JSON Number =
type to IEEE-754 double precision (=3Dstrict I-JSON).
>>=20
>> =
https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-03=
#section-3.2.2.3
>>=20
>> Do you think this should be in the charter?
>>=20
>> thanx,
>> Anders
>>=20
>>> Cheers,
>>>> On 24 Jan 2019, at 2:06 pm, Anders Rundgren =
<anders.rundgren.net@gmail.com> wrote:
>>>>=20
>>>> On 2019-01-24 22:55, Mark Nottingham wrote:
>>>>> Will the Working Group limit itself to canonicalising the data =
model that's described by JSON's native data types (object, array, =
number, string, boolean, null), or will it attempt to canonicalise =
subtypes -- for example, inside strings (whether they be key or value)?
>>>>=20
>>>> It is possible that I misunderstand your question but the charter =
talks about using
>>>>=20
>>>> "...the serialization methods for JSON primitives defined by =
EcmaScript version 6"
>>>>=20
>>>> which means that strings and numbers are normalized (null and =
boolean already have a fixed form).
>>>>=20
>>>> Is this the explanation you miss?
>>>>=20
>>>> thanx,
>>>> Anders
>>>>=20
>>>>> I'd be much more comfortable if this were addressed explicitly in =
the charter.
>>>>> Cheers,
>>>>>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> =
wrote:
>>>>>>=20
>>>>>> All,
>>>>>>=20
>>>>>> Here is a proposed charter for this WG.  Please send any comments =
on this charter to this email list.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> ### BEGIN
>>>>>>=20
>>>>>> JavaScript Object Notation (JSON) is a text format for the =
serialization of structured data described in RFC 8259. The JSON format =
is often used for serializing and transmitting structured data over a =
network connection. With the increased usage of JSON in protocols in the =
IETF and elsewhere, there is now a need to define a canonical =
representation of JSON objects to enable comparison operations and =
security services on plain text JSON.
>>>>>>=20
>>>>>> Different proposals for providing such security services have =
already been defined and implemented. The goal of the Working Group is =
to define and standardize a mechanism for creating a canonical =
representation of plain text JSON objects.
>>>>>>=20
>>>>>> This group is chartered to work on the following deliverable:
>>>>>>=20
>>>>>> - A Standards Track document specifying a canonical =
representation of JSON data.
>>>>>>=20
>>>>>> In order to promote interoperability and ease of implementation, =
the current proposal builds on I-JSON (RFC 7493), the serialization =
methods for JSON primitives defined by EcmaScript version 6, and a =
platform-independent method for sorting object properties.  By doing =
that, JSON parsers will not need modifications, enabling the described =
mechanism to ultimately be reduced to an option in JSON serializers.
>>>>>>=20
>>>>>> The proposed work-item is tentatively named JSON Canonicalization =
Scheme (JCS)
>>>>>>=20
>>>>>> ### END
>>>>>>=20
>>>>>>=20
>>>>>>=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
>>>>>> json-canon mailing list
>>>>>> json-canon@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>>> --
>>>>> Mark Nottingham   https://www.mnot.net/
>>>>=20
>>> --
>>> Mark Nottingham   https://www.mnot.net/
>>=20
>=20
>    --
>    Mark Nottingham   https://www.mnot.net/
>=20
>    --=20
>    json-canon mailing list
>    json-canon@ietf.org
>    https://www.ietf.org/mailman/listinfo/json-canon
>=20
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Thu Jan 24 14:53:28 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 ED4E51311EA for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:53:26 -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 ADcAPIWiqZ6V for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:53:24 -0800 (PST)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 3AFAE130EE1 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:53:24 -0800 (PST)
Received: by mail-wm1-x32d.google.com with SMTP id b11so4946966wmj.1 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:53:24 -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=SDuoxQGeBgAmiN7FgxBV3SWjidlQzXKZDjhktQdzfIY=; b=NRVP2ah9G1ToZwGM5I42a89EdioKrl07kEhL2cyKH34nR92LT64oG6SrApvBAkKWgg IBw4iqm+RfW5W0s+1Xkh/Q++wluW1KLacAALl63O7/alLdAipBoPiEFOKShPHg1fab0R P1Bx86LDnERlk4J6uK3ioo8Vh2KANzId4adYpk9gHMRdapiSyFqOXa4VszArcX0emQgb suuJ6FtLzWHxxy17NOiZoFmZK+Km9P0FxUdleh9NnF05XbuGVHqBWNOm6GOnnEJiYI8v pN2ZKR07l9KZ8SFzsVmGGhWKzzeCb/Xzad+uv7LVGeU5OQaKISI8C+4uhovRu8ACie/C ymsA==
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=SDuoxQGeBgAmiN7FgxBV3SWjidlQzXKZDjhktQdzfIY=; b=i5NhrfxYIhjzJe0xFrOCvkbBa9QG+pzIhC00cTY5l+DgzQOZd/17032d4i2WCsq42v qdaFYKgnn0UMjSNVNY/QOA4abcdNwWmYaxAWLv6e8xQlguafrOZHFIqioXx/P+zX43ZN s9QYpK0mO3P2RB28yvN+H9K25vexp0VCle+QSZYj/ZHnZhcNu9j2KGOOS57QFrCj7Mrb fjuMsQedxZWjZkGAblMSQwe4bJpD4tIhrgsoKhME5zkSJBzkU7ZpiN23UkqRnQd4MJLk AnLvgtiAj1cCX7TBoPTTRGAomIeos/YRxbRSzixOv0fEN7D1qk3A/fRkpyPMJmgOoFlV xsyw==
X-Gm-Message-State: AJcUukdRCq1mg3aA1agnM3rA1rfrVI004QdKFCR5mIYoEUToRtbBI1HZ fgjMRQ9DO6POhJaVLyUhPIP2skTK
X-Google-Smtp-Source: ALg8bN4Ki9b3V/8nRneIw1vRHHiJopmKjGa1eaLkT/QsiabhIkiE2GST39S654/54bcbSIF0EH41OA==
X-Received: by 2002:a1c:f71a:: with SMTP id v26mr4210448wmh.131.1548370402165;  Thu, 24 Jan 2019 14:53:22 -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 a62sm52870359wmf.47.2019.01.24.14.53.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 14:53:21 -0800 (PST)
To: Mark Nottingham <mnot@mnot.net>
Cc: Bret Jordan <jordan.ietf@gmail.com>, json-canon@ietf.org
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com> <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net> <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com> <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <065785a0-30a2-d92b-9470-4d161009de0d@gmail.com>
Date: Thu, 24 Jan 2019 23:53:15 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net>
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/oDHBJq1EHUcg9SjFq1eK-5Yqnxc>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 22:53:27 -0000

On 2019-01-24 23:42, Mark Nottingham wrote:
> I'm primarily concerned that people will want to invite new subtypes, e.g. "base64'd binary in a string." A good charter would make that clearly in or out of scope.

Aah, is that what you meant!  Well, interpretation of data in strings is for sure out of scope.  We'll find some way to express this.  Thanx.

As Allan Thomson just mentioned, people indeed encode a lot of things inside of strings and this works just fine, the canonicalizer only see a string.

thanx,
Anders



> 
> Cheers,
> 
> 
>> On 24 Jan 2019, at 2:40 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>
>> On 2019-01-24 23:14, Mark Nottingham wrote:
>>> I saw that, but it wasn't clear whether that was a starting point, or a limit.
>>
>> It is the current proposal/definition.  It limits the JSON Number type to IEEE-754 double precision (=strict I-JSON).
>>
>> https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-03#section-3.2.2.3
>>
>> Do you think this should be in the charter?
>>
>> thanx,
>> Anders
>>
>>> Cheers,
>>>> On 24 Jan 2019, at 2:06 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>>>
>>>> On 2019-01-24 22:55, Mark Nottingham wrote:
>>>>> Will the Working Group limit itself to canonicalising the data model that's described by JSON's native data types (object, array, number, string, boolean, null), or will it attempt to canonicalise subtypes -- for example, inside strings (whether they be key or value)?
>>>>
>>>> It is possible that I misunderstand your question but the charter talks about using
>>>>
>>>> "...the serialization methods for JSON primitives defined by EcmaScript version 6"
>>>>
>>>> which means that strings and numbers are normalized (null and boolean already have a fixed form).
>>>>
>>>> Is this the explanation you miss?
>>>>
>>>> thanx,
>>>> Anders
>>>>
>>>>> I'd be much more comfortable if this were addressed explicitly in the charter.
>>>>> Cheers,
>>>>>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> wrote:
>>>>>>
>>>>>> All,
>>>>>>
>>>>>> Here is a proposed charter for this WG.  Please send any comments on this charter to this email list.
>>>>>>
>>>>>>
>>>>>>
>>>>>> ### BEGIN
>>>>>>
>>>>>> JavaScript Object Notation (JSON) is a text format for the serialization of structured data described in RFC 8259. The JSON format is often used for serializing and transmitting structured data over a network connection. With the increased usage of JSON in protocols in the IETF and elsewhere, there is now a need to define a canonical representation of JSON objects to enable comparison operations and security services on plain text JSON.
>>>>>>
>>>>>> Different proposals for providing such security services have already been defined and implemented. The goal of the Working Group is to define and standardize a mechanism for creating a canonical representation of plain text JSON objects.
>>>>>>
>>>>>> This group is chartered to work on the following deliverable:
>>>>>>
>>>>>> - A Standards Track document specifying a canonical representation of JSON data.
>>>>>>
>>>>>> In order to promote interoperability and ease of implementation, the current proposal builds on I-JSON (RFC 7493), the serialization methods for JSON primitives defined by EcmaScript version 6, and a platform-independent method for sorting object properties.  By doing that, JSON parsers will not need modifications, enabling the described mechanism to ultimately be reduced to an option in JSON serializers.
>>>>>>
>>>>>> The proposed work-item is tentatively named JSON Canonicalization Scheme (JCS)
>>>>>>
>>>>>> ### END
>>>>>>
>>>>>>
>>>>>>
>>>>>> 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."
>>>>>>
>>>>>> -- 
>>>>>> json-canon mailing list
>>>>>> json-canon@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>>> --
>>>>> Mark Nottingham   https://www.mnot.net/
>>>>
>>> --
>>> Mark Nottingham   https://www.mnot.net/
>>
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 


From nobody Thu Jan 24 15:15:19 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 EB28B1311EA for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 15:15:17 -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 iXo1Ki2-1MpV for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 15:15:16 -0800 (PST)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 A265813108C for <json-canon@ietf.org>; Thu, 24 Jan 2019 15:15:15 -0800 (PST)
Received: by mail-wm1-x332.google.com with SMTP id m22so4886156wml.3 for <json-canon@ietf.org>; Thu, 24 Jan 2019 15:15:15 -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=GlbFc1Mdm4fO4qSKyK00MzKsRpQBDktOGpBo2SdOLiY=; b=I+GnNhujUhAphHgzltY1cMdyVYYdLL4GGIcKp9v+/2YLyoxhz6DBiinwiQqJI3qbkx x3ek9U1GWo3UlCzSU+PecHAvP8oIekD5fiqH7k/Qkm2WV2P3577VJGdRgIKix9pHFDxP 0Uc4TJgK7+ZYFXa6peaPY5MXib260vZhr7ViQuRc/Fvas8VurS6Ozq3gE+De82z0xzH7 XFl8WxaEM1IMTjLfVK64j6/xbS5PEhh1Q9XqstaUttSmPuM/d69rgT0c8/G5fhfgCRBz R7Z7VwJeRAKmAcBjR84Osn+QfdaoWhvvOspMNOxQ75NxRG9YdKKR8sZ8WR1nco+lpRFR oueQ==
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=GlbFc1Mdm4fO4qSKyK00MzKsRpQBDktOGpBo2SdOLiY=; b=GNVdJBfSDuKpivyF/M0oaiTSi52EJOj1aFvAA4frwo0S1NPDxD2Tr4otKQ1z2mJ5kz Q4xTMEjOFSgaRHbkDKILWuAbazEiQqWehD4M0aNfTFs7KbuPLbZ28wRv6Hw+37PFSOQo lGLFie+gmwRCKmBuL2DwSlQTKuwgtJgxo7qzC9rHnG+V1lkkK8NYlS5cORSzCy3WSzlu cHKOhLDvDxYrbPlTFre1wCp9I9owMf+os1vICR5/ciI0QJDwXuAmhD3cvX2X6BwJKF+X BCJErkfv8SRS/vOmC7cWsS3bVhBnzuf/aqahLpoxyGLnCgyqzGy0TiWKwXKx9NifK+RI /d1g==
X-Gm-Message-State: AJcUukfxk8A5uY9U0pBgyEDDVNwulNDK9HsI+nKqGrzaGXoPtbhrpcwF 5ecQmAA/Qa/8L+bhXu2Jwu2GHpzG
X-Google-Smtp-Source: ALg8bN5iZWu4JcOPMQR+OH1QTY6HI8RDYWJsBDCjjIPWsZlZzFI7Oe2s4eNNBx0e5W66WkWE+9T+vA==
X-Received: by 2002:a1c:8851:: with SMTP id k78mr4568256wmd.51.1548371713513;  Thu, 24 Jan 2019 15:15:13 -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 s66sm54225428wmf.34.2019.01.24.15.15.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 15:15:12 -0800 (PST)
To: Mark Nottingham <mnot@mnot.net>, Allan Thomson <athomson@lookingglasscyber.com>
Cc: Bret Jordan <jordan.ietf@gmail.com>, "json-canon@ietf.org" <json-canon@ietf.org>
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com> <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net> <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com> <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net> <741572B2-8826-41F4-B15D-E538141771BF@lookingglasscyber.com> <80F418FE-277C-4B02-894D-95D3A23437DD@mnot.net>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <36bcf4eb-f22f-e549-33dd-3fc39be65504@gmail.com>
Date: Fri, 25 Jan 2019 00:15:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <80F418FE-277C-4B02-894D-95D3A23437DD@mnot.net>
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/sKIWBD1_FovNvLTYlBghCg9fv_4>
Subject: Re: [Json-canon] Proposed Charter
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, 24 Jan 2019 23:15:18 -0000

On 2019-01-24 23:49, Mark Nottingham wrote:
> I wasn't suggesting that every possible data type be in the charter; it just seems good to set expectations about whether they're allowed at *all* (and if they are, perhaps some sort of general parameters for what's in-scope).

For the primary application of this spec, "hashable JSON", there is no need to bother about anything but the core primitives.

For sub-type strings like a hypothetical BigNumber, a comparison between "3e+500" and "3.0e+500" wont work as expected.

Thanx, this will obviously be needed in the charter as well as in an updated draft!

Anders

> 
> 
>> On 24 Jan 2019, at 2:46 pm, Allan Thomson <athomson@lookingglasscyber.com> wrote:
>>
>> Currently, many *do* define base64 binary as strings in JSON and this effort would be more useful to them if it included them.
>>
>> I'm not sure why we would want to be so prescriptive or restrictive on every last data type. It seems like if a reasonable use case requires a data type being included then having to redo the charter just to include it seems cumbersome.
>>
>> Allan
>>
>> ﻿On 1/24/19, 2:42 PM, "json-canon on behalf of Mark Nottingham" <json-canon-bounces@ietf.org on behalf of mnot@mnot.net> wrote:
>>
>>     I'm primarily concerned that people will want to invite new subtypes, e.g. "base64'd binary in a string." A good charter would make that clearly in or out of scope.
>>
>>     Cheers,
>>
>>
>>> On 24 Jan 2019, at 2:40 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>>
>>> On 2019-01-24 23:14, Mark Nottingham wrote:
>>>> I saw that, but it wasn't clear whether that was a starting point, or a limit.
>>>
>>> It is the current proposal/definition.  It limits the JSON Number type to IEEE-754 double precision (=strict I-JSON).
>>>
>>> https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-03#section-3.2.2.3
>>>
>>> Do you think this should be in the charter?
>>>
>>> thanx,
>>> Anders
>>>
>>>> Cheers,
>>>>> On 24 Jan 2019, at 2:06 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>>>>
>>>>> On 2019-01-24 22:55, Mark Nottingham wrote:
>>>>>> Will the Working Group limit itself to canonicalising the data model that's described by JSON's native data types (object, array, number, string, boolean, null), or will it attempt to canonicalise subtypes -- for example, inside strings (whether they be key or value)?
>>>>>
>>>>> It is possible that I misunderstand your question but the charter talks about using
>>>>>
>>>>> "...the serialization methods for JSON primitives defined by EcmaScript version 6"
>>>>>
>>>>> which means that strings and numbers are normalized (null and boolean already have a fixed form).
>>>>>
>>>>> Is this the explanation you miss?
>>>>>
>>>>> thanx,
>>>>> Anders
>>>>>
>>>>>> I'd be much more comfortable if this were addressed explicitly in the charter.
>>>>>> Cheers,
>>>>>>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> wrote:
>>>>>>>
>>>>>>> All,
>>>>>>>
>>>>>>> Here is a proposed charter for this WG.  Please send any comments on this charter to this email list.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ### BEGIN
>>>>>>>
>>>>>>> JavaScript Object Notation (JSON) is a text format for the serialization of structured data described in RFC 8259. The JSON format is often used for serializing and transmitting structured data over a network connection. With the increased usage of JSON in protocols in the IETF and elsewhere, there is now a need to define a canonical representation of JSON objects to enable comparison operations and security services on plain text JSON.
>>>>>>>
>>>>>>> Different proposals for providing such security services have already been defined and implemented. The goal of the Working Group is to define and standardize a mechanism for creating a canonical representation of plain text JSON objects.
>>>>>>>
>>>>>>> This group is chartered to work on the following deliverable:
>>>>>>>
>>>>>>> - A Standards Track document specifying a canonical representation of JSON data.
>>>>>>>
>>>>>>> In order to promote interoperability and ease of implementation, the current proposal builds on I-JSON (RFC 7493), the serialization methods for JSON primitives defined by EcmaScript version 6, and a platform-independent method for sorting object properties.  By doing that, JSON parsers will not need modifications, enabling the described mechanism to ultimately be reduced to an option in JSON serializers.
>>>>>>>
>>>>>>> The proposed work-item is tentatively named JSON Canonicalization Scheme (JCS)
>>>>>>>
>>>>>>> ### END
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 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."
>>>>>>>
>>>>>>> -- 
>>>>>>> json-canon mailing list
>>>>>>> json-canon@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>>>> --
>>>>>> Mark Nottingham   https://www.mnot.net/
>>>>>
>>>> --
>>>> Mark Nottingham   https://www.mnot.net/
>>>
>>
>>     --
>>     Mark Nottingham   https://www.mnot.net/
>>
>>     --
>>     json-canon mailing list
>>     json-canon@ietf.org
>>     https://www.ietf.org/mailman/listinfo/json-canon
>>
>>
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 

