[netconf] Éric Vyncke's No Objection on draft-ietf-netconf-http-client-server-17: (with COMMENT)

[Éric Vyncke via Datatracker <[e-mail]>]

Éric Vyncke has entered the following ballot position for
draft-ietf-netconf-http-client-server-17: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-netconf-http-client-server/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


# Éric Vyncke, INT AD, comments for draft-ietf-netconf-http-client-server-17

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points (but replies would be
appreciated even if only for my own education).

Special thanks to Mahesh Jethanandani for the shepherd's detailed write-up
including the WG consensus and the justification of the intended status.

I hope that this review helps to improve the document,

Regards,

-éric

# COMMENTS (non-blocking)

## What about HTTP3 ?

Is HTTP/3 (RFC 9114) so different to HTTP1/HTTP2 that it is not included in
this I-D ?

## Section 2.1.2.1

Having a module only using basic authentication seems *very* restrictive in
2024... I would have expected the WG to specify a YANG module supporting other
authentication scheme.