IETF Logo Mail Archive

Re: [Cbor] Review of draft-ietf-cbor-packed-02

Carsten Bormann <cabo@tzi.org> Mon, 15 March 2021 20:33 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 0DBC33A0AD1 for <cbor@ietfa.amsl.com>; Mon, 15 Mar 2021 13:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 j8xEHLk22k7U for <cbor@ietfa.amsl.com>; Mon, 15 Mar 2021 13:33:49 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B79323A0ABD for <cbor@ietf.org>; Mon, 15 Mar 2021 13:33:49 -0700 (PDT)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (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 4Dzp6M2qqzzyb4; Mon, 15 Mar 2021 21:33:47 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0C959B3D-462F-4872-A8AA-12F9C90FD425@vigilsec.com>
Date: Mon, 15 Mar 2021 21:33:46 +0100
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 637533226.85946-45b86eff82f03abdb3ec8fb9bf201d73
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BB8857D-1212-4AD7-B3E7-0416C8248290@tzi.org>
References: <3835E637-85A1-44B3-812D-FD6A80EE8473@vigilsec.com> <08DB2CF6-21D7-4EE6-85C7-1E73416D1A70@tzi.org> <0C959B3D-462F-4872-A8AA-12F9C90FD425@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/LNwmSr6G_HQ0ZHQdTBo3jNkS9LU>
Subject: Re: [Cbor] Review of draft-ietf-cbor-packed-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: Mon, 15 Mar 2021 20:33:53 -0000

On 2021-03-15, at 19:40, Russ Housley <housley@vigilsec.com> wrote:
> 
> I felt this point of divergence from the original design goal needed explicit discussion.
> 
> I'm not sure what the right answer might be.  Maybe some preamble to say that a named table is needed for successfully recovering the entire content. In the current document, this context is assumed.

I added to PR#2:

>  * By the application environment, e.g., a media type.  These can
>    define tables that amount to a static dictionary that can be used in
>    a CBOR data item for this application environment.
> +  Note that, without this information, a data item that uses such a
> +  static dictionary can be decoded at the CBOR level, but not fully
> +  unpacked.
> +  The table setup mechanisms provided by this document are defined in
> +  such a way that an unpacker can at least recognize if this is the
> +  case.
>  
>  * By one or more tags enclosing the packed content.
[…]

I’m not sure that this fully addresses your comment, but I agree that it is important to make this point.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email