[netconf] Re: draft-ietf-netconf-privcand private candidate | NETCONF client capability declaration in 4.4.2.1

["Jan Lindblad (jlindbla)" <[e-mail]>]

Dylan, Kent,

I too like the proposed wording. As an extension of this, maybe the document would be easier to digest if it did not describe the functionality as an introduction a new datastore at all, but rather a new mode of operation for the existing candidate datastore. I believe someone already proposed this idea during the IETF120 WG session.

Best Regards,
/jan

From: Kent Watsen <[e-mail]>
Date: Saturday, 10 August 2024 at 18:06
To: [e-mail] <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: [netconf] Re: draft-ietf-netconf-privcand private candidate | NETCONF client capability declaration in 4.4.2.1



On Aug 9, 2024, at 6:27 AM, [e-mail] wrote:

Hi

As per James C. (co-author) preference, I am sending all other questions and remarks I have on this draft.

Quoting 4.4.2.1:

"All RPC requests that target the candidate configuration datastore will operate in exactly the same way as they would do when using the shared candidate configuration datastore, however, when the server receives a request to act upon the candidate configuration datastore it instead uses the session's private candidate configuration datastore."

I find this formulation quite difficult to undertand.

Also, quoting 2.2:
"The candidate configuration datastore defined in [RFC6241] is referenced as the shared candidate configuration in this document."

Thus I suggest a different and simpler formulation for 4.4.2.1:
"All RPC requests that target or impact the shared candidate configuration datastore will implicitly target or impact the session's private candidate configuration datastore instead, and operate in exactly the same way."

What do you think?


I like it.
I agree that 4.4.2.1 should take into account 2.2.
The proposed text is clearer (more direct)

K.



Best regards,
Dylan Sadoun
Orange Restricted


____________________________________________________________________________________________________________

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.
_______________________________________________
netconf mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>