[netconf] Privcand: Use with Restconf

["Robert Wills (rowills)" <[e-mail]>]

Hi working group,

In a previous email thread [1], it was suggested that the wording for draft-ietf-netconf-privcand-04 section 4.4.2.1 paragraph 6 was changed to this:

"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."

Dylan suggested the change, and Kent and Jan both gave positive feedback. (I also think it’s a good change).

With this change, when the Netconf client and server both specify the private-candidate capability in the hello exchange, the existing candidate datastore behaves like a private candidate and there is no named private-candidate datastore. In other words, “private candidate” is a mode on the existing candidate datastore. I think this simplifies the draft considerably and is a good change.

The question remains of what to do for Restconf. In the -04 draft, the client has to explicitly reference the private-candidate datastore in order to use the private candidate (because in that draft the private candidate is a separate datastore and Restconf has no client capability declaration).

After making the above wording change for Netconf, is it sufficient to say that if the Restconf server advertises the private-candidate capability, a private candidate is used when a request references the candidate datastore? This would be consistent with the new Netconf behaviour.

Rob.

[1] 2024-08-10, “[netconf] Re: draft-ietf-netconf-privcand private candidate | NETCONF client capability declaration in 4.4.2.1”