Re: [core] Content-Format size for yang-cbor (and sid!)

Carsten Bormann <cabo@tzi.org> Wed, 17 March 2021 20:10 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF683A12F8 for <core@ietfa.amsl.com>; Wed, 17 Mar 2021 13:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 mFmG6q8pse1J for <core@ietfa.amsl.com>; Wed, 17 Mar 2021 13:10:39 -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 3F3B83A12FA for <core@ietf.org>; Wed, 17 Mar 2021 13:10:39 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (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 4F11Vj28j5zyXm; Wed, 17 Mar 2021 21:10:37 +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: <299C6908-F83E-42D3-87B1-883C12075780@tzi.org>
Date: Wed, 17 Mar 2021 21:10:36 +0100
X-Mao-Original-Outgoing-Id: 637704635.611284-e3c0aacf4731132e23d13cec836cb811
Content-Transfer-Encoding: quoted-printable
Message-Id: <AAF2A2A2-7820-4C47-ADF7-56EDF1036E10@tzi.org>
References: <299C6908-F83E-42D3-87B1-883C12075780@tzi.org>
To: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/VgzBJJ_YEZe8HUdk7RekevpoqkQ>
Subject: Re: [core] Content-Format size for yang-cbor (and sid!)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Mar 2021 20:10:44 -0000

And, of course the same thing for draft-ietf-core-sid and application/yang-data+cbor;id=sid.

In this case, I believe that YANG-based data structures will not just be used in the context of the larger interchanges typical of CORECONF, but also for data structures specified in YANG and interchanged separately.
Some of these will be rather small and will benefit from YANG-CBOR’s delta compression.
So I believe going for a one-byte value is more appropriate in this case.

So that the two allocations for id=sid and id=name are a bit more memorable, I now propose:

264 application/yang-data+cbor;id=name
 64 application/yang-data+cbor;id=sid

Again, comments welcome.

Grüße, Carsten