Re: [Cbor] Request for IANA registry addition for cbor tag

Laurence Lundblade <lgl@island-resort.com> Tue, 21 January 2020 17:58 UTC

Return-Path: <lgl@island-resort.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 C2184120A69 for <cbor@ietfa.amsl.com>; Tue, 21 Jan 2020 09:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 3mtKZXGHrrms for <cbor@ietfa.amsl.com>; Tue, 21 Jan 2020 09:58:43 -0800 (PST)
Received: from p3plsmtpa11-08.prod.phx3.secureserver.net (p3plsmtpa11-08.prod.phx3.secureserver.net [68.178.252.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1517D120A5D for <cbor@ietf.org>; Tue, 21 Jan 2020 09:58:43 -0800 (PST)
Received: from [192.168.1.76] ([76.167.193.86]) by :SMTPAUTH: with ESMTPA id txnViNgNGfcRItxnViq7b5; Tue, 21 Jan 2020 10:58:41 -0700
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <644EE647-CC60-4F4C-AE4A-94B511E9597F@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FB5854B9-A90A-4247-9661-34F3457E4BC0"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 21 Jan 2020 09:58:40 -0800
In-Reply-To: <75E3B32F-CEF8-4338-917D-2264006287FF@tzi.org>
Cc: Kio Smallwood <kio@mothers-arms.co.uk>, cbor@ietf.org
To: Carsten Bormann <cabo@tzi.org>
References: <8eefb11ba6e49f7f19fd645d11d47a7f@mothers-arms.co.uk> <75E3B32F-CEF8-4338-917D-2264006287FF@tzi.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-CMAE-Envelope: MS4wfJUkjbIfRVjSGxVd+L6EWwMZYRZWGoD7DfWgIpLCpWlaJzVOdUvtHLjA5Ub6OBtKMH5r22dkeVKxtVJgApdxfsWfCz/dp9+UXlulO4lQ6ihpcv071BC/ TSexzzsGdwLLjXfYE/OUszmHKtg8OTZyh0flMCJCFSNngABY58IrE9BHWcRKLXMLhijkBLTOTAs1FvPD13w8C/BR+aahQ8d66p56fXMvUqE9JhRvBeLtzI/Z
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/tIei_wWM3zA9eVW1K6hYpk07Y6s>
Subject: Re: [Cbor] Request for IANA registry addition for cbor tag
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: Tue, 21 Jan 2020 17:58:48 -0000

Here’s some decoders types in relation to this tag:

1) It recognizes the tag, supports it and does the right thing.

2) It recognizes the tag, knows it can’t do what is required and errors out. For this decoder this type is invalid.

3) It doesn’t recognizes the tag and happens to do the wrong thing. That is perfectly OK.

4) It doesn’t recognize the tag and happens to do the right thing.

So anyone using this tag really needs to be sure they are using a decoder of type 1. Decoder types 3 and 4 are really the same in that there is no way to know which one you’ve got.

I don’t think we want some sort of implication that decoder type 3 is defective creating a situation where all decoders are forced to support this.

I think this should be spelled out in the description of this tag.

LL



> On Jan 21, 2020, at 3:26 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> Hi Kio,
> 
> overall, your registration request looks good to me.
> (Nit: The way you are using single quotes in your diagnostic notation triggers appendix G.2 of RFC 8610 [0], which apparently is not what you want.)
> In the editorial revision of RFC 7049 that we are creating right now [1], we are moving away from the concept of a strict decoder; instead we are identifying the specific checking tasks in more detail (here: map validity [2]).
> 
> Thank you for also bringing this to the WG.
> A lot of people have been suggesting one or another form of ordered map (including ordered multimaps, which would remove the need for avoiding duplicate keys).  Maybe we can have a short discussion if the registration of this kind of ordered maps is a good reason to complete registration of related kinds.
> 
> Grüße, Carsten
> 
> [0]: https://tools.ietf.org/html/rfc8610#appendix-G.2
> [1]: https://github.com/cbor-wg/CBORbis
> [2]: https://cbor-wg.github.io/CBORbis/draft-ietf-cbor-7049bis.html#rfc.section.5.3.1
> 
>> On 2020-01-21, at 12:14, Kio Smallwood <kio@mothers-arms.co.uk> wrote:
>> 
>> Hi CBOR list,
>> 
>> I'd like to register the following tag for representing key-value maps where the order of keys is significant and must be passed through encode/decode steps without re-ordering:
>> 
>> 
>> Requesting tag #272
>> Data item: array
>> Semantics: Ordered Map
>> Point of contact: kio.smallwood@flexitricity.com
>> Description of semantics (URL): https://github.com/Sekenre/cbor-ordered-map-spec/blob/master/CBOR_Ordered_Map.md
>> 
>> 
>> Thanks!
>> 
>> _______________________________________________
>> CBOR mailing list
>> CBOR@ietf.org
>> https://www.ietf.org/mailman/listinfo/cbor
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor