IETF Logo Mail Archive

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

Ben Campbell <ben@nostrum.com> Tue, 07 May 2019 21:32 UTC

Return-Path: <ben@nostrum.com>
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 ADEC712024D for <dispatch@ietfa.amsl.com>; Tue, 7 May 2019 14:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 bZvuJlFDdGcZ for <dispatch@ietfa.amsl.com>; Tue, 7 May 2019 14:32:55 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 286CD120248 for <dispatch@ietf.org>; Tue, 7 May 2019 14:32:55 -0700 (PDT)
Received: from bens-macbook.lan (cpe-66-25-20-105.tx.res.rr.com [66.25.20.105]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x47LWpDl021123 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 7 May 2019 16:32:53 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1557264773; bh=BZbGl1JGe5hqd7ifm4GZ5BXHnGGeyA5WQ3zzduPDYj4=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=jmQ1qnG9s/urvueiaivj0Qz38f33cT+TK5cks9/r3giLLnHAv3ReljthWvF2dAyew FHuk6Djxy6WRJ1YU4TarpIEmc+ojO4tS/2RIqk6pcVAexxlGM95MjDIiWShwK7iNn9 ffIHBEC5iKEsi0wcQQ0loBFfEv3c2STHywJMX4V8=
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-20-105.tx.res.rr.com [66.25.20.105] claimed to be bens-macbook.lan
From: Ben Campbell <ben@nostrum.com>
Message-Id: <2904F41A-539C-496B-ABF2-7D2618FC8116@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A09AAC2E-11F3-43F4-A576-3315E7C5E827"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Tue, 07 May 2019 16:32:45 -0500
In-Reply-To: <6445089C-CC1A-4405-85CB-A7561D9B25BA@gmail.com>
Cc: dispatch@ietf.org
To: Bret Jordan <jordan.ietf@gmail.com>
References: <6445089C-CC1A-4405-85CB-A7561D9B25BA@gmail.com>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/AKDIdj2mLorS4VPFl_FtnLT5slY>
Subject: Re: [dispatch] JSON Canonicalization Scheme (JCS) Proposal
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: Tue, 07 May 2019 21:33:03 -0000

(as DISPATCH chair)

It would be helpful to hear some more voices here. Does anyone else have opinions? Especially people involved in those side meetings?

Bret, could you offer a very high level summary of the side discussions from Prague?

Thanks!

Ben.

> On Apr 29, 2019, at 1:44 PM, Bret Jordan <jordan.ietf@gmail.com> 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: https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-05 <https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-05>
> 
> Further, many successful implementations for several different platforms as well as a public "playground" https://mobilepki.org/jws- <https://mobilepki.org/jws->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
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

v2.23.0 | Report a Bug | By Email