Re: [Cbor] Reminder: CBOR WG Virtual Meeting on 2021-12-15

Michael Richardson <mcr@sandelman.ca> Wed, 15 December 2021 18:25 UTC

Return-Path: <mcr@sandelman.ca>
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 8C2D73A0A2E for <cbor@ietfa.amsl.com>; Wed, 15 Dec 2021 10:25:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 tx-uhfXXPANJ for <cbor@ietfa.amsl.com>; Wed, 15 Dec 2021 10:25:44 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CC6D3A0A17 for <cbor@ietf.org>; Wed, 15 Dec 2021 10:25:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E69CA38C55; Wed, 15 Dec 2021 13:29:52 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Aj5FSYNhoQaw; Wed, 15 Dec 2021 13:29:51 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D1CA438C50; Wed, 15 Dec 2021 13:29:51 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1639592991; bh=WMvF9b6882LnLmmlrf5pJfGzxlALgmRMDt7xUMPv9ZQ=; h=From:To:Subject:In-Reply-To:References:Date:From; b=HxKxjpvB01m0no5ygSULDfhHUhDRI3shDBregLy9s9kY+iiKhwQcSvDsIjAULyacj MfetgQ0je+IslVsKae8/NmvyM6FihKqB/cReEQOkwAVXU10mKEUZ1erlVR8gU7SDEn KUkB7Jm9/6yIYi6xn37ISxHtL1ZoIM24GglbsYF5tFpSYyrGzC60f0Y7rAIsajQ0gC wtCQ5CtV+EyAu61ujhlrcxKFV7BKJLdtTbaH4pzxFVu4701QVCC5vgAYJWp6G1TwQV eZcfds7yQ1hmdOyxL+PVl/hr8qivNIIrqys3VRQRLPeaiQWYt5mx3YvmccxBkwggQx JVaJqgMYFVfCQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 93EA0418; Wed, 15 Dec 2021 13:25:40 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, cbor@ietf.org
In-Reply-To: <B3480B8D-0FFB-468C-9BF4-1275099B9121@tzi.org>
References: <163707702504.30387.8402584115975093888@ietfa.amsl.com> <CALaySJJM9HGoC_fcqNRXDypZKwxRKYqa16Kwy+obNoPYHMY9_A@mail.gmail.com> <B3480B8D-0FFB-468C-9BF4-1275099B9121@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 15 Dec 2021 13:25:40 -0500
Message-ID: <5240.1639592740@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/x54ASyH2bbT3VprsNSWSDQtY3rI>
Subject: Re: [Cbor] Reminder: CBOR WG Virtual Meeting on 2021-12-15
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: Wed, 15 Dec 2021 18:25:49 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > This now clearly separates the case of adding a CBOR header to non-CBOR
    > Content-Formats from the CBOR Sequence Tag.  It also repairs the
    > examples, and adds an Appendix C that discusses CBOR headers to
    > non-CBOR data identified by CoAP Content-Formats.

    > Technically, there would be no need to separate 55800 and 55801 (a
    > 55801 tag will work with any data that normally would have a 55800
    > tag); but I found it clearer to provide this separation.

I'm happy to allocate/use tag 55801.

    > Let’s discuss this in 1 h…

Sorry, I started another thread because I read my email out of order, and I
had a conflict for the CBOR meeting.