Details
-
Bug
-
Status: Resolved
-
Resolution: Cannot Reproduce
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
4446
Description
The RFC 6241, section 3.2 states that "Document Type Definitions MUST NOT appear in NETCONF content". Yet when I emit a request, the response I get from ODL contains a document type declaration.
I heard that there are devices which are not compliant with this RFC section by requiring these document type definitions to interoperate (Juniper?) but I can easily imagine that a device fails to interoperate when these document type definitions are present in the responses.
So to fix this bug and allow for interoperability it would be best to make the behavior configurable, with the default set to "do not send document type definitions". If this is already configurable, then the problem is that the default is wrong.
I just unpack the distribution, add Netconf to boot features, run Karaf and start sending the requests and the result is that the document types are sent in each reply. See the test suite at https://git.opendaylight.org/gerrit/#/c/27672 where you can see that all the *-reply.msg files contain the document type definitions; this test suite is passing but it should fail as these expected replies are not RFC compliant.