Re: [dispatch] DISPATCH of JCS

Anders Rundgren <> Tue, 19 February 2019 04:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EFD1B130E6C for <>; Mon, 18 Feb 2019 20:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ijPF9rgEKN5R for <>; Mon, 18 Feb 2019 20:26:52 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::444]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C6246130E67 for <>; Mon, 18 Feb 2019 20:26:51 -0800 (PST)
Received: by with SMTP id c8so20617688wrs.4 for <>; Mon, 18 Feb 2019 20:26:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=x+ixEZN9yx9FtUC60in0niTH9jUBaGu2V9/m0elGVSI=; b=jdW0cAvVBoaJDu/JAHWO+XEsFsmFWOatQNKSEbWiw9i/C4kf2ew8DvDSnmvvKVhYn4 3xUf03W+SXpqt6+IMy7ncuEskK2z1mlrKYp80mysYLF851gDg5R04EBOXSto1uQr/rgp /3YFizecnW1XBYawAdsi01uLOjEfIfd/mPsVUXAjwUn959WOqGP8B28lbzp5i1AyuDsH Ps5oRLjwhlPcB2NtDj79kTyx6OiIO0SFdyLGaj8rVWtKMqjXXeNS141ewbDwloieazsj vlYOEHDNuDINw9Q0JYC/2lD2sOM2XCMqDs5tSf0LoAxiwW6h7R4ZJBsqsDSoAjkkYhYq HIqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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=x+ixEZN9yx9FtUC60in0niTH9jUBaGu2V9/m0elGVSI=; b=cDAVF4m0bqZKckfJewrLsBqAd8a95cx+vCRMJbd/y9f2W8anNj6IiIR12lMM/gYpru 9ZES24e2zfAlEyqx8kfnu7ZE2ApkxITLB4RyLkSWh4yJdHi/hm6igmzrs+TyIn6cILAP hF8mlDR8WjQCXn/4FXdP4/KMclSdRC0kGLDJuEJ1qtKc3BoBxEIVv4ycoATYk+d+TQKH yQiStzRRdlAXnT0Vn9oPGD+EGBZ7MbKQTO30NfjIUE1OUyz0RcLHDy4PgIq24yR+XT65 KfYAiporVWrtnJQhbnT4LugzVvEBc5WX2PAgkzl3Rhv6f5OAhKVr6cv2OE0U39JfHqTN uSxA==
X-Gm-Message-State: AHQUAuYjNwsyNNe98UpdtZUFyuoMRZ0RmVG41gSsQvSJB9jmIUq9QEB/ Ch9UB3kKf3xbyo0FLxALPye2VtXL
X-Google-Smtp-Source: AHgI3IbOpXuh/hteyEUFPQg7z6bdiZ4yNGyzaYywqmJWn1KhQs//83FEy/da7PQtosBz5/MNXPR/iw==
X-Received: by 2002:adf:ea88:: with SMTP id s8mr10298655wrm.127.1550550409686; Mon, 18 Feb 2019 20:26:49 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id s3sm13950530wrt.81.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Feb 2019 20:26:48 -0800 (PST)
To: "Dale R. Worley" <>
References: <>
From: Anders Rundgren <>
Message-ID: <>
Date: Tue, 19 Feb 2019 05:26:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [dispatch] DISPATCH of JCS
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 19 Feb 2019 04:26:54 -0000

On 2019-02-18 23:16, Dale R. Worley wrote:
> Anders Rundgren <> writes:
>> Recently updated I-D:
> The value of having a JSON canonicalization is clear to me.  But I note
> that the abstract doesn't seem to actually *say* that the document
> defines a JSON canonicalization, but leaves the reader to infer from the
> name, "JSON Canonicalization Scheme", what JCS does...
> Dale

    Cryptographic operations like hashing and signing requires that the
    original data does not change during serialization or parsing.  One
    way addressing this issue is creating a canonical form of the data.
    The JSON Canonicalization Scheme (JCS) performs this task on data
    provided in JSON [RFC8259] format.  JCS achieves this by building
    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.