Early Review of draft-ietf-netconf-over-quic-04
review-ietf-netconf-over-quic-04-opsdir-early-liu-2025-07-11-00

I have reviewed draft-ietf-netconf-over-quic-04 as part of the Operational
directorate's ongoing effort to review all IETF documents being processed by
the IESG. These comments were written with the intent of improving the
operational aspects of the IETF drafts. Comments that are not addressed in last
call may be included in AD reviews during the IESG review. Document editors and
WG chairs should treat these comments just like any other last call comments.

   “This document specifies how to use QUIC as a secure transport for
   exchanging Network Configuration Protocol (NETCONF) messages.  QUIC
   provides encryption properties similar to TLS, while eliminating TCP
   head-of-line blocking issues and also providing more loss detection
   and congestion control than UDP.  NETCONF over QUIC has privacy
   properties similar to NETCONF over TLS.”

My overall view of the document is 'Has Nits' for publication.

** Technical **

- The mapping of single or multiple NETCONF sessions to QUIC connections lacks
sufficient clarity in the current text. It is recommended that Sections 3 and 4
be revised to elaborate on this point, thereby preventing potential
ambiguities. - Given that the document aims to propose QUIC as a secure
transport protocol, the Security Considerations section, particularly in
relation to NETCONF over TLS, warrants more detailed exposition. -
Additionally, it is observed that the inclusion of a YANG Module in the
document is not mentioned in the Abstract or Introduction. It is advisable to
emphasize this relevant information early in the draft. - Further, details
regarding the current implementation status and the tangible advantages over
TCP would be valuable additions, and it is suggested that such content be
incorporated into the draft.

** Editorial **

No.