Re: [netconf] Shepherd review on draft-ietf-netconf-restconf-client-server-26

["maqiufang (A)" <[e-mail]>]

Hi, Kent

Thanks for clarification and resolving my comments. The proposed update looks good to me.

The shepherd write up has been update and is now available at https://datatracker.ietf.org/doc/draft-ietf-netconf-restconf-client-server/shepherdwriteup/.
Happy to receive any comments.

Best Regards,
Qiufang

From: Kent Watsen [mailto:[e-mail]]
Sent: Thursday, October 20, 2022 8:00 AM
To: maqiufang (A) <[e-mail]>
Cc: [e-mail]; [e-mail]
Subject: Re: [netconf] Shepherd review on draft-ietf-netconf-restconf-client-server-26

Hi Qiufang,




Hi, all

I am glad to be the doc shepherd for this draft as it moves beyond the WG with the other client-server suite of drafts.

Thank you for your valuable comments!



As part of my shepherd writeup, I’ve read the latest version of the draft and have got some comments, which I hope could be resolved before progressing the document.

Please find my responses to your comments below, and see the just-posted updated draft..


Thanks.

Best Regards,
Qiufang

Kent


Comments:
·         Sec.2.3 YANG Module
o    The author information should be updated
o    s/load balanacer/load balancer/
o    The description for feature "http-listen": s/https-listen/http-listen/

All fixed - thanks!

·
o
·         Sec.3.1.1 Features
o    Both a client and a server have defined a http-listen feature in the YANG modules;
my confusion is that, if a server supports http-listen feature, why doesn’t the client support the http-initiate feature?
In other words, if a client supports http-listen feature, why doesn’t the server support the http-call-home?

If I understand your question, the reason because the client and server may be implemented by different vendors, or by the same vendor and deployed with different settings.  Makes sense?


·         Sec.3.3 YANG Module
o    The author information is inconsistent

Fixed.


·
o
·         Sec.4 Security Considerations
o    s/NETCONF access control model (NACM)/ Network access control model (NACM)/ (applied for both 4.1 and 4.2)

Fixed (per your netconf-client-server review)


·
o
·         Sec.5.2 The "YANG Module Names" Registry
o    s/prefix: ncc/prefix: rcc/
o    s/prefix: ncs/prefix: rcs/

Fixed.


·
o
·         Sec.6. Informative References
o    Draft-ietf-restconf-client-server is self-referenced.

Fixed (per your netconf-client-server review)


Once everything settles, please update the Shepherd write-up posted to Datatracker to reflect an "all good" report (assuming that is true).

Thanks again,
Kent