Re: [Cbor] File extension for cbor sequences

"Paul Hoffman" <paul.hoffman@vpnc.org> Wed, 25 September 2019 13:49 UTC

Return-Path: <paul.hoffman@vpnc.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 C83C8120118; Wed, 25 Sep 2019 06:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 q-5EGvxkhOJU; Wed, 25 Sep 2019 06:49:47 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEA88120108; Wed, 25 Sep 2019 06:49:46 -0700 (PDT)
Received: from [10.32.60.105] (50-1-98-250.dsl.dynamic.fusionbroadband.com [50.1.98.250]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id x8PDn5lj043534 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 25 Sep 2019 06:49:07 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-98-250.dsl.dynamic.fusionbroadband.com [50.1.98.250] claimed to be [10.32.60.105]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: cbor@ietf.org, draft-ietf-cbor-sequence@ietf.org, cbor-chairs@ietf.org
Date: Wed, 25 Sep 2019 06:49:42 -0700
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <BC319FD3-5456-4EB9-9964-1674EDC5CE48@vpnc.org>
In-Reply-To: <99AD19E5-1A5B-41C5-BB10-A7A384458E3C@tzi.org>
References: <156753408409.3422.7830964135939662716.idtracker@ietfa.amsl.com> <DFB3F8F3-3851-4B31-922E-75AF7B96AAB6@tzi.org> <99AD19E5-1A5B-41C5-BB10-A7A384458E3C@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/s9P8SjKxv3ZHIb7juigkrUl0PGg>
Subject: Re: [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:49:48 -0000

On 25 Sep 2019, at 6:15, Carsten Bormann wrote:

> 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?).

Preference: don't give one, just like JSON sequences.

--Paul Hoffman