https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-27 netconf <p>There is no RFC 5539 (Netconf over TLS) support at present. Needed for feature complete implementation.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-27

RFC 5539 support

New Feature Confirmed Unresolved Unassigned Anton Ivanov Wed, 3 Jun 2015 06:20:19 +0000 Tue, 13 Aug 2019 07:38:39 +0000 netconf 0 6 <p>Scheduling for Beryllium</p> <p>Move to NETCONFI project.</p> <p>Required steps (as per the discussion with Maros):</p> <p>1. Read RFC in the bug</p> <p>2. Take a look how NETTY pipeline is constructed for NETCONF (NetconfClientDIspatcher, NetconfServerDispatcher)</p> <p>3. Take a look at openflowplugin and bgpcep, how they initialize pipeline with TLS support</p> <p>4. Do the same for our Dispatchers (probably new method would have to be introduced because if I recall, we have something like createSSHClient, createTcpServer etc.... or we have that in a DTO)</p> <p>5. Update the configuration bundle/models for netconf server + southbound<br/> to have TLS in addition to SSH and TCP there for server, we might have to develop a simple proxy server just with TLS inside (the same we do for netconf in netconf-ssh bundle)</p> <p>6. Test in the loopback connection (having our server on TLS and having our client on TLS)</p> Development External issue ID 3554 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01w07: