Re: [netconf] Latest ietf-netconf-server draft and related modules

[Kent Watsen <[e-mail]>]

Hi Michal,


> firstly I am sorry, somehow I missed this reply, my bad :(

No worries!  :)


>>> I had a chance to look at these modules again and have 2 questions regarding some recent changes.
>>> 
>>> - ietf-ssh-server, ssh-server-grouping/client-authentication/supported-authentication-methods> 
>>> Since the "other" leaf-list was removed there is no way to support some other methods than those specified. I am not sure whether this was the intention and if so, what is the reason for it? If nothing else, we support "interactive" authentication method but there are some others that I see no reason why they could not be used.
>> 
>> It took me a bit to determine that this change happened in ssh-client-server-18.
>> 
>> The motivation behind the change was to align the values with those defined in RFCs 4252 and 4250.
>> 
>> You mention an “interactive” and “some other” methods - where are they defined?
> 
> That is a good question. It seems no other methods are standardized but that does not mean they are not used.

What change are you hoping to see?  Is there anyway that such changes could be augmented in, or must they be in the base module?



>>> For a robust and extendible solution, why not use an identityref leaf-list with all the methods as identities? One could then simply add new ones with specific "if-feature" statements.
>> 
>> An identityref seems reasonable, could you propose a snippet of YANG for it?
>> 
>> That said, it seems equally possible for a future module to augment-in a new leaf under the "supported-authentication-methods” container...
> 
> Right, that would solve the problem, too. So you can keep it the way it is, up to you which solution you prefer. Not sure why I did not think of augments first but identityrefs. But identityrefs are much more general so the implementation should probably depend on whether these authentication methods are to be used only for this single purpose or not.

Either way is fine with me.  As the module is in WGLC currently, it would be good if others could express an option...



>>> - ietf-netconf-server, grouping netconf-server-grouping/client-identity-mappings
>>> 
>>> The "if-feature" on this container is strange. The practical problem is that if one wants to support certificates only for TLS, both one of the TLS features and "ssh-x509-certs" must be enabled. This then results in the container being defined for both SSH and TLS so there is no way to support it only for TLS or SSH.
>> 
>> Yes, granular features would be nice.  This issue is tracked here: https://github.com/netmod-wg/yang-next/issues/82 <https://github.com/netmod-wg/yang-next/issues/82>.  A possible fix would be to enable features on a per-XPath basis, perhaps using the “node-tags” draft going on in NETMOD.   Do you have a proposal?
>> 
>> BTW, shouldn’t the “if-feature” statement have an “or” (not an “and”) between the two major expressions?
> 
> Yes, I think "or" fits much better. I just was not sure whether there is not a specific reason why "and" was chosen.

OLD:        "(tls-listen or tls-call-home) and (sshcmn:ssh-x509-certs)”;
NEW:        "tls-listen or tls-call-home or sshcmn:ssh-x509-certs";

But what about your original question, are you okay with consuming modules augmenting-in use-specific if-feature statements? 


K.