Re: [Cbor] Reminder and call for agenda: CBOR WG Virtual Meeting on 2023-03-08

Carsten Bormann <cabo@tzi.org> Mon, 06 March 2023 11:02 UTC

Return-Path: <cabo@tzi.org>
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 C22F9C151B19 for <cbor@ietfa.amsl.com>; Mon, 6 Mar 2023 03:02:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 QfH7OA1Tvtqa for <cbor@ietfa.amsl.com>; Mon, 6 Mar 2023 03:02:41 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 AB7F8C151B14 for <cbor@ietf.org>; Mon, 6 Mar 2023 03:02:41 -0800 (PST)
Received: from [192.168.217.124] (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 4PVbJY6KFPzDCgR; Mon, 6 Mar 2023 12:02:37 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAAse2dH3KKmRWmZvg9Nk9iF+CPVXkRDcSh1nUj6j7KmnchPCWQ@mail.gmail.com>
Date: Mon, 06 Mar 2023 12:02:37 +0100
Cc: Barry Leiba <barryleiba@computer.org>, Anders Rundgren <anders.rundgren.net@gmail.com>, Christian Amsüss <christian@amsuess.com>, Shannon.Appelcline@gmail.com, cbor@ietf.org, wolf@wolfmcnally.com
X-Mao-Original-Outgoing-Id: 699793357.316063-b495b144359353c80a4abb78e2f55952
Content-Transfer-Encoding: quoted-printable
Message-Id: <84270959-1304-47F6-BC51-99B8335B885C@tzi.org>
References: <CALaySJJ8kwtR8y9us4Qi49KFAYwus0uBoRi49rMsEO4smwfKSA@mail.gmail.com> <CALaySJJqusJ=6X06Ee4UrhQp236h079Ng3MLbTgEzEd4=9EUhQ@mail.gmail.com> <CALaySJLGk9Ztg_kMmvk=PW+=2SLf1Bkb-kmQyPz=Dbs8=DuXMA@mail.gmail.com> <CAAse2dH3KKmRWmZvg9Nk9iF+CPVXkRDcSh1nUj6j7KmnchPCWQ@mail.gmail.com>
To: Christopher Allen <ChristopherA@lifewithalacrity.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/1p5xH2O5TLqlyhbBowX_dj6sNVE>
Subject: Re: [Cbor] Reminder and call for agenda: CBOR WG Virtual Meeting on 2023-03-08
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
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, 06 Mar 2023 11:02:44 -0000

Hi Christopher,

> Is there any interest by the broader CBOR community in having Wolf McNally and I talk about our deterministic CBOR (dCBOR) libraries in Swift & Rust, either at this week’s call or virtually during your Thursday at Yokohama IETF? (We currently have some time scheduled during Dispatch on Monday). Or some other date after Yokohama?

I can’t speak for the whole community, but I am sure interested in any implications your implementation might have on standardization.
I think the CBOR meeting at IETF 116 will be a bit cramped for the discussion content we should be having, so doing this at an interim probably works better.
I don’t know what you are trying to achieve at DISPATCH; this group is for finding the right place for starting new work, not contributions to existing work (unless they are substantial enough to actually amount for new work).

> Similarly, is there interest in this community about to discuss about our Gordian Envelope draft https://datatracker.ietf.org/doc/draft-mcnally-envelope/ ? We plan to attend in person the San Francisco IETF meeting and hope there will be sufficient interest in Gordian Envelope for a BOF.

A BOF is a very formal thing in the IETF which takes months of preparation.
I think you mean what we call a “side meeting” (because the term BOF is taken for that formal thing).
Side meetings have a heavy multi-track problem, but can draw in people who would not otherwise invest time.
Such a side meeting probably needs to be announced in groups such as secdispatch and saag — this is a security protocol that just happens to use CBOR (kudos for that, of course).
Leafing through the draft, there are a lot of things that might require rethinking in the IETF (say, BLAKE3???).
(At some point we should be talking about assigning the tags that are squatted on by this draft, but maybe talking about the content is first.
Have you looked at SCITT?)

Grüße, Carsten