[Cbor] πŸ”” WGLC on draft-ietf-cbor-cde-08

Christian AmsΓΌss <christian@amsuess.com> Thu, 06 March 2025 22:34 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: cbor@mail2.ietf.org
Delivered-To: cbor@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6D49C88ADC1; Thu, 6 Mar 2025 14:34:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJlDoTDptSd5; Thu, 6 Mar 2025 14:34:11 -0800 (PST)
Received: from smtp.akis.at (smtp.akis.at [IPv6:2a02:b18:500:a515::f455]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 1798288ADB7; Thu, 6 Mar 2025 14:34:07 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com ([IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by smtp.akis.at (8.18.1/8.17.2) with ESMTPS id 526MY6na073803 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 6 Mar 2025 23:34:06 +0100 (CET) (envelope-from christian@amsuess.com)
X-Authentication-Warning: smtp.akis.at: Host [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd] claimed to be poseidon-mailhub.amsuess.com
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 96946515C5; Thu, 6 Mar 2025 23:34:05 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2001:4bb8:259:3f67:84c8:e986:484e:899b]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 2DE7C44F8B; Thu, 6 Mar 2025 23:34:05 +0100 (CET)
Received: (nullmailer pid 205279 invoked by uid 1000); Thu, 06 Mar 2025 22:34:04 -0000
Date: Thu, 06 Mar 2025 23:34:04 +0100
From: Christian AmsΓΌss <christian@amsuess.com>
To: cbor@ietf.org
Message-ID: <Z8oi3HMTum5eriSw@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="9IugkbQtiYMb4xIK"
Content-Disposition: inline
X-Scanned-By: MIMEDefang 2.86
Message-ID-Hash: MYHDVOIY4UEQIPE6CYDNX2LQZ3DEKKIC
X-Message-ID-Hash: MYHDVOIY4UEQIPE6CYDNX2LQZ3DEKKIC
X-MailFrom: christian@amsuess.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cbor.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-cbor-cde@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Cbor] πŸ”” WGLC on draft-ietf-cbor-cde-08
List-Id: "Concise Binary Object Representation (CBOR)" <cbor.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/ycBnWqFyQx2Hquixn0elDKUnP9E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Owner: <mailto:cbor-owner@ietf.org>
List-Post: <mailto:cbor@ietf.org>
List-Subscribe: <mailto:cbor-join@ietf.org>
List-Unsubscribe: <mailto:cbor-leave@ietf.org>

Hello CBOR group,

as discussed in the last interim[1], it's time to run a Working Group
Last Call on CBOR Common Deterministic Encoding (CDE) [2].

This document has seen controversial discussion. I hope that most
concerns have been addressed, and ask both those who have long since
been happy with the document and those whose concerns were addressed to
state that on the list. Likewise, for those who do not agree with the
document, this thread is a good spot to state their concerns here in a
concise way (referencing archived threads for details can help keep
things short while preserving context).

As a special note, there is a text proposal with protocol from Laurence
on design considerations around ALDRs on [3]; Carsten is taking that up
into an appendix and will provide a PR link / updated document. This is
a sufficiently isolated concern that we don't need to wait for an
integrated document (to be available when submissions reopen). If
guidance on ALDR is something where you think the current document is
lacking, please have a look at [3] or the upcoming PR.


The call will run until Marh 26th to accommodate for lack of
availability during IETF122.

Best regards,
Christian

PS. We don't have a shepherd assigned for this document, any volunteers?

[1]: https://datatracker.ietf.org/meeting/interim-2025-cbor-05/session/cbor
[2]: https://datatracker.ietf.org/doc/draft-ietf-cbor-cde/
[3]: https://mailarchive.ietf.org/arch/msg/cbor/G6w0Rz0eW9GJNd1et8I899Ua9MQ/

-- 
A beginning is the time for taking the most delicate care that the
balances are correct.
  -- Princess Irulan, Manual of Muad'Dib