I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-netconf-udp-client-server-09
Reviewer: Elwyn Davies
Review Date: 2025-11-21
IETF LC End Date: 2025-12-03
IESG Telechat date: Not scheduled for a telechat

Summary: Ready.  The document is clear and appears to be in compliance wth the conventions and standards for YANG documents.  There are two trivial nits which are effectively inherited from draft I-D.ietf-netmod-rfc8407bis. I habve not run any YANG parsers on the document components.

Major issues:
None

Minor issues:
None

Nits/editorial comments:
s4, para 1: This para should probably be marked for removal by the RFC Editor on completion.

s4, para 3: [Serious nerdishness] The phrase "The Network Configuration Access Control Model (NACM) [RFC8341]" is inherited from I-D.ietf-netmod-rfc8407bis.  The acronym NACM did not immediately seem obvious - why not NCACM?  Looking at the RFC8407bis draft. I would suggest this should say "The Network Configuration (NETCONF) Access Control Model (NACM) [RFC8341]". I gather the NACM acronym has historc value and was not alteed when RESTCONF was incorporated.  I should probably make a comment on I-D.ietf-netmod-rfc8407bis.