IETF Logo Mail Archive

Re: [Cbor] Adoption call for CBOR Sequences

Sean Leonard <dev+ietf@seantek.com> Tue, 30 July 2019 22:26 UTC

Return-Path: <dev+ietf@seantek.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 5D30F120072 for <cbor@ietfa.amsl.com>; Tue, 30 Jul 2019 15:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=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 8Xh_-EdvmIQV for <cbor@ietfa.amsl.com>; Tue, 30 Jul 2019 15:26:21 -0700 (PDT)
Received: from smtp-out-2.mxes.net (smtp-out-2.mxes.net [205.237.194.127]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08825120043 for <cbor@ietf.org>; Tue, 30 Jul 2019 15:26:21 -0700 (PDT)
Received: from Customer-MUA (mua.mxes.net [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 5B6E82753F for <cbor@ietf.org>; Tue, 30 Jul 2019 18:26:18 -0400 (EDT)
To: cbor@ietf.org
References: <004a01d5461b$97fba390$c7f2eab0$@augustcellars.com>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <c23a206d-d490-f9e9-2059-908c765ced64@seantek.com>
Date: Tue, 30 Jul 2019 15:25:53 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <004a01d5461b$97fba390$c7f2eab0$@augustcellars.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Sent-To: <Y2JvckBpZXRmLm9yZw==>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/SkBl9YSqfDfdWLfWYFdKym6P8Ho>
Subject: Re: [Cbor] Adoption call 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: Tue, 30 Jul 2019 22:26:22 -0000

I support adoption of this draft.

The document already describes the advantages (just concatenate together 
= easy) and disadvantages (no end-of-sequence indicator, and if a data 
item is corrupted then it is not possible to reliably decode the rest of 
the sequence) of its approach, which is good. I believe that the 
document should point out alternate ways to encode sequences (without 
specifying them, just naming/identifying alternate approaches).

Sean

On 7/29/2019 7:40 AM, Jim Schaad wrote:
> This starts a two week adoption call for draft-bormann-cbor-sequence ending
> 12 August 2019.
>
> This document describes the Concise Binary Object Representation (CBOR)
> Sequence format and associated media type "application/cbor-seq".  A CBOR
> Sequence consists of any number of encoded CBOR data items, simply
> concatenated in sequence.
>
> CBOR Chairs
> Francesca and Jim
>
>
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor

v2.23.0 | Report a Bug | By Email