7 The NETCONF projects hosts multiple components relating to IETF's NETCONF Working Group:
9 * Northbound and southbound plugins for NETCONF protocol, as described in `RFC-6241 <http://tools.ietf.org/html/rfc6241>`__
10 * Northbound plugin for RESTCONF protocol, as described in `RFC-8040 <http://tools.ietf.org/html/rfc8040>`__
11 * Northbound plugin for RESTCONF protocol, as described in `an early draft <https://tools.ietf.org/html/draft-bierman-netconf-restconf-02>`__
12 * Northnound plugin for descring RESTCONF endpoint in terms of `OpenAPI 3.0 <https://swagger.io/docs/specification/about/>`__
15 Behavior/Feature Changes
16 ========================
17 The RFC8040 endpoint now correctly interprets `YANG Patch Media Type <https://datatracker.ietf.org/doc/html/rfc8072>`__
20 The ``netcon-node-topology`` YANG model has been updated to correctly mark the presence of OpenDaylight's
21 ``yang-ext:mount`` extension. This does not affect the implementation, but improves interoperability with
26 There are no new features.
28 Deprecated and Removed Features
29 ===============================
30 The ``odl-messagebus`` feature has been removed.
32 The old RESTCONF endpoint ``localhost:8181/restconf``, as installed via ``odl-restconf-nb-bierman02`` feature,
33 is now considered legacy and is expected to become deprecated in the next major release. Users are advised to
34 migrate to using the RFC8040-compliant endpoint ``localhost:8181/rests``, as installed via
35 ``odl-restconf-nb-rfc8040``.
40 The following table lists the issues resolved in this release.
42 .. jira_fixed_issues::
44 :versions: 2.0.0-2.0.11
49 The following table lists the known issues that exist in this release.
51 .. jira_known_issues::
53 :versions: 2.0.0-2.0.11