Re: [netconf] Question about RFC8040 data root node and depth example

[Henning Rogge <[e-mail]>]

On Thu, May 7, 2020 at 11:46 AM Per Andersson (perander)
<[e-mail]> wrote:
> I would say this is an error in RFC 8040, there is no note about it
> in the Errata. [0]

ok.

> > The second is about GET queries directly to the /data node, as it is
> > done in example B.3.3.
> >
> > Is the server meant to "join" both the ietf-restconf,
> > ietf-yang-library and the "user" datamodel into a larger one? This is
> > interesting because the ietf-restconf yang model does not event
> > implement any container, only a grouping that could be used by other
> > models.
>
> Under the unified datastore (i.e. {+restconf}/data node), all top level
> nodes would be found

**sigh** I was worried to get this answer. My current implementation
of the "yang data model" does load one library file... not a
hierarchical series of libraries...

This makes iterating over the "unified" datastore 'interesting',
especially because of the depth/fields query parameter.

> {
>   "ietf-restconf:data": {
>     "ietf-yang-library:yang-library": {},
>     "example-jukebox:system": {},
>     "example-jukebox:jukebox": {},
>     "ietf-restconf-monitoring:restconf-state": {}
> }

In theory It should be possible to define the "data" YANG model and
then import/augment everything from there, right?

> Note that example-jukebox have two top level nodes.

I assume this is just your example, not the "example-jukebox" in the
RFC 8040, right?

Henning