From nobody Wed Feb 15 14:39:09 2023 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05B63C1782C7; Wed, 15 Feb 2023 14:39:08 -0800 (PST) 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vj1VnWsc3rnq; Wed, 15 Feb 2023 14:39:03 -0800 (PST) Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DADCC16B5C1; Wed, 15 Feb 2023 14:39:02 -0800 (PST) Received: from smtpclient.apple (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4PHCfr0VKRzDCcj; Wed, 15 Feb 2023 23:39:00 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) From: Carsten Bormann In-Reply-To: Date: Wed, 15 Feb 2023 23:38:49 +0100 Cc: core@ietf.org, lake@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <7A07B432-3DD7-4517-B22D-C5C58E9910E6@tzi.org> References: To: =?utf-8?Q?Christian_Ams=C3=BCss?= X-Mailer: Apple Mail (2.3731.400.51.1.1) Archived-At: Subject: Re: [core] =?utf-8?q?=5BLake=5D___=F0=9F=94=94_Working_Group_Last_Ca?= =?utf-8?q?ll_=28WGLC=29_of_draft-ietf-core-oscore-edhoc-06?= X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2023 22:39:08 -0000 On 15. Feb 2023, at 23:25, Christian Ams=C3=BCss = wrote: >=20 > * 3.2 step 3: "The first CBOR byte string is the EDHOC message_3 Ah. We are using the term =E2=80=9Cbyte string=E2=80=9D to describe the = generic data model data item with that name (using major type 2 and = enclosing a sequence of bytes into a single data item). We are using the term =E2=80=9Cencoded CBOR data item=E2=80=9D to = describe the sequence of bytes that results from encoding a CBOR data = item (any CBOR data item of course, not just a byte string). So where the byte string is h=E2=80=99010203=E2=80=99, the encoded CBOR = data item encoding that data item is 43010203 hex. The latter, of course, can be carried in another byte string = h=E2=80=9943010203=E2=80=99, which would then be encoded as 4443010203 = hex. So it is really important not to confuse =E2=80=9CCBOR byte string=E2=80=9D= with =E2=80=9Cencoded CBOR data item=E2=80=9D. (Of course, this distinction applies to any representation format that = can carry its own encodings, as in the JSON text=20 =E2=80=9C{\=E2=80=9Da\=E2=80=9D: 1, \=E2=80=9Db\=E2=80=9D: 2}=E2=80=9D= =20 which is obviously not the same as the JSON text {=E2=80=9Ca=E2=80=9D: 1, =E2=80=9Cb=E2=80=9D: 2} In JSON this kind of embedding is rather expensive and thus done less = often, while in CBOR embedding encoded data items in byte strings is a = rather natural way to carry certain kinds of information.) Gr=C3=BC=C3=9Fe, Carsten