[Cbor] File extension for cbor sequences

Carsten Bormann <cabo@tzi.org> Wed, 25 September 2019 13:15 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1BF70120806; Wed, 25 Sep 2019 06:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vOdwWjabgr_o; Wed, 25 Sep 2019 06:15:13 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3106112008A; Wed, 25 Sep 2019 06:15:13 -0700 (PDT)
Received: from [] (p548DCE50.dip0.t-ipconnect.de []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46ddp754PLz109W; Wed, 25 Sep 2019 15:15:11 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <DFB3F8F3-3851-4B31-922E-75AF7B96AAB6@tzi.org>
Date: Wed, 25 Sep 2019 15:15:11 +0200
Cc: draft-ietf-cbor-sequence@ietf.org, cbor-chairs@ietf.org
X-Mao-Original-Outgoing-Id: 591110107.561138-28f0d9f9023f0c4c2d6bc47f9304e178
Content-Transfer-Encoding: quoted-printable
Message-Id: <99AD19E5-1A5B-41C5-BB10-A7A384458E3C@tzi.org>
References: <156753408409.3422.7830964135939662716.idtracker@ietfa.amsl.com> <DFB3F8F3-3851-4B31-922E-75AF7B96AAB6@tzi.org>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/YS8wY_7FOA5mEOLSj246VQoMkjI>
Subject: [Cbor] File extension for cbor sequences
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, 25 Sep 2019 13:15:16 -0000

This is now actually the last thing missing before I can declare that all IESG comments have been addressed.  

RFC 7049 defines .cbor as the file extension for single encoded CBOR data items.

draft-ietf-cbor-sequence doesn’t define one, because it copied that RFC 7464 (JSON Text Sequences) doesn’t define one, not because of some actual thinking about the question.

Do we want to go for .cborseq?  Better ideas?  Probably not .csq (*)?  Since this is bike-shedding, I’d like to timebox this decision (to today?).

Grüße, Carsten

(*) CSQ file is a Microsoft Visual FoxPro Client-Server Query File.
I think essentially all TLAs are taken.

> On Sep 3, 2019, at 21:09, Carsten Bormann <cabo@tzi.org> wrote:
>> Alexey Melnikov added the following comment to the history of draft-ietf-cbor-sequence
>> AD review:
>> This is a well written document. I have one (non blocking) question:
>> Any particular reason why file extension is not defined in Section 6.1?
> Answer: Mindless copy/paste from RFC 7464 (JSON sequence).
> But definitely a very good point.
> At the moment I have no obvious candidate; .cborseq is a bit long, but everything else is not “speaking” enough to me.
> Grüße, Carsten
>> The document can be found at
>> I-D: <draft-ietf-cbor-sequence-01.txt>
>> Datatracker URL: https://datatracker.ietf.org/doc/draft-ietf-cbor-sequence/