On Fri, Dec 08, 2017 at 04:03:06PM +0100, Martin Bjorklund wrote: > Vladimir Vassilev <[email protected]> wrote: > > On 11/15/2017 06:29 PM, Robert Wilton wrote: > > > > > I don't think that this is really a good idea. You would end up > > > returning server metadata in addition to the configuration. > > Obviously RFC 7895 defines only config false; data and I was not > > proposing a change to that. But I agree something has to be added to > > complete the solution. Special purpose datastore identities can be > > defined that return instance of yang-library data when read with > > <get-data>. (Datastores with yang-library config false; only data not > > represented in 'operational') > > > > Adding this special yang-library-datastore to the proposed > > ietf-datastores container e.g. > > > > module: ietf-datastores > > +--ro datastores > > | +--ro datastore* [name] > > | +--ro name identityref > > | +--ro yang-library-datastore identityref > > > > I don't understand this proposal. How would a client learn the > library for <running>? For <operational>?
My interpretation is that the client reads the datastores list from <operational> and the list entries give you the identity of a separate datastore that gives you the content of the yang library for that datastore. (For each datastore, you have a separate datastore to report its yang library.) /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
