Re: [netconf] Trouble with RFC 8040 (Restconf) fields Query Parameter

[Henning Rogge <[e-mail]>]

On Tue, May 12, 2020 at 1:46 PM Per Andersson (perander)
<[e-mail]> wrote:
>
> Henning Rogge <[e-mail]> on Tuesday, May 12, 2020 12:57:
> > I noticed the following parts:
> > * "fields" and "depth" query can be combined
> > * "depth" default is unlimited
> > * "fields" can be done on the "/restconf/data" level
> > * a query to "/restconf/data" does NOT result in unlimited depth...
>
> The depth default would still be unbounded if not set explicitly.

the second/third in Example B.1.2 suggest otherwise... Client request
something from "/restconf" and only gets a tree "1 deep" (node itself
plus direct children), which would be an equivalent of "?depth=2"...

> > does this mean "depth" is always 2 for /restconf/data queries (but not
> > on sub-paths)?
> > what is about a GET to "/restconf" ?
>
> From RFC 8040
>
>     The requested data node has a depth level of "1".
>
> So, a request towards /restconf/data would yield depth level 1
> on /restconf/data, /restconf/data/node would be depth level 2,
> and so on.

Yes... "?depth=2" gives you the node itself and the direct children.

> If the request would be towards /restconf/data/node instead,
> /restconf/data/node would be depth level 1.
>
> > is the "depth" default still 2 for "/restconf/data" if there is a
> > "field" query operator?
>
> If depth and fields are combined, nodes that would be selected
> in fields (and all ancestor nodes) would have a depth value of 1.
> I.e. the path to the selected node is included even if depth is
> lower than the nodes included in fields. Otherwise the depth
> query parameter is obeyed.

Does the counting just begin when the explicit selected fields end or
does it directly jump to the depth measured from the root node?

Henning Rogge