Re: [Cbor] πŸ”” WGLC on draft-ietf-cbor-array-tags-03

Jim Schaad <ietf@augustcellars.com> Fri, 15 March 2019 01:49 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A31130EED; Thu, 14 Mar 2019 18:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 WXRs4wpWDeiz; Thu, 14 Mar 2019 18:49:06 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3E6F1311F8; Thu, 14 Mar 2019 18:49:05 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 14 Mar 2019 18:49:00 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Jeffrey Yasskin' <jyasskin@chromium.org>, 'Laurence Lundblade' <lgl@island-resort.com>
CC: <cbor@ietf.org>, <draft-ietf-cbor-array-tags@ietf.org>, 'Francesca Palombini' <francesca.palombini@ericsson.com>
References: <426CD514-B174-4CE7-B467-2727C6B5B354@ericsson.com> <6F7C83DD-E98C-44EF-A315-194E31759518@island-resort.com> <72F7B17A-2684-4591-8D70-01DE32BFA03B@island-resort.com> <CANh-dX=Yao9pYfd-ubrsUsMYH6boqEKzaeZpYe09sz1tDovPxg@mail.gmail.com>
In-Reply-To: <CANh-dX=Yao9pYfd-ubrsUsMYH6boqEKzaeZpYe09sz1tDovPxg@mail.gmail.com>
Date: Thu, 14 Mar 2019 18:48:56 -0700
Message-ID: <00eb01d4dad1$42493120$c6db9360$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00EC_01D4DA96.95EC06D0"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQJDckXT1PNyaRbuIeGp9sN/08XZzALTp86QAZld6+8Cj9y01qT21eGw
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/AfLgY70X9RtctECqEWcLRK4u-Pc>
Subject: Re: [Cbor] =?utf-8?q?=F0=9F=94=94_WGLC_on_draft-ietf-cbor-array-tags?= =?utf-8?q?-03?=
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2019 01:49:14 -0000

I would say that this is analogous to the question of how date and time are encoded.  There are several different options and we don’t say which of them is deterministic for encoding.  We just say how to encode it once the value and tag are selected.

 

Jim

 

 

From: CBOR <cbor-bounces@ietf.org> On Behalf Of Jeffrey Yasskin
Sent: Wednesday, March 13, 2019 11:29 AM
To: Laurence Lundblade <lgl@island-resort.com>
Cc: cbor@ietf.org; draft-ietf-cbor-array-tags@ietf.org; Francesca Palombini <francesca.palombini@ericsson.com>
Subject: Re: [Cbor] πŸ”” WGLC on draft-ietf-cbor-array-tags-03

 

On Fri, Mar 8, 2019 at 7:43 AM Laurence Lundblade <lgl@island-resort.com <mailto:lgl@island-resort.com> > wrote:

In addition to what I said before, a deterministic encoding should be specified (formerly known as canonical) in the specification and that should probably be network / big endian.

 

I think it's the job of the protocol to describe how it's encoded deterministically, rather than this tag. For example, the choice of whether or not to tag an array at all is a potential point for non-determinism to enter, so the protocol needs to specify whether there's a tag, and if so, which one. At that point, it's made the choice of little-vs-big endian, so there's no more question for this document to answer.

 

Jeffrey