IETF Logo Mail Archive

Re: [Json-canon] Proposed Charter

Anders Rundgren <anders.rundgren.net@gmail.com> Thu, 24 January 2019 22:06 UTC

Return-Path: <anders.rundgren.net@gmail.com>
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 745CF130EE1 for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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=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 rEA2-tWltjks for <json-canon@ietfa.amsl.com>; Thu, 24 Jan 2019 14:06:28 -0800 (PST)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 C85A9128AFB for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:06:27 -0800 (PST)
Received: by mail-wr1-x42b.google.com with SMTP id u4so8205118wrp.3 for <json-canon@ietf.org>; Thu, 24 Jan 2019 14:06:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=n5wTszjkms6Cd1DkQXjMLTFn6bLIeU8cprbdfSnvWN0=; b=CFbwBOUzlOCSVrlfsuzVXwbyClaEIdDTzDxsghbKoZb0qFD/y1MzJJgmoTfwdAvTx7 nABN4xeqjubmkE8ojTtQ2TxWacz+nO8d0tdZEYBmeBSDbb/wI2dXQ8cPTzc2RX/a0ogH fX6KGW6GP6QdQVYFvz19Q2L6YSOo/ycTS3aYDMyzaMeJuCHAqFMgleMu21JkyzI8OSZP RVfw+v+h9FfzBtvikPxdWaYz/nkf4xyfSEC/iaKLqE6fkMoFRPmvgt1HNtmaUDvIXPQh 4cQ5pJsKwwNwTVjWDjAXPiG+AVIXpk213cqpgPU/+cDtkbglcq75f7LO87EdGEiJS/bD dz8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=n5wTszjkms6Cd1DkQXjMLTFn6bLIeU8cprbdfSnvWN0=; b=DXu0bl5f8MhVCNbd67JcQ7vXO41ojHGuAzriiCi9kM9JtNmsmwoLEk50LSFa++hHak thuxNLZxtvK+7+NYfIFWEcGoyoHodUp0oEfQwhlhqWUNhd9ohX1Yl3ivdi+T1U8VVBHP JcbdzOcMDEidlMrU8KLPzO1hgpJe00o2obwB27DqXIV3M2DRhtEBtJN/ISkbDRM/DDxT TSut+HXL2yziYtQx432H3S5trLv9krsT4GGO50bJPNFT4uEsXHSZ6RNSA4+ZrSCCt/B3 D4qD7mIDA8u3SB0bO4F+nddj+FbtxbHOMQQp4AO71YQ+Xo8TDpBxCUXh8bBU85ZD2Qbd GDyQ==
X-Gm-Message-State: AJcUukdMbZatIVe86LgqD+xQtlCw7uL+UUz6Ymf9+WzdKJJoqIQPxlyO 5wWodMdZLab/mz6r/AQEeli8LY9F
X-Google-Smtp-Source: ALg8bN5KJ4T0JHNzljSrmKqmLxjtfxmvreTm9Qw5uiuV1oek0gU7KzWrY6np2/aODPaMw6bt6flCYQ==
X-Received: by 2002:a5d:6aca:: with SMTP id u10mr8600320wrw.310.1548367585838; Thu, 24 Jan 2019 14:06:25 -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 k23sm39248836wmj.32.2019.01.24.14.06.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Jan 2019 14:06:24 -0800 (PST)
To: Mark Nottingham <mnot@mnot.net>, Bret Jordan <jordan.ietf@gmail.com>
Cc: json-canon@ietf.org
References: <069AE75F-45F0-4C46-8AB6-8B734073261B@gmail.com> <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <347d7716-570f-169b-1ea9-62cc83d346f0@gmail.com>
Date: Thu, 24 Jan 2019 23:06:19 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <797CD514-E3CE-40C2-9360-21B31372D9AE@mnot.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json-canon/H6y_zeyXdEPlOM2cyaCLPXNscPA>
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:06:30 -0000

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/
>

v2.23.0 | Report a Bug | By Email