Backward compatibility for NETCONF 1.0 version

[hsynercn]

Can I use the NETCONF 1.0 with v2.2.0, as I understand the current version is locked for NETCONF 1.1.

netconf-java/src/main/java/net/juniper/netconf/element/Hello.java

Line 183 in 8271420

final String BASE_11 = "urn:ietf:params:netconf:base:1.1";

[peterjhill]

It might be good as is.. it will be good after my next PR gets merged..

Based on the current code, the default Device path is not “locked to 1.1” in the way the customer fears:

Default client capabilities include base:1.0 in Device.java (line 68).
Hello.build() auto-adds base:1.1 in Hello.java (line 181).
The actual hello payload is built from those capabilities in Device.java (line 398).
On the server side, framing falls back to legacy delimiter mode when the server hello does not advertise base:1.1; see NetconfSession.java (line 319) and NetconfSession.java (line 1325).
The tests already back this up:

Default device hello includes both base:1.0 and base:1.1 in DeviceTest.java (line 341).
A server hello with only base:1.0 is handled in NetconfSessionTest.java (line 244).
A server hello with base:1.1 triggers chunked framing in NetconfSessionTest.java (line 259).
So the precise answer is:

Yes, it can interoperate with standards-compliant NETCONF 1.0 servers.
No, it does not let you force a pure “advertise only 1.0, never 1.1” client hello. If someone wants that for a broken old server, that would be a separate non-standard compatibility mode.

[peterjhill]

#83
includes new docs/compatability.md file
https://github.com/Juniper/netconf-java/pull/83/changes#diff-16cdac13dd8a32decd591a6b2ab41b65468dc12835e78ee1bceb4e6b7fbcf315