[NETCONF-27] RFC 5539 support Created: 03/Jun/15 Updated: 13/Aug/19 |
|
| Status: | Confirmed |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Anton Ivanov | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
There is no RFC 5539 (Netconf over TLS) support at present. Needed for feature complete implementation. |
| Comments |
| Comment by Maros Marsalek [ 03/Jun/15 ] |
|
Scheduling for Beryllium |
| Comment by Robert Varga [ 13/Nov/15 ] |
|
Move to NETCONFI project. |
| Comment by subhash kumar singh [ 04/Dec/15 ] |
|
Required steps (as per the discussion with Maros): 1. Read RFC in the bug 2. Take a look how NETTY pipeline is constructed for NETCONF (NetconfClientDIspatcher, NetconfServerDispatcher) 3. Take a look at openflowplugin and bgpcep, how they initialize pipeline with TLS support 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) 5. Update the configuration bundle/models for netconf server + southbound 6. Test in the loopback connection (having our server on TLS and having our client on TLS) |