Medium NETCONF release plan status can be found by looking at it's release page in jira
The plan is best effort and subject to change.
At the time of this TSC ticket creation, the following NETCONF tickets are listed:
| T | Key | Summary |
|---|---|---|
| connection-timeout-milliseconds parameter is not working properly for ssh connections | ||
| Conflicting modification for path /(urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring?revision=2017-01-26)restconf-state | ||
| ListenerAdapter needs to serialize JSON directly | ||
| CSIT regression in netconf-csit-1node-scale-only-sodium | ||
| NETCONF southbound requires notifications.yang model to be present on the device | ||
| Separate out schemaless mountpoints | ||
| Eliminate duplicate SchemaRepositoryProviderImpl | ||
| Refactor SchemaRepositoryProvider into its own component | ||
| Non-clustered NETCONF topology leaks schema registrations | ||
| Mountpoints cannot connect due to BaseSchema failing to initialize | ||
| Support for Root Resource Discovery is missing | ||
| NetconfMessageTransformer action/rpc empty reply | ||
| Refactor NETCONF transport layer | ||
| Attribute prefix binding warning encountered with RESTCONF | ||
| NETCONF-605 | Support cache refresh without restart of ODL | |
| NETCONF-638 | Termination of NetConf Sessions | |
| Allow SshClient configuration to be tuned by netconf-client users | ||
| NetconfMessageToXmlEncoder can leak sensitive data | ||
| standard edit-config fails when module augmenting base netconf has been retrieved from device | ||
| callhome device with the duplicate ssh host key should be denied | ||
| The ConcurrentModificationException was found in the websocket test in restconf-nb-rfc8040. | ||
| Differentiate authentication failures from other session setup failures | ||
| Eliminate AsyncSshHandlerReader | ||
| Shade mina-sshd | ||
| RFC8040 compliance - wrong URI returns incorrect HTTP status | ||
| Apidoc explorer is not able to list mountpoint content (RFC8040) |
