IETF Logo Mail Archive

[Json] JSON Concluded? Well, maybe not

Anders Rundgren <anders.rundgren.net@gmail.com> Sun, 31 December 2017 05:24 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D976B12702E for <json@ietfa.amsl.com>; Sat, 30 Dec 2017 21:24:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TX1cD8SbJ2N7 for <json@ietfa.amsl.com>; Sat, 30 Dec 2017 21:24:52 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 588901200B9 for <json@ietf.org>; Sat, 30 Dec 2017 21:24:52 -0800 (PST)
Received: by mail-wm0-x234.google.com with SMTP id f206so53420693wmf.5 for <json@ietf.org>; Sat, 30 Dec 2017 21:24:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=2EFVIekJAGnXop7ZiaJCXBvDZVh94lf2CnQBqHgVWjM=; b=kw8MYClQ/o+/+GlBZVR6tl/F5dqNEmb09Qaq8KP7YX2ubn0BBdUGkT2ukc7sj03hi8 P96vtpVhFzs/vsijuPIqRJESFxltMtW8dlf77y3KCBWX2pw06FJ8tvWfVZSBf3bYPqhh MlFR5rSSQ1aGfUOqv/wPe3jpAiM51jkgaoSEPTRga1bIb6QaFXwqj3Y7jVZoXknwhZKE 6di933DYQ0DsKoTZ3WmQGNoSvw3IhClFzGq6e9Bm23Fpr5aRVUNoPE8zQ2bbgusTZEl3 jCGlV3tKxY0mkwHBosthJH33CxuEay3K/16C0ozUZCsO6fdIvrKay8GKdqHk2Rf3B5b8 F9MA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=2EFVIekJAGnXop7ZiaJCXBvDZVh94lf2CnQBqHgVWjM=; b=O8VYhgLg3kZUeFcwGCm30jYlMDt4IYjudJVMR/hewCEsuFWyNyDxVTQs3tAD0du4ub po6FCEkdZkyLi1QJw2wXqr5JuJM1cZqPjH955nzQtRMbZDdWpHQrqU+qKUFZewBzKXjI Wwg8DhlKlvwaehGVyP7fxcgsOqDJwvW7OoIOZisYth+t7NDwMe3hgeAVk7J3trp/iT/P EvBtz2CK18WexeOVv5riUquUBfEnSXkTK1dEpJ8l8mEH7qxhw6wG5KOJ4Kvs4/OQkV6y a85NFBy8pq3BcPI55LPE1ZTodBVNjeCOs3gq77an4wFpKECOxA0edkMyxZP3El/yNeWl Ubmw==
X-Gm-Message-State: AKGB3mLNoue3lgCpX2uxK1cVDdkto+qS6sxhgewQOrXzyjAB6KWUGQUX WZ7CA0JIO6f0ZwqTjtFVsmXbDQ==
X-Google-Smtp-Source: ACJfBouM8hfQm+3GBF5/JCQWv0+B3u2vh1VjY30mz4GsNajRJRhHdzdVRaQrfI01l7DRFYoSbYKoSQ==
X-Received: by 10.28.144.10 with SMTP id s10mr29069726wmd.103.1514697890506; Sat, 30 Dec 2017 21:24:50 -0800 (PST)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id 139sm18247967wmp.7.2017.12.30.21.24.48 for <json@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 30 Dec 2017 21:24:48 -0800 (PST)
To: "json@ietf.org" <json@ietf.org>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <13860352-ef8e-1d4b-2eff-27e275c25e3a@gmail.com>
Date: Sun, 31 Dec 2017 06:24:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/ry3X1fNW8iEE9TmVo7V6m3gwzRI>
Subject: [Json] JSON Concluded? Well, maybe not
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 31 Dec 2017 05:24:55 -0000

Congratulations everybody to the revised JSON RFC!

Does this mean that JSON is "done" for good?

Probably not because the concept I have mentioned from time to time, the ability adding a digital signature to a JSON object (in contrast to signing arbitrary Base64Url-encoded data), is still very much alive.  In fact, there is an I-D in preparation aiming at reducing the current proliferation of "DIY-standards" for dealing with this highly requested feature.  The only real challenge is agreeing on a suitable way "normalizing" JSON data during parsing and serialization.  Such a scheme will be like an extended version of I-JSON (RFC7493), potentially having an impact on "ordinary" uses of JSON as well.

Happy New [and optionally signed] JSON Year
Anders Rundgren

v2.23.0 | Report a Bug | By Email