Skip to main content

Early Review of draft-ietf-netconf-list-pagination-nc-07
review-ietf-netconf-list-pagination-nc-07-opsdir-early-dunbar-2025-05-01-00

Request Review of draft-ietf-netconf-list-pagination-nc
Requested revision No specific revision (document currently at 11)
Type Early Review
Team Ops Directorate (opsdir)
Deadline 2025-05-01
Requested 2025-04-10
Requested by Kent Watsen
Authors Kent Watsen , Qin Wu , Per Andersson , Olof Hagsand , Hongwei Li
I-D last updated 2026-04-02 (Latest revision 2026-04-01)
Completed reviews Yangdoctors IETF Last Call review of -03 by Ladislav Lhotka (diff)
Yangdoctors Early review of -07 by Ladislav Lhotka (diff)
Opsdir Early review of -07 by Linda Dunbar (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Early review on draft-ietf-netconf-list-pagination-nc by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/MOSiC3u5-icOaa5Y09KzjEVMNkI
Reviewed revision 07 (document currently at 11)
Result Has nits
Completed 2025-05-01
review-ietf-netconf-list-pagination-nc-07-opsdir-early-dunbar-2025-05-01-00
I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last-call comments.

Summary: The draft defines a useful and backward-compatible extension to
support list pagination in NETCONF. It aligns well with NMDA and includes
appropriate error handling and security considerations.

Some minor issues:
 (1) It would be nice to add some guidance on logging or debugging paginated
 queries; (2) Add notes on potential resource impact from large or complex
 queries;
(3) Parameters like offset and cursor could potentially conflict. It would be
useful to add clarification when used together; (4) The draft briefly mentions
that the NETCONF list pagination YANG module may also be used with RESTCONF,
but it does not provide details on how to do so, such as how the pagination
parameters would map to RESTCONF's HTTP-based interface (e.g., query parameters
or request body).

Best Regards,
Linda Dunbar