Subject: [netconf] List Pagination Open Issue #1: Cusor Support

From: Qin Wu <[email-masked]>
Date: Wed, 22 Dec 2021 12:11:35 +0000

Hi, All:
In draft-wwlh-netconf-list-pagination-00，we define five query parameters for list pagination and One query parameter for descendant list pagination. These query parameters provide offset based list pagination.
One of features we would like to investigate is cursor support, which has been brought up in IETF 112 NETCONF virtual meeting:
For server w/ cursor support:
* It Enables the paging to continue over the snapshot, despite the dataset changing.
* The client assumes the list doesn’t change;
b.  For server w/o cursor or snapshot support:
* The server might return larger remaining value than previous fetch during refetching page in a time series log (where logs are appended).
c.  For config, some protocols support locks (to prevent out-of-band changes), while others support tag/timestamps (enabling out-of-band changes to the detected), so the issue is effectively limited to opstate lists.
Based on the above our analysis, it looks we don’t have compelling use case, therefore cursor support is not needed in this work.

If you have different opinion, please let us know.

-Qin (on behalf of Authors)