Re: [core] js review of draft-ietf-core-yang-cbor-12

Carsten Bormann <> Tue, 07 April 2020 20:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0AA533A0FA8; Tue, 7 Apr 2020 13:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oPs3gM_ub51Y; Tue, 7 Apr 2020 13:55:33 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4940D3A1279; Tue, 7 Apr 2020 13:55:31 -0700 (PDT)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 48xfnF2CHHzyTQ; Tue, 7 Apr 2020 22:55:29 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Tue, 07 Apr 2020 22:55:28 +0200
Cc: Ivaylo Petrov <>, NetMod WG <>, core <>
X-Mao-Original-Outgoing-Id: 607985728.761826-987ad46b9786698c380faa14070a030a
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Juergen Schoenwaelder <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [core] js review of draft-ietf-core-yang-cbor-12
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 07 Apr 2020 20:55:36 -0000

On 2020-04-07, at 21:47, Juergen Schoenwaelder <> wrote:
> For me, the question is whether this ID defines SIDs and the other ID
> details how they are managed or this ID imports the definition of SIDs
> from the other document, which also details how they are managed.
> Right now, it seem something in between, i.e., it is not clear what
> the dependencies between these specifications is.

Thank you for that feedback.

So I think we need to be a bit more radical/precise:

-YANG-CBOR should explain that SIDs are 63-bit unsigned integers and how the delta encoding in the CBOR map keys works.  I.e., define the concept, but not the number space management.

-sid does the latter.

The document that defines the media types (comi) gets to bind YANG-CBOR, for these media types, to the specific SID concept defined in -sid.

-YANG-CBOR can still refer to -sid as a preferred way to manage the number space.
But you can implement -YANG-CBOR without understanding -sid, so this is not a normative reference.
Any other document using -YANG-CBOR can refer to -sid as well (or, exceptionally, to something specific for that usage).

Grüße, Carsten