bug report: the element into NETCONF server reply <rpc-reply> has no explicit namespace

[dubhokku]

Hello, i'am trying to make netconf request with junos-rpc yang models. The making request is succes, i make send to NETCONF server:

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
 <get-lldp-interface-neighbors xmlns="http://yang.juniper.net/junos/rpc/lldp">
    <interface-device>ge-0/0/0</interface-device>
  </get-lldp-interface-neighbors>
</rpc>

and NETCONF server sending reply:

<rpc-reply xmlns:junos="http://xml.juniper.net/junos/18.4R2/junos" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
  <lldp-neighbors-information junos:style="detail">
  </lldp-neighbors-information>
</rpc-reply>

I have use libnetconf2 for receive and parse NETCONF server reply, but call to libnetconf2 always return parsing error, because the <rpc-reply> that the server sends has not contain junos namespace ( xmlns="http://yang.juniper.net/junos/rpc/lldp" ) in the element <lldp-neighbors-information>. in case api call, libnetconf2 can only receive a correct reply. This applies to many (or all) messages sent in reply to an junos-rpc request.

I corresponded with the libnetconf2 developer and got the answer:

I am sorry but there is nothing to take into account. The reply must be parsed according to XML rules and there is nothing vague there. In this XML the namespace of lldp-neighbors-information is urn:ietf:params:xml:ns:netconf:base:1.0 and it would be incorrect to parse it in any other way. You can only report the problem to the server developers and there is nothing we can do on the client-side to fix it.

Regards,
Michal

Can you express your point of view about this and i would like to understand when making the fix of this error can be expected?

--
Regards,
Hokku