Re: [core] [Cbor] map (5), ordering vs YANG SID in ietf-core-yang-cbor

Carsten Bormann <cabo@tzi.org> Thu, 17 August 2017 07:33 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 507F51327FE; Thu, 17 Aug 2017 00:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 H1x8DjEefHMc; Thu, 17 Aug 2017 00:33:51 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 692211327EC; Thu, 17 Aug 2017 00:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v7H7XmF7019034; Thu, 17 Aug 2017 09:33:48 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7FC78.dip0.t-ipconnect.de [93.199.252.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3xXyd81VJszDLdK; Thu, 17 Aug 2017 09:33:48 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20170817072903.sce5vxgckv3q3njt@elstar.local>
Date: Thu, 17 Aug 2017 09:33:47 +0200
Cc: cbor@ietf.org, core WG <core@ietf.org>
X-Mao-Original-Outgoing-Id: 524648027.541033-8d9006c7919cd41c44fdc3168b152d27
Content-Transfer-Encoding: quoted-printable
Message-Id: <9449DAD7-723C-46DE-96BE-6D46DE6E7BBE@tzi.org>
References: <13753.1502939016@obiwan.sandelman.ca> <7689DC42-6C05-462F-8466-C067B34232A9@tzi.org> <20170817065430.wp3gqiui37f26ki6@elstar.local> <BCE12092-9C93-4432-835A-EB87CB84977B@tzi.org> <20170817072903.sce5vxgckv3q3njt@elstar.local>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/FqwxHBDQ3F5qUeQjSoz2yp0aY-s>
Subject: Re: [core] [Cbor] map (5), ordering vs YANG SID in ietf-core-yang-cbor
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 17 Aug 2017 07:33:54 -0000

> On Aug 17, 2017, at 09:29, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
> Carsten,
> 
> I looked into core-sid to understand how sids work,

That document tells you how to get SIDs.

> I did not expect
> that the definition how delta sids work is in core-cbor…

That document tells you how to encode the SIDs you have into deltas in the CBOR serialization of YANG models.

I think that is a quite reasonable division of work, but maybe again there is potential for explaining this better editorially.

One problem in the past has been that people have been referring to the deltas as SIDs — they aren’t, and we need to root any remnant of that usage out of the documents.

Grüße, Carsten


> 
> /js
> 
> On Thu, Aug 17, 2017 at 09:04:07AM +0200, Carsten Bormann wrote:
>> On Aug 17, 2017, at 08:54, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>>> 
>>> Carsten,
>>> 
>>> if I search for 'delta' or 'reference SID', I do not find text that
>>> says what the reference SID is. Where do I have to look at to
>>> understand that delta SIDs are parent-referenced?
>> 
>> 4.2.1 (of yang-cbor) says:
>> 
>>   o  The delta value is equal to the SID of the current schema node
>>      minus the SID of the parent schema node.  When no parent exists in
>> 
>> But maybe there is indeed potential for editorial improvement here.
>> Clearly phrasing this always in terms of the reference SID, and then saying where that reference SID comes from (e.g., zero at the root of the tree), might help.
>> This probably also should be buttressed some more by examples.
>> 
>>> /js
>>> 
>>> PS: Why do we have this, I mean, why is there a $ for some of these?
>>> 
>>>          pattern 'Module|Submodule|feature|' +
>>> 	           'identity$|node$|notification$|rpc$|action$';
>>> 
>>>   Why is this not an enum in the first place? And why are the
>>>   first two capitalized?
>> 
>> (Now you are in core-sid, I think.)
>> Good questions; I’d defer to the YANG specialists here.
>> 
>>> PS: Why do you not import yang-identifier from ietf-yang-types?
>> 
>> Ditto.
>> 
>> Grüße, Carsten
>> 
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor
> 
>