Re: [Json-canon] Proposed Charter

Mark Nottingham <mnot@mnot.net> Thu, 24 January 2019 22:42 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: json-canon@ietfa.amsl.com
Delivered-To: json-canon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB9DE1311D7 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:42:32 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=1BNrRYd+; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=E8c+rEc/
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 AF0dEAmFWBx5 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:42:30 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D331813117B for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:42:29 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D0AC022158; Thu, 24 Jan 2019 17:42:28 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 24 Jan 2019 17:42:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=4 ZTktssK+g2GPKbuoPKjhtedM6w6/Q10CvfJmXpXHLE=; b=1BNrRYd+xPXsXe2Dk o37WZQGIzYyqMGgTC0Za5MqAtJE01o26v1HOZfpFq2QyTly5vQtHVQ3iaFz0wcfn 3UNIhZYpeZby5M6WNlFarhVOI3KGQw+PARbuV9I1h6nY6PoKgbbOMJZS2lVP0Wjh 6GGX1yuUjftOIwA2A7JDoGbOuJT2ZT0MVCCyHl2MzZEOOe6MNUL+fsdvlwmsnPNd etB9sy6wTEtOqSpYTL/UcI0S2Z/bkNENI2BB8J8rbYcgkIAfGI3Iw2Xy55YyPL6g e6DilwPRMMPnhyI3lj8blJSHUwGY23DDuxInrLw8bOFgdQAxbhwb+GI7J8Bp4b14 Uss+g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=4ZTktssK+g2GPKbuoPKjhtedM6w6/Q10CvfJmXpXH LE=; b=E8c+rEc/ni8nVrtOQj+d0ek2NTsEV+inZ9xsJmwUIuB9MsWpJZCds+Ej5 Mc/l7IAEP6P5UrOIqHXi0iIds7IZW6WZpZBGsHgU/88lnGm/ebNmfH58tiQABxaQ 7q8me6YW7hbYAgO/lYSj5mNa9Z6fNvqk+zlXRC2EgEdF9BtV1aCp5RvxN8ejEiLH 6uWjkox4JMZ5dX8Q/xVOn5dQPaHlDY+7+DVGn83oKyasgJ34mqGwBEOeieSCLYGz BExt4yXsQmnbsHOpzIqCfZVIn6I3In4nkmAiOwrDA4BrNVEqV02lTSnAqyIS9A3V aLVAM3DVWQTdNSebmu/L9jyPX7LNA==
X-ME-Sender: <xms:Uz9KXPTrm4iipRTRDkiZA2YcvNEM43ammCf4fORmEJ39YqWpLZgPnA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrieefgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurheptggguffhjgffgf fkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcu oehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepihgvthhfrdhorhhgpdhmnh hothdrnhgvthenucfkphepkedrudekrddvudejrddvtddvnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:Uz9KXFZQf9IsFAyEseQn_yvv3N1dl7q-aYBGRp3z5WMgvTXpC1lIVw> <xmx:Uz9KXM8PO2FCyv3e_G0iPFCF9X5WV9bysiPYGB21HPPLBLE-XK53iQ> <xmx:Uz9KXJLDCt822QoXg8H_lK-pCXAtA9F9DG3O-ATnbotvwA8rtEvOgw> <xmx:VD9KXHkcLpdqmirPHkrvRAnboeR5dcq2ZvIkgNBe_LpZvl_ajZ0JLQ>
Received: from [10.100.20.187] (unknown [8.18.217.202]) by mail.messagingengine.com (Postfix) with ESMTPA id EC840E4394; Thu, 24 Jan 2019 17:42:26 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com>
Date: Thu, 24 Jan 2019 14:42:23 -0800
Cc: Bret Jordan <jordan.ietf@gmail.com>, json-canon@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4B4D8D8-B7D5-4963-9E0F-06BFDFB0F246@mnot.net>
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net> <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com> <D39ED435-7DA6-439E-A71F-4789974AA1D2@mnot.net> <46cd19f4-62e7-bc46-84d9-3fd647f8ede9@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/4ch8ojN5qt8xtJ3i8WmI9Jmy33M>
Subject: Re: [Json-canon] Proposed Charter
X-BeenThere: json-canon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Canonicalization <json-canon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json-canon>, <mailto:json-canon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json-canon/>
List-Post: <mailto:json-canon@ietf.org>
List-Help: <mailto:json-canon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json-canon>, <mailto:json-canon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2019 22:42:33 -0000

I'm primarily concerned that people will want to invite new subtypes, e.g. "base64'd binary in a string." A good charter would make that clearly in or out of scope.

Cheers,


> On 24 Jan 2019, at 2:40 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
> On 2019-01-24 23:14, Mark Nottingham wrote:
>> I saw that, but it wasn't clear whether that was a starting point, or a limit.
> 
> It is the current proposal/definition.  It limits the JSON Number type to IEEE-754 double precision (=strict I-JSON).
> 
> https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-03#section-3.2.2.3
> 
> Do you think this should be in the charter?
> 
> thanx,
> Anders
> 
>> Cheers,
>>> On 24 Jan 2019, at 2:06 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
>>> 
>>> On 2019-01-24 22:55, Mark Nottingham wrote:
>>>> Will the Working Group limit itself to canonicalising the data model that's described by JSON's native data types (object, array, number, string, boolean, null), or will it attempt to canonicalise subtypes -- for example, inside strings (whether they be key or value)?
>>> 
>>> It is possible that I misunderstand your question but the charter talks about using
>>> 
>>> "...the serialization methods for JSON primitives defined by EcmaScript version 6"
>>> 
>>> which means that strings and numbers are normalized (null and boolean already have a fixed form).
>>> 
>>> Is this the explanation you miss?
>>> 
>>> thanx,
>>> Anders
>>> 
>>>> I'd be much more comfortable if this were addressed explicitly in the charter.
>>>> Cheers,
>>>>> On 24 Jan 2019, at 10:56 am, Bret Jordan <jordan.ietf@gmail.com> wrote:
>>>>> 
>>>>> All,
>>>>> 
>>>>> Here is a proposed charter for this WG.  Please send any comments on this charter to this email list.
>>>>> 
>>>>> 
>>>>> 
>>>>> ### BEGIN
>>>>> 
>>>>> JavaScript Object Notation (JSON) is a text format for the serialization of structured data described in RFC 8259. The JSON format is often used for serializing and transmitting structured data over a network connection. With the increased usage of JSON in protocols in the IETF and elsewhere, there is now a need to define a canonical representation of JSON objects to enable comparison operations and security services on plain text JSON.
>>>>> 
>>>>> Different proposals for providing such security services have already been defined and implemented. The goal of the Working Group is to define and standardize a mechanism for creating a canonical representation of plain text JSON objects.
>>>>> 
>>>>> This group is chartered to work on the following deliverable:
>>>>> 
>>>>> - A Standards Track document specifying a canonical representation of JSON data.
>>>>> 
>>>>> In order to promote interoperability and ease of implementation, the current proposal builds on I-JSON (RFC 7493), the serialization methods for JSON primitives defined by EcmaScript version 6, and a platform-independent method for sorting object properties.  By doing that, JSON parsers will not need modifications, enabling the described mechanism to ultimately be reduced to an option in JSON serializers.
>>>>> 
>>>>> The proposed work-item is tentatively named JSON Canonicalization Scheme (JCS)
>>>>> 
>>>>> ### END
>>>>> 
>>>>> 
>>>>> 
>>>>> 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."
>>>>> 
>>>>> -- 
>>>>> json-canon mailing list
>>>>> json-canon@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/json-canon
>>>> --
>>>> Mark Nottingham   https://www.mnot.net/
>>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
> 

--
Mark Nottingham   https://www.mnot.net/