[netconf] Re: draft-ietf-netconf-privcand private candidate | <update> operation by the server

["James Cumming (Nokia)" <[e-mail]>]

Hi Dylan,

Thanks for this observation, I agree that the wording is not ideal.  We have tried to clean it up in the next version.

Thanks

James


From: [e-mail] <[e-mail]>
Date: Friday, 9 August 2024 at 06:29
To: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: draft-ietf-netconf-privcand private candidate | <update> operation by the server

Hi



Quoting 4.7.1.1:

"The <update> operation is provided to allow NETCONF clients (or servers) to trigger a rebase of the private candidate configuration against the running configuration.The <update> operation may be triggered manually by the client or automatically by the server."



Although I fully understand the intent, I do not think the NETCONF protocol RFCs allow the server to trigger an operation, do they? Aren't only clients able to trigger operations?



Quoting RFC6241 1.1:



" o  client: Invokes protocol operations on a server.  In addition, a

      client can subscribe to receive notifications from a server.



[…]



   o  protocol operation: A specific remote procedure call, as used

      within the NETCONF protocol.



   o  remote procedure call (RPC): Realized by exchanging <rpc> and

      <rpc-reply> messages.



[…]



   o  server: Executes protocol operations invoked by a client.  In

      addition, a server can send notifications to a client."



Or quoting RFC8342 chapter 3:



"   o  client: An entity that can access YANG-defined data on a server,

      over some network management protocol.



   o  server: An entity that provides access to YANG-defined data to a

      client, over some network management protocol."



There was a similar discussion as to whether NETCONF server could set data in datastores like clients do in some RFC6243 errata e-mails. On triggering operations though, I do not know.



Do you think this should be rephrased? If so, how? Should we consider that the server is acting as a client here, or explain that the server is acting as if a client triggered the <update>?



Best regards,

Dylan Sadoun

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.