Re: [Json] Normative reference reasoning and logistics

Anders Rundgren <anders.rundgren.net@gmail.com> Sun, 01 May 2016 12:36 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 39A6D12D518 for <json@ietfa.amsl.com>; Sun, 1 May 2016 05:36:56 -0700 (PDT)
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 eziLzAPthAen for <json@ietfa.amsl.com>; Sun, 1 May 2016 05:36:54 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 044181200A0 for <json@ietf.org>; Sun, 1 May 2016 05:36:53 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id a17so103762308wme.0 for <json@ietf.org>; Sun, 01 May 2016 05:36:53 -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-transfer-encoding; bh=eOSxlEpjlj+BzQxYajcI8JFtrcGuG2wwk6ZV/2WgYKE=; b=esleY/oLTlzJzOgUjlZXIULSz83CVmVGzF+ebym1DRFIqAc4+TotIYOzo/m3N5pDcN FXPEH7NW1WpVh8n2OTuzNy3OK5zUCiO8DaDPI+7eQ2yBuo5my8DJyg8fbnXOmlYzKDqj vRnCIA9XOkfhVCM2wmgi6cOsKxzhrv6Cq7Sj5vosBG55pVeiIh70oog4q1Wpa98VNA72 MB276R+ZX5mxQ+M2Bl0ZBdo8v6je7jb1bHjd4w7k/gbMg1SKE+DtHFRhEEaNHViA7wEz gKPyhBPxo3rEvc9WQyK/8Hwr06YEzALylimuXQRtMLlsncUqdu3lgVQvDZi8J84n1fJY a4nw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=eOSxlEpjlj+BzQxYajcI8JFtrcGuG2wwk6ZV/2WgYKE=; b=DO1gGKYLUsvxZSYcBC63WTU3IYmVa6pEngSNqyc+y9HoLcxxaVZq5+Ju4Te6x/wNOy dC2GAgPAS6a2FCWgenK3Jm4zxnlH9tcnqCwBQFzIj7n9u/srPsuRY7jxe87bcB9Mmtzl V0SR9XUKM1lxqM6sz0EakBJfp82jcmLoJnkuIFCdVnqY9Y1nnKattv5Au4VDtjjEV/cz TOmu3WzDiwAa/6wPUm+PxC9cpsI19T8qP7PQI4GfMQAzAZ6IYFNlDwOCpxg3yyHvSJhK tQ8sEPgW8LBZedrzlrIZWyz+cehyj0kCpXqDP5Kqy7Ld4fBzmDGAIL9rQsSMj3MbXUG4 wAJg==
X-Gm-Message-State: AOPr4FW9rKfpMGhHNEEQ1dw6F1Fe7kpj94m+/TZSqzagcMa4kIOvyZ2/hbidBK+DLIXskw==
X-Received: by 10.194.184.38 with SMTP id er6mr30286312wjc.93.1462106212483; Sun, 01 May 2016 05:36:52 -0700 (PDT)
Received: from [192.168.1.79] (124.25.176.95.rev.sfr.net. [95.176.25.124]) by smtp.googlemail.com with ESMTPSA id d79sm13143889wmi.23.2016.05.01.05.36.51 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 01 May 2016 05:36:51 -0700 (PDT)
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Stefan Hagen <stefan@dilettant.eu>, "json@ietf.org" <json@ietf.org>
References: <CAHBU6iu0j492Mzbo2HriFtjm_o5516yCsQCX9PGHvqAxhU0Zjg@mail.gmail.com> <CAHBU6isb+A4crvdEMkMqhreXLcox3Q5O-TJeOYvb4vvUqYupmg@mail.gmail.com> <978CE59C-19EA-44E0-8AA9-620B854ACB6F@cisco.com> <5725C566.9040606@dilettant.eu> <31996bff-e42e-8ae8-2052-06bfc9386190@gmail.com> <0ee4fb33-9f59-8885-7ce3-0577e7029770@it.aoyama.ac.jp>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <397a238d-4d50-a852-6e96-ccb7aa08148d@gmail.com>
Date: Sun, 01 May 2016 14:36:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <0ee4fb33-9f59-8885-7ce3-0577e7029770@it.aoyama.ac.jp>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/dbWqjn940NEuW9TYIMgjwex2BMY>
Cc: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Subject: Re: [Json] Normative reference reasoning and logistics
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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, 01 May 2016 12:36:56 -0000

On 2016-05-01 14:22, Martin J. Dürst wrote:
> On 2016/05/01 21:14, Anders Rundgren wrote:
>> IMO, ES6's JSON serialization scheme will likely be way more significant
>> than ECMA-404
>> (which I believe very few application developers have bothered looking
>> into).
>
> Hello Anders,

Hello Martin,

First off I don't see the point with having multiple organizations specifying
the JSON core format.  AFAIK, JSON started its life as RFC4627 which later was
upgraded by RFC7159.  That is, ECMA-404 can safely be ignored.

My reference to ES6 is not related to the JSON format, but how JSON parsers
and serializers could (IMO SHOULD) be implemented in order to offer maximum
interoperability as well as supporting digital signatures in a human-friendly way:
https://cyberphone.github.io/openkeystore/resources/docs/jsonsignatures.html

Anders

>
> Can you provide some background? Is "ES6's JSON serialization scheme" a
> separate format, with changes from ECMA-404?
>
> Or are you just saying that the IETF better point to "ES6's JSON
> serialization scheme" than ECMA-404? I guess we should do that if that's
> what ECMA wants, but your "will likely be" doesn't really sound very
> definitive yet.
>
> Regards,   Martin.
>