Re: [Cbor] Tagging requirement
Laurence Lundblade <lgl@island-resort.com> Mon, 17 August 2020 20:37 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 4694F3A11E2 for <cbor@ietfa.amsl.com>; Mon, 17 Aug 2020 13:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 FyTHpbnN5fc6 for <cbor@ietfa.amsl.com>; Mon, 17 Aug 2020 13:37:49 -0700 (PDT)
Received: from p3plsmtpa07-05.prod.phx3.secureserver.net (p3plsmtpa07-05.prod.phx3.secureserver.net [173.201.192.234]) (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 138D23A10FB for <cbor@ietf.org>; Mon, 17 Aug 2020 13:37:49 -0700 (PDT)
Received: from [192.168.1.49] ([76.167.193.86]) by :SMTPAUTH: with ESMTPA id 7lt6kkqphkxIh7lt6kd6Cw; Mon, 17 Aug 2020 13:37:48 -0700
X-CMAE-Analysis: v=2.3 cv=SPU8q9nH c=1 sm=1 tr=0 a=t2DvPg6iSvRzsOFYbaV4uQ==:117 a=t2DvPg6iSvRzsOFYbaV4uQ==:17 a=IkcTkHD0fZMA:10 a=gKmFwSsBAAAA:8 a=K6EGIJCdAAAA:8 a=ey7ATvvnupcXmTZE4YAA:9 a=v15LZa1yhbqMXTkt:21 a=-4PSTzjWFYep3vxg:21 a=QEXdDO2ut3YA:10 a=nnPW6aIcBuj1ljLj_o6Q:22 a=L6pVIi0Kn1GYQfi8-iRI:22
X-SECURESERVER-ACCT: lgl@island-resort.com
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Laurence Lundblade <lgl@island-resort.com>
In-Reply-To: <1FC978C4-5EB5-42D9-B522-28D72FDCA5B9@tzi.org>
Date: Mon, 17 Aug 2020 13:37:47 -0700
Cc: cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <72CC1398-659B-4934-8851-50B8BB4752E1@island-resort.com>
References: <5F695632-CF27-40FF-BC23-E731AAA95771@island-resort.com> <895A3DF8-DF11-479F-9DC6-9EF98465A7E0@tzi.org> <D8A304BA-897A-46D2-9B67-4FF458883478@island-resort.com> <1FC978C4-5EB5-42D9-B522-28D72FDCA5B9@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-CMAE-Envelope: MS4wfJcjXT0W6Q5FbcXUwUr2oQEDOKblPFHZUDpvomgh4ndyuEpY3hzQzqzmf/Ck4n2iCWF9ZpMrzygpLRApJ1pLuYU+lSakqgCG3oEO1gzLjcVI21Ez/ell kZEBQNtDglMNjpHNxPOuztU9M6FIaSkyT+3uOLP53FD831bbx1pY+cBJgjT9EtY6GNRjuixu5F5F5w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/mG9SiSLrNpo_sSELLmS5ufwKD3w>
Subject: Re: [Cbor] Tagging requirement
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: Mon, 17 Aug 2020 20:37:56 -0000
> On Aug 17, 2020, at 11:23 AM, Carsten Bormann <cabo@tzi.org> wrote: > > On 2020-08-17, at 19:56, Laurence Lundblade <lgl@island-resort.com> wrote: > >> with value 1 followed by the content which is a number. > > Yes. > >> Unless explicitly allowed, the type 6 integer and number content are inseparable. > > As long as you are talking about Tags, yes: Tags are a major-type 6 container. > You can also borrow the definition of a Tag content data structure for an application protocol, but then you aren’t using a Tag, you are using the definition of a Tag content data structure (or “an unwrapped tag”, if you must say so). What do you think about defining CBOR protocol items that can be either tag-contained or unwrapped? In CDDL, “dualistic_bigfloat = bigfloat / ~bigfloat”. Making a distinction in the way CWT is defined and named from the way epoch date, bignum and such are defined is what clears it up for me. The definition of the CBOR structure for CWT is independent of the CWT tag. The CBOR structure for the CWT is defined first. Then the tag definition comes a long and says is contents is a CWT. For tags epoch date, bignum and such there is no independent definition of the contents. That content definite is wrapped up with the tag definition. If you want to use the content without a tag-container you have to unwrap it. That a tag is a “container” is really helpful to me. Thanks for the discussion on this! LL
- [Cbor] Tagging requirement Laurence Lundblade
- Re: [Cbor] Tagging requirement Carsten Bormann
- Re: [Cbor] Tagging requirement Laurence Lundblade
- Re: [Cbor] Tagging requirement Carsten Bormann
- Re: [Cbor] Tagging requirement Laurence Lundblade
- Re: [Cbor] Tagging requirement Michael Richardson
- Re: [Cbor] Tagging requirement Carsten Bormann
- Re: [Cbor] Tagging requirement Carsten Bormann
- Re: [Cbor] Tagging requirement Laurence Lundblade
- Re: [Cbor] Tagging requirement Michael Richardson