[Cbor] file-magic: "What to pick" text?

Christian Amsüss <christian@amsuess.com> Wed, 23 June 2021 16:11 UTC

Return-Path: <christian@amsuess.com>
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 48E163A3C7F; Wed, 23 Jun 2021 09:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lAugq99GWeQS; Wed, 23 Jun 2021 09:11:22 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BCB43A3C7C; Wed, 23 Jun 2021 09:11:21 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id BA6B64000E; Wed, 23 Jun 2021 18:11:14 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (poseidon-mailbox.amsuess.com [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id F3761D7; Wed, 23 Jun 2021 18:11:10 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:7357:eb96:fa0b:c937]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 94F677D; Wed, 23 Jun 2021 18:11:10 +0200 (CEST)
Received: (nullmailer pid 1123995 invoked by uid 1000); Wed, 23 Jun 2021 16:11:10 -0000
Date: Wed, 23 Jun 2021 18:11:10 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: draft-ietf-cbor-file-magic@ietf.org, cbor@ietf.org
Message-ID: <YNNdHguTxEY32yEa@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="eJk1HY4LqxWglN6w"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/HAlhSW_9x1QqTfhynJVPe2d1W44>
Subject: [Cbor] file-magic: "What to pick" text?
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, 23 Jun 2021 16:11:26 -0000

Listening to today's COSE discussion, I think that with file-magic, it'd
help to include some guidance on what to pick when developing a CBOR
based format, especially (but not only) if the content-format proposal
gets included:

* Why would an application pick a wrapped or a sequence tag?
* Are there good reasons to register a content format (for inline use)
  *and* a tag for the above? Under which conditions should which be
  used?

(And other than for "if you already have a content format, that may be
enough" I'm not sure I can answer them -- but I think we should.)

BR
c

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom