obbaa appears not support NETCONF SSH Call Home

[commuser]

We are taking the latest obbaa build and followed the instructions from the obbaa-forum website and tested with the netconf-simulator, and found that the obbaa appear not support NETCONF SSH Call Home. It does support the TLS Call Home. Is this the case and why the SSH is not supported?

[vcmahadevan]

OBBAA supports only TLS Callhome . SSH is supported only for direct connection
We wanted to have one reference implementation of Callhome and chose TLS based approach. Can you let us know if you would like to have SSH based CH? If so we can look into the request. Nevertheless if you are willing to contribute we would be happy to have you in our team.

[commuser]

Thanks for the quick reply. We are analyzing the various approaches and haven't made any decisions. However, it appears that adding SSH is not trivial. First the bbf-obbaa-network-manager YANG model seems not having the SSH call home supported as the under 'call home' only has option to specify a DUID, which is a verifier in server TLS certificate, but not be able to specify SSH client credentials such as SSH key or username/password. If YANG model needs change, then I'm not sure this will impact from the NBI all the way down to SBI including the basic data models in between. Also it appears that the existing SSH client used for direct connection which uses MINA SshClient and ClientSession can not be easily re-used in the Netty NIO ChannelPipeLine handlers currently used by the TLS call home.