IETF Logo Mail Archive

Re: [Json-canon] [EXT] Re: Support for a WG

Allan Thomson <athomson@lookingglasscyber.com> Tue, 22 January 2019 15:19 UTC

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

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 JSON.
    
    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üße, Carsten
        
        
    
    -- 
    json-canon mailing list
    json-canon@ietf.org
    https://www.ietf.org/mailman/listinfo/json-canon

v2.23.0 | Report a Bug | By Email