Re: [Json] JSL: Clarifying purpose, and renaming it to JDDF

Carsten Bormann <cabo@tzi.org> Thu, 29 August 2019 08:44 UTC

Return-Path: <cabo@tzi.org>
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 EB927120103 for <json@ietfa.amsl.com>; Thu, 29 Aug 2019 01:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 X4M4viOPPd71 for <json@ietfa.amsl.com>; Thu, 29 Aug 2019 01:44:01 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EDE01200D8 for <json@ietf.org>; Thu, 29 Aug 2019 01:44:01 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46Jx3g4w6KzyXf; Thu, 29 Aug 2019 10:43:59 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4644E5BE-096F-44BA-84DF-1EE74761ED9D@tzi.org>
Date: Thu, 29 Aug 2019 10:43:58 +0200
Cc: JSON WG <json@ietf.org>, Ulysse Carion <ulysse@segment.com>
X-Mao-Original-Outgoing-Id: 588761034.7030621-e6a7bca2a615aea122fae8488cacc927
Content-Transfer-Encoding: quoted-printable
Message-Id: <43B2E14E-5FF2-4E29-9EB9-DCA805C89B67@tzi.org>
References: <CAJK=1Rj6zW_MffKvsOiQh28KY5yDeoALGSYqve+vGj52s1Owag@mail.gmail.com> <SY2PR01MB2764EDAB3DD01417A95A26D5E5A20@SY2PR01MB2764.ausprd01.prod.outlook.com> <4644E5BE-096F-44BA-84DF-1EE74761ED9D@tzi.org>
To: "Manger, James" <James.H.Manger@team.telstra.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/ncneR5E6mIzAYhC2Tg83dKN8Qo8>
Subject: Re: [Json] JSL: Clarifying purpose, and renaming it to JDDF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 29 Aug 2019 08:44:03 -0000

On Aug 29, 2019, at 10:33, Carsten Bormann <cabo@tzi.org> wrote:
> 
> representation

… and adding something closer to a proposal to my observation:

intString is an int[unlimited?  64?] in decimal.
(Note that the below are all strings on the JSON side, too; nothing is special requiring calling out the use of Strings, but it should be said that they are decimal(*)).

uintB64u is an uint_unlimited in (msb-first bytes and then) b64u (Section 5/no padding).

bytesB64 is a byte string in b64c (Section 4/padding).
bytesB64u is a byte string in b64u.

Note that there is no “default” representation of byte string in JSON, so this always needs a representation (possibly the JDDF defines a default, which would be b64u).

Grüße, Carsten

(*) should have a position on leading zeros…