Re: [Cbor] 🔔 WGLC with request for reviews on cbor-file-magic-02

Christian Amsüss <christian@amsuess.com> Wed, 20 October 2021 14:38 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 81CA53A074B for <cbor@ietfa.amsl.com>; Wed, 20 Oct 2021 07:38:06 -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 S-tvhLcazhcf for <cbor@ietfa.amsl.com>; Wed, 20 Oct 2021 07:37:57 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9892F3A0A3A for <cbor@ietf.org>; Wed, 20 Oct 2021 07:37:48 -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 932FF401B7; Wed, 20 Oct 2021 16:37:45 +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 BB143106; Wed, 20 Oct 2021 16:37:44 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:5a9d:daee:cd20:89d6]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 7ED5D10A; Wed, 20 Oct 2021 16:37:44 +0200 (CEST)
Received: (nullmailer pid 590080 invoked by uid 1000); Wed, 20 Oct 2021 14:37:44 -0000
Date: Wed, 20 Oct 2021 16:37:44 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: core-file-magic@ietf.org
Cc: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, "cbor@ietf.org" <cbor@ietf.org>
Message-ID: <YXApuOQsLxnLw1oF@hephaistos.amsuess.com>
References: <HE1PR0701MB3050661AAA66295ECE439A4089ED9@HE1PR0701MB3050.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cBmgOX1WFfT1VAK7"
Content-Disposition: inline
In-Reply-To: <HE1PR0701MB3050661AAA66295ECE439A4089ED9@HE1PR0701MB3050.eurprd07.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/pKmA-wYmc0-f2sfXU0bUgEBQ6bo>
Subject: Re: [Cbor] =?utf-8?q?=F0=9F=94=94_WGLC_with_request_for_reviews_on_c?= =?utf-8?q?bor-file-magic-02?=
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, 20 Oct 2021 14:38:15 -0000

Hello file-magic authors,

while the minor comments have been addressed in the updates, I think
that these two were neither answered nor resulted in changes (not that
they'd necessarily would, but a change might be just as good as an
answer), could you comment on them?

On Sat, Jul 31, 2021 at 10:02:37AM +0000, John Mattsson wrote:
> - "as is a file extension"
> The draft does not say anything about how to chose a file extension. I think the needs to say something and give guidance. Are protocols supposed to use some generic ".cbor" or use there own like ".c509". Is it recommended to use several tags with the same extension, i.e., should .c509 be used for several different tags (chain, bag, CSR, CRL,...) or should each tag use its own file extension. In the later case it would be good if the file extension was registered together with tag number in IANA.
> 
> - I think it would help the reader to have an examples (CBOR diagnostic + CBOR encoding) already in Sections 3.1 and 3.2.
>   Something like the example in appendix B: "55800(1330664270(h'424F52'))"
>   Example CBOR protocol values and the resulting bytes in the file would be even better and would really help to make the draft easy to understand.

Thanks
Christian

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