IETF Logo Mail Archive

Re: [Cbor] CBOR-packed: comments and function tag suggestion

Carsten Bormann <cabo@tzi.org> Wed, 28 February 2024 08:01 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 6A780C14CEED for <cbor@ietfa.amsl.com>; Wed, 28 Feb 2024 00:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 PugDPawfQOba for <cbor@ietfa.amsl.com>; Wed, 28 Feb 2024 00:01:34 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (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 79001C14F700 for <cbor@ietf.org>; Wed, 28 Feb 2024 00:01:32 -0800 (PST)
Received: from smtpclient.apple (p548dcbf2.dip0.t-ipconnect.de [84.141.203.242]) (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 4Tl6Ht2bSwzDCcZ; Wed, 28 Feb 2024 09:01:30 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <fa8ac454-22d7-4a36-9d20-64f74dd4c64d@tu-dresden.de>
Date: Wed, 28 Feb 2024 09:01:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4FC450D-0B9F-4607-A751-3E8D04A559A7@tzi.org>
References: <1edff8c7-7975-4ede-9737-eac0165ef1b3@tu-dresden.de> <3C49548A-B6F4-4980-9FAF-57B511404E9D@tzi.org> <fa8ac454-22d7-4a36-9d20-64f74dd4c64d@tu-dresden.de>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Xiub2CgpnAimb2Y23EUJIkOaby4>
Subject: Re: [Cbor] CBOR-packed: comments and function tag suggestion
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: Wed, 28 Feb 2024 08:01:38 -0000

On Feb 26, 2024, at 11:57, Mikolai Gütschow <mikolai.guetschow@tu-dresden.de> wrote:
> 
> In the IANA Considerations in Section 6.1, tags 224..255, 28704..32767, 1879052288..2147483647, 216..223, 27647..28671, 1811940352..1879048191, are all requested with the contained data item being "text string, byte string, array, map, tag", which should be changed to "any" then?
> 
> Also the last paragraph of Section 2.2 constraints the content to "string or container (map or array)". This should be adapted to "anything else than an integer"?


For those not following the GitHub repo:

This was solved in https://github.com/cbor-wg/cbor-packed/pull/18

Diff of the generated plaintext: https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-cbor-packed&url_2=https://cbor-wg.github.io/cbor-packed/draft-ietf-cbor-packed.txt

Together with any other comments we get, this will go into a -12, which we should have before or on the IETF 119 I-D cutoff day next Monday.
Please keep those comments coming...

Grüße, Carsten

v2.23.0 | Report a Bug | By Email