IETF Logo Mail Archive

Re: [Json-canon] Support for a WG

Samuel Erdtman <samuel@erdtman.se> Mon, 21 January 2019 21:18 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 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

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
>

v2.23.0 | Report a Bug | By Email