Re: [netmod] Question on "bits" in YANG

[Sampathkumar Santhanakrishnan <[e-mail]>]

My assumption was "position" will help the implementers on the server side as they can map it directly to their bitmask implementation.
When "position" is carried north bound in read-only data,  the client may not be using it right ?

Thanks & Regards,
Sampath

-----Original Message-----
From: Juergen Schoenwaelder [mailto:[e-mail]] 
Sent: Thursday, February 25, 2016 11:44 AM
To: Sampathkumar Santhanakrishnan
Cc: [e-mail]
Subject: Re: [netmod] Question on "bits" in YANG

On Thu, Feb 25, 2016 at 06:48:52PM +0000, Sampathkumar Santhanakrishnan wrote:

> I have a question on "bits" type in YANG. Does it make sense to use 
> "bits" in "config:false" attributes ?

Yes, why would it not make sense?

> As per my understanding in the read-only uses cases, the bits 
> "position" is not much useful. Please clarify.

Why do you think the position is meaningful for config true but not for config false leafs or date that is shipped in RPCs or actions or notifications? Here is the relevant text:

   The "position" statement, which is optional, takes as an argument a
   non-negative integer value that specifies the bit's position within a
   hypothetical bit field.  The position value MUST be in the range 0 to
   4294967295, and it MUST be unique within the bits type.  The value is
   unused by YANG and the NETCONF messages, but is carried as a
   convenience to implementors.

The position is a 'convenience to implementors' and this convenience applies equally well to clients and servers.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <http://www.jacobs-university.de/>