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

From: Qin Wu <[email-masked]>
Date: Mon, 18 Mar 2019 01:39:41 +0000

-----邮件原件-----
发件人: netconf [mailto:[email-masked]] 代表 Wisotzky, Sven (Nokia - DE/Stuttgart)
发送时间: 2019年3月15日 16:48
收件人: wangzitao <[email-masked]>; Douglas Hubler <[email-masked]>
抄送: [email-masked]
主题: Re: [netconf] Current activities on RESTCONF/NETCONF to support paging

> Actually, there are some discussions in this WG. And there is an https://datatracker.ietf.org/drafts/draft-ietf-netconf-restconf-collection draft that try to address these issues (https://tools.ietf.org/html/draft-ietf-netconf-restconf-collection-00). IMO, these problems also exist in NETCONF, therefore, a common solution is required. 
 
It should have been clear from my initial ask. Yes, I am actually interested in a solution which serves both NETCONF and RESTCONF. The problem might be seen more important for RESTCONF - as this is considered protocol of choice for network controllers, talking about a larger scale of objects and traditionally used for communication between WebUI and back-end.

The bigger challenge regarding NETCONF is, that networking devices are often more restricted regarding management plane footprint (CPU/Memory). So whatever solution we come up with, it must be easy to implement without requiring large server-side footprint.

[Qin]: Agree, there is another relevant draft https://tools.ietf.org/html/draft-zheng-netconf-fragmentation-00
which try to address this issue. But the big challenge is large size data handling, whether it should be stateless or stateful. How much state does both side need to keep?

Sven 

_______________________________________________
netconf mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/netconf