Re: [netconf] Current activities on RESTCONF/NETCONF to support paging

[Mikael Abrahamsson <[e-mail]>]

On Thu, 14 Mar 2019, Juergen Schoenwaelder wrote:

> One of the issues to consider is that depending on the datastore
> accessed, the data can change more or less rapidly and it is unclear
> whether you want servers to maintain potentially big amounts of state
> between requests. If you retrieve data in chunks, the question is
> whether you can simply put the data back together or the client side
> or whether this may lead to data that never really existed in that
> form on the server. With RESTCONF, etags may help to check whether the
> resource queried remains consistent (but then the server still has to
> be able to decide etag changes).
>
> But backing up for this discussion of details, I agree that this is a
> problem worth solving by standardizing a common solution.

We have run into several use-cases where we'd like to be able to handle 
tens of millions of entries and still keep it declarative configuration 
and stay away from RPCs (which is what often is suggested).

Examples of these use-cases are AFTR binding tables (think huge NAT/tunnel 
box), DHCP servers (with millions of leases potentially also configured 
static leases) and DNS servers (tens of millions of DNS zones).

So yes, I fully support working on solving this problem-space.

-- 
Mikael Abrahamsson    email: [e-mail]