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

Samuel Erdtman <samuel@erdtman.se> Tue, 22 January 2019 16:37 UTC

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

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
>
> 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
>
>
> --
> json-canon mailing list
> json-canon@ietf.org
> https://www.ietf.org/mailman/listinfo/json-canon
>