From nobody Mon Aug 17 11:23:37 2020 Return-Path: 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 EFEEC3A154E for ; Mon, 17 Aug 2020 11:23:35 -0700 (PDT) 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 SqZ-4ZrKeKF5 for ; Mon, 17 Aug 2020 11:23:33 -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 D58DF3A1576 for ; Mon, 17 Aug 2020 11:23:03 -0700 (PDT) Received: from [172.16.42.100] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (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 4BVj8P638RzytY; Mon, 17 Aug 2020 20:23:01 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) From: Carsten Bormann In-Reply-To: Date: Mon, 17 Aug 2020 20:23:01 +0200 Cc: cbor@ietf.org X-Mao-Original-Outgoing-Id: 619381381.37963-12b2a228f480908bd0f20f15a704a80c Content-Transfer-Encoding: quoted-printable Message-Id: <1FC978C4-5EB5-42D9-B522-28D72FDCA5B9@tzi.org> References: <5F695632-CF27-40FF-BC23-E731AAA95771@island-resort.com> <895A3DF8-DF11-479F-9DC6-9EF98465A7E0@tzi.org> To: Laurence Lundblade X-Mailer: Apple Mail (2.3608.120.23.2.1) Archived-At: 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\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2020 18:23:36 -0000 On 2020-08-17, at 19:56, Laurence Lundblade = wrote: >=20 > At this point the word =E2=80=9Ctag=E2=80=9D is confusing to me. When = you say =E2=80=9Cuse Tag 1=E2=80=9D you seem to mean encode a type 6 = integer (The argument is not used as an integer, but as a tag number.) > with value 1 followed by the content which is a number. Yes. > Unless explicitly allowed, the type 6 integer and number content are = inseparable.=20 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=E2=80=99t using a Tag, you = are using the definition of a Tag content data structure (or =E2=80=9Can = unwrapped tag=E2=80=9D, if you must say so). > When you say USE tag 1, it means both the type 6 integer and the = number content. By contrast, when CWT refers to the =E2=80=9CCWT tag=E2=80= =9D it is just referring to the type 6 integer. We recently revisited that terminology in 7049bis; this is a bit similar = (but inverse) to what are tags and elements in XML =E2=80=94 what are = called elements in XML (except by the 95 % who don=E2=80=99t know the = difference between a tag and an element) are tags in CBOR, and what are = tags in XML are not really discussed very much (they are briefly = referred to as =E2=80=9Cheads=E2=80=9D). Gr=C3=BC=C3=9Fe, Carsten