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: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
