IETF Logo Mail Archive

Re: [Cbor] Status of Appendix A in RFC 8949

Carsten Bormann <cabo@tzi.org> Fri, 05 May 2023 09:17 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 EB213C151B34 for <cbor@ietfa.amsl.com>; Fri, 5 May 2023 02:17:14 -0700 (PDT)
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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U3_kjIpbbx5P for <cbor@ietfa.amsl.com>; Fri, 5 May 2023 02:17:10 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78818C14CEED for <cbor@ietf.org>; Fri, 5 May 2023 02:17:09 -0700 (PDT)
Received: from [192.168.217.124] (p548dc0f6.dip0.t-ipconnect.de [84.141.192.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4QCQ745KktzDCf9; Fri, 5 May 2023 11:17:04 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CADEL5zsgq+yxB+dd5vpVpB4A8xs86h+JGz6Mb9aZNPyEmxct_g@mail.gmail.com>
Date: Fri, 05 May 2023 11:17:04 +0200
Cc: cbor@ietf.org
X-Mao-Original-Outgoing-Id: 704971023.72763-e0b71809d500467dbd2affb11a0c5f8b
Content-Transfer-Encoding: quoted-printable
Message-Id: <C76EF730-DDD0-4E63-8933-58225C921668@tzi.org>
References: <8233a692-df84-f093-96bf-fe99c03adfc5@gmail.com> <31111796-3CF7-4F8F-A805-4CBE1124E9D8@tzi.org> <e16961f5-edbc-233e-3e24-e3a20bc57ea4@gmail.com> <83052D85-36BE-45AA-81EA-A46068B89D95@tzi.org> <CADEL5zsgq+yxB+dd5vpVpB4A8xs86h+JGz6Mb9aZNPyEmxct_g@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/C-w1oaF-i7cwAJN5yQiF1wAn8rA>
Subject: Re: [Cbor] Status of Appendix A in RFC 8949
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 05 May 2023 09:17:15 -0000

On 2023-05-05, at 10:16, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
> A diagnostic notation parser/decoder would generate 0x23 for -4.0.

When an application uses a dCBOR library to encode a -4.0, the CBOR generic data model will see a -4, which is shown as -4 in diagnostic notation and as 0x23 in the encoded data item.

You can write an application that takes CBOR diagnostic notation for -4.0, ingests this to a CBOR generic data model, applies dCBOR rules to that, and then encodes it using CBOR deterministic encoding rules.  The diagnostic notation for the latter will show -4, not -4.0.

Grüße, Carsten

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