Re: [dispatch] JSON Canonicalization Scheme (JCS) Proposal

Brian Rosen <> Mon, 29 April 2019 19:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E715D1206B2 for <>; Mon, 29 Apr 2019 12:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, 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 Dqo3HnTYKzbl for <>; Mon, 29 Apr 2019 12:17:16 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 05E251206B3 for <>; Mon, 29 Apr 2019 12:17:16 -0700 (PDT)
Received: by with SMTP id m137so6672627qke.3 for <>; Mon, 29 Apr 2019 12:17:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Ce3UBUbDLG09UROugn2stcMEch0FB9qc+b5rFPif7JE=; b=txZytIsiQKWvCN2DOuQduLh6D4Ya/l+TURlgAJK6aY0ogAYYESVBPMSYVNt9GR3FkS 0IcB3BiA+qd/az0GAC6UHDnPiPtopYm/PR+lfECMitCZBJD/iqO8JoQs2ysp8eNZmdcO 5bE1OirTlfyCbnD8AolbFNCJeUc8VicIVS+vXMDjeF4gyNnhKJxjfHrnmC4JxhqOmmrB bU3JbDdvT3wyPauhQaUiiWs5S6NMGKqiuNcEWS9iBURg8c4nGuvBtKSyHt/vIunBBLzp xsPeSBI+wVoaDMvOzL9AT9R0BwoJPrzqZetIFIGIX4t8wII6c9FFQKNih8ywbPrdHyPl xnCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Ce3UBUbDLG09UROugn2stcMEch0FB9qc+b5rFPif7JE=; b=kheK3YErYIrFB+PVuZXyz3LNS3qrBUfZjjtrvm9NZoT3cDh92k8gYlXa86Jv5IKmNF sSYXPbfn4BSLqxXli4blSUY6QqYtyTf/FGRPB4x+MDYAl/763EWI/89Uxzuq1w7otzLl LD1k7roimUU+pzg+lWiNenSbP+gdEykmx/Hu65uC4gZZVqSGx9v9Khq/48eM3/6RN3sn n6HVFNUP7wSb6DpyQf3fmzctVeogYc02AJKZHK+HCPfllI4G/s1lNMZmqbZXWhctiAvZ fbXh4AU7P1IN8oUB5vAzyOnuSNzm+9azpYZBR6BwNFsCU0/znk5wq77PQusrvPib5GS5 aXtg==
X-Gm-Message-State: APjAAAXpXIsB5/CVEvxZMVuTe/8DIkEryzDqMGBkj63rbpwgPFcKw9B8 6WebTaRBfrdXqf0PYLiZ3gPclA==
X-Google-Smtp-Source: APXvYqx2DGvgOb0SZf1rrsGe+yb4X1OpZcZu/byuunnrkBJEQR6uWrxIEIsofA5MpJF3CH2CUy/tlA==
X-Received: by 2002:a37:c245:: with SMTP id j5mr39855325qkm.70.1556565434934; Mon, 29 Apr 2019 12:17:14 -0700 (PDT)
Received: from brians-mbp-6.lan ([]) by with ESMTPSA id g185sm14693860qkc.48.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Apr 2019 12:17:14 -0700 (PDT)
From: Brian Rosen <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A4547121-2852-4A4B-AF34-55CCBD19D519"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Mon, 29 Apr 2019 15:17:13 -0400
In-Reply-To: <>
To: Bret Jordan <>
References: <>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <>
Subject: Re: [dispatch] JSON Canonicalization Scheme (JCS) Proposal
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: Mon, 29 Apr 2019 19:17:19 -0000

I like this work and would like it to move forward.  A use case I have is the recording system for emergency calls.  Everything is recorded and the recorded data is used real time as history of an incident, rather than retaining it both in some temporary system and in the main recording system.  That means that the recording system is frequently consulted real time as the incident progresses.  Signatures are used throughout, primarily for non-repudiation.  You only validate the signature months after the event, when lawyers want to make sure transcripts are accurate.  Having to do more work to get the data is not desirable. 

I will review, comment and participate actively in this effort.


> On Apr 29, 2019, at 2:44 PM, Bret Jordan <> wrote:
> Dispatch,
> During IETF 104 there were several meetings and sessions about the proposed JCS solution. This JCS solution defines a way to canonicalize JSON data to enable hash-able JSON. After listening to and working through most of the concerns that were raised, there seems to be some significant interest and use-cases for moving this work forward.
> We respectfully request that DISPATCH look at this work and determine where it would best fit in the IETF.  We would also like to request that DISPATCH add this to the next interim or full meeting.  
> The current draft can be found here: <>
> Further, many successful implementations for several different platforms as well as a public "playground" <>jcs/home have been created to show that this not only works, but is pretty easy to implement. 
> Personally I know many organizations and solutions that desperately need this for production.   Thank you for your consideration. 
> Thanks,
> Bret
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
> "Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
> _______________________________________________
> dispatch mailing list