IETF Logo Mail Archive

Re: [Cbor] I-D Action: draft-ietf-cbor-file-magic-06.txt

Carsten Bormann <cabo@tzi.org> Wed, 10 November 2021 22:58 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 359183A145F for <cbor@ietfa.amsl.com>; Wed, 10 Nov 2021 14:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ZwuR9ZK8BTOi for <cbor@ietfa.amsl.com>; Wed, 10 Nov 2021 14:58:11 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA9CF3A0F0F for <cbor@ietf.org>; Wed, 10 Nov 2021 14:58:10 -0800 (PST)
Received: from smtpclient.apple (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HqKy24HQrz2xcc; Wed, 10 Nov 2021 23:58:02 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <403793.1636584263@dooku>
Date: Wed, 10 Nov 2021 23:58:02 +0100
Cc: cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <745C89C5-61C7-472B-A519-816BC5994DB4@tzi.org>
References: <163484662604.2786.6905890868276647458@ietfa.amsl.com> <YYKYIzFFIGWVqNK8@hephaistos.amsuess.com> <403793.1636584263@dooku>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/21YeDSlCMU8fTUB3d_MkfWvccSc>
Subject: Re: [Cbor] I-D Action: draft-ietf-cbor-file-magic-06.txt
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, 10 Nov 2021 22:58:16 -0000

On 10. Nov 2021, at 23:44, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> a) them all to be bstr'ed
> b) for only those that happen to be CBOR to be acceptable
> c) some combination of the above, as appropriate.

d) Don’t bstr.

Define a tag 55801 that means “I’m a CBOR header for a non-CBOR file of content-format X (see next tag)”.

So it’s like a CBOR sequence, except that only the first item is CBOR, and rest is arbitrary media type till end of file.

Of course, we don’t have to do this, and can stick with 55800 for b and don’t do the others, but why should we limit ourselves so much.

Grüße, Carsten

v2.31.3 | Report a Bug | By Email | System Status