Christian Gouret

Thanks for the celerity of your support, more over it works now with those advises above!

Ok, got it, so updated xml as follow : ``` /O-RAN/log/trace2.log sftp://[email protected]/trace2.log mysftppasswd ct:secp256r1 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDuX6C0MwNtoHyR5F8PPXSr8XEX4f2k38yQYR22RH/WnodRg2nTiD1hKqEDnhDVxRcDrNGSwfa/LfAyYB4cx11w= ``` I still have error in CLI : ``` ERROR type: application tag: operation-failed severity:...

Ok...but doing so CLI reports same error message => Unexpected valid opaque node list "keys" : ``` /O-RAN/log/trace2.log sftp://[email protected]/trace2.log mysftppasswd ct:secp256r1 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDuX6C0MwNtoHyR5F8PPXSr8XEX4f2k38yQYR22RH/WnodRg2nTiD1hKqEDnhDVxRcDrNGSwfa/LfAyYB4cx11w= ```

Thanks for the support !

Sorry, I am lost, if syntax with ct:prefix is correct, then why rpc is rejected by Netopeer2-cli ?

Is it possible to know what is this newer drafts targeted in next Netopeer2 delivery for module ietf-crypto-types ?

No, I am not looking at netopeer2 release, just want to know what is the targeted revision of the new module ietf-crypto-types ?

Thanks for the fix, it has been successfully tested !

It must be noted that whatever the revision of ietf-crypto-types, namespace remain the same : namespace "urn:ietf:params:xml:ns:yang:ietf-crypto-types"; So without model number at the end, like it could be : namespace...

Ok, understood for IETF modules embedded into Netopeer2 NC Server. But what about pure application modules, if an application has set two modules with same name, same prefix, but with...