Re: [netconf] Comments on draft-ietf-netconf-keystore v17

[Juergen Schoenwaelder <[e-mail]>]

On Wed, Jun 24, 2020 at 08:07:19PM +0000, Eric Voit (evoit) wrote:
> 
> 1) Already the draft “supports” the existence of a multiplicity of keystores.  Please refer to the exchange I had with Juergen on this thread regarding how my personal project does just this by a) NOT *implementing* "ietf-keystore” and b) NOT enabling either the “keystore-supported” or “local-definitions-supported” features, while c) augmenting in new leafref definitions into the “local-or-keystore” choice statements pointing to my application-specific instances as needed.   All this to say that it’s possible.
> 

True for some definition of "supports".

If the requirement is that we need to support multiple keystores, then
the container keystore should be turned into a list keystore. If the
requirement is to support multiple keystores located at various places
in the schema tree, well, then we likely can't do this properly with
plain YANG 1.1, but possibly with schema mount.

/js

PS: My definition of "supports" would imply interoperability. The
    current approach of "there is a grouping and if you tweak it
    enough it can give you multiple keystores" is not interoperable
    unless we standardize the tweaks.

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>