Re: [dispatch] DISPATCH of JCS

worley@ariadne.com (Dale R. Worley) Wed, 20 February 2019 03:31 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C869D12E036 for <dispatch@ietfa.amsl.com>; Tue, 19 Feb 2019 19:31:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 TWR633BWuLSC for <dispatch@ietfa.amsl.com>; Tue, 19 Feb 2019 19:31:35 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 37EEF12DDA3 for <dispatch@ietf.org>; Tue, 19 Feb 2019 19:31:34 -0800 (PST)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id wITWglsizdcv3wIbcgeNV7; Wed, 20 Feb 2019 03:31:32 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1550633492; bh=033B78DRb88wWHF2SIBd3+eNrs0woJ9q/Q8EEnNo+sQ=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=dmWREeIK86vVvxGN81LNrRmom95GL7MeMXwLcg5AdWiB39uHRzmGBsyeH1dk1bea7 mCAeCoIlgL2rUHr8z0OOG+guOo6td+GUNuXoQSsYheE9rIqeRHiPF5zM+8lIl0QoOy WHs1PD2/4y3qFhV8YA9Vo/D3Cd7+Dw9e/nGnEMCgTsjjElDHxS9rUlioOzqohRggl/ VwRkrmDtVjFGW/aqtV8kmY7LfnoGJMDzcjcLOICVg3MwU0A7kKGQIgmnGOLO5IlbHF 27FMbae4ZLrgfrs7XUBXKqpyGszu7E7QdbE/HssTdGBmv+9+4dHLhYIkPRG+KF4mCK 2GzH5f2Xqv/NA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-18v.sys.comcast.net with ESMTPA id wIbbgQb1VppFLwIbbg339k; Wed, 20 Feb 2019 03:31:32 +0000
X-Xfinity-VMeta: sc=0;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id x1K3VUxw016647; Tue, 19 Feb 2019 22:31:30 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x1K3VTLa016640; Tue, 19 Feb 2019 22:31:29 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: mary.ietf.barnes@gmail.com, dispatch@ietf.org
In-Reply-To: <76521b9d-8216-e523-e719-006a0bc5ec5e@gmail.com> (anders.rundgren.net@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 19 Feb 2019 22:31:28 -0500
Message-ID: <87y36bjfu7.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/7E5nIQGpyL84BqloU250y1ZevwU>
Subject: Re: [dispatch] DISPATCH of JCS
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2019 03:31:38 -0000

Anders Rundgren <anders.rundgren.net@gmail.com> writes:
>     Cryptographic operations like hashing and signing requires that the
s/requires/require/
>     original data does not change during serialization or parsing.  One
>     way addressing this issue is creating a canonical form of the data.
---------^
"of" is missing here
>     The JSON Canonicalization Scheme (JCS) performs this task on data
>     provided in JSON [RFC8259] format.  JCS achieves this by building
You might want to omit "provided".
>     on the strict serialization formats for JSON primitives defined by
>     ECMAScript [ES6], constraining JSON data to the I-JSON [RFC7493]
>     subset, and through a platform independent property sorting scheme.
I think this is "platform-independent property-sorting scheme", but
you'd better check with the Editor.

Yes, that clarifies it.

Dale