Re: [netconf] restconf collections

[Andy Bierman <[e-mail]>]

On Sat, Sep 26, 2020 at 10:21 AM Kent Watsen <[e-mail]> wrote:

> Hi Qin,
>
> (My concern is that the IETF version will be too complex to implement or
> use as the feature list grows.)
>
> [Qin]:That’s the issue we try to address in our customer’s scenarios. If
> the solution only focuses on list, the complexity is controllable. If the
> scope is not limited to list, XAPTH filtering and query actually provides a
> good solution to navigate from root node to leaf node.
>
>
> The functionality is only for lists.  The functionality (e.g., paging)
> being discussed only make sense for lists...
>
>
> It is easy. Use RPC operations which map to RESTCONF POST automatically.
>
>
>
> [Qin]: Agree, NETCONF fragment provide an example on what RPC operations
> look like
>
> https://tools.ietf.org/html/draft-zheng-netconf-fragmentation-02
>
> which is similar to getbulk operation.
>
>
> The <get-block> RPC may be a good starting point.  It would be good to
> also look at Andy’s <get-bulk> RPC for inspiration.
>
>
>
The <get-block> operation seems very stateful and seems to be tied to the
existing get-config operation

The <get-bulk> operation is not stateful.
 http://www.netconfcentral.org/modulereport/yumaworks-getbulk


There are 3 completely different approaches:

  1) stateless
  2) stateful
  3) stateful snapshot

How to efficiently iterate through data that is changing constantly?
This problem is harder than it looks.


K.
>
>
Andy