IETF Logo Mail Archive

Re: [Json] Kicking Off JSONbis

Anders Rundgren <anders.rundgren.net@gmail.com> Wed, 14 October 2015 05:39 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C1401B2B8D for <json@ietfa.amsl.com>; Tue, 13 Oct 2015 22:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 CtZ6sOkPFn_0 for <json@ietfa.amsl.com>; Tue, 13 Oct 2015 22:39:53 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (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 07F741B2B8C for <json@ietf.org>; Tue, 13 Oct 2015 22:39:53 -0700 (PDT)
Received: by wicge5 with SMTP id ge5so85079307wic.0 for <json@ietf.org>; Tue, 13 Oct 2015 22:39:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=mz0FRJFTPshBuFK3PtAniGSP0vGDIhzjEoybJYu6RX4=; b=vhCSP2QjKuLAvJaoHSN/295BLpG8TS2iEO1s0uoe48ckQuA0kwWRAPLOjzXlsgr4zB gaTGFdyJnO353fj1l9SeRsUFXDipH6Q6XITDjfzbm3Zc17pD7atZA24i1ZzEz/kDKsMH mUxUzdwIqbA1X1mLFk+iCbeUmFWq0LwOxpf/qFLHOnC8EMPcQY+zrG+wpul9tcHPbuMU bSZfct5+h1XTWAy/pBbQ5niGoipw897h7iNSk+9P5nfr8I39+8dp72yQvGnPmDsNy2q5 tu7/07hdueXD/Hk0lyMe9TRcv9hFyuStc8tnLnmzMY2Yn7S55mdn+z1U0nune+4D8Coc ySXw==
X-Received: by 10.180.207.235 with SMTP id lz11mr2061292wic.1.1444801191407; Tue, 13 Oct 2015 22:39:51 -0700 (PDT)
Received: from [192.168.1.79] (148.198.130.77.rev.sfr.net. [77.130.198.148]) by smtp.googlemail.com with ESMTPSA id o3sm17693378wif.22.2015.10.13.22.39.50 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Oct 2015 22:39:50 -0700 (PDT)
To: Barry Leiba <barryleiba@computer.org>, Tim Bray <tbray@textuality.com>
References: <DB74C466-D542-42D6-95B0-690A564435A9@cisco.com> <CAC4RtVD3cKThDTr_eS-QCUhKqZkMS0y+nPS5HxCk3f1RQ7VyJQ@mail.gmail.com> <CAHBU6iv_w_O95Nq-bU1z2GOKgouuGrMbZP4Uwio25pPtFCc3UQ@mail.gmail.com> <CALaySJ+==5_mstrgHEd7bUGzSo85Er9VR_zEaJ+gh-O+zSpK=w@mail.gmail.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <561DEA9F.3070605@gmail.com>
Date: Wed, 14 Oct 2015 07:39:43 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+==5_mstrgHEd7bUGzSo85Er9VR_zEaJ+gh-O+zSpK=w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/Wwju0L63O_VPyR89MyMBluuDYLU>
Cc: "Matt Miller (mamille2)" <mamille2@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Kicking Off JSONbis
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 05:39:54 -0000

I'm obviously "somewhat" biased but how about evaluating my proposal which addresses
two entirely different topics:

- The ability to sign JSON objects in a way that mimics XML DSig but without bringing
   in a complex canonicalization scheme
- Predictive serialization which most developers are likely to appreciate

Note: There's no need defining a specific signature scheme, it is enough creating a
foundation for such work.

https://mailarchive.ietf.org/arch/msg/json/wfyXZ6mzDwQqVMUw-UT_-L1fhQU

JWS will be a hard sell to the business community who are slowly but surely converting
from XML and EDI to JSON.  They shouldn't have to develop their own JSON standards!

Cheers,
Anders Rundgren

v2.23.0 | Report a Bug | By Email