|
We essentially need to separate out individual connection handling into proper RFC6241 stack. Preliminary break down looks something like this:
| RFC6241 figure 1 |
Concern |
Configuration |
Implementations |
Interface towards upper layer |
In scope of this issue |
| Transport |
Establish an authenticated channel |
host, port, authentication handler |
TCP, TLS, SSH |
Netty Channel |
Yes |
| Messages |
Establish and maintain message encoding,
manipulating Netty ChannelPipeline |
HELLO message content |
|
NetconfSession |
Yes |
| Protocol |
Message dispatch |
EXI parameters |
|
NetconfOperation |
No |
| Content |
??? |
|
|
|
No |
This brackets the parts that this issue addresses:
- separation of transport implementation configuration
- separation of channel establishment (note NETCONF-571)
- NetconfSession lifecycle in terms of startup, shutdown and re-establishment
The interface between Messages and Protocol/Content layers (i.e. how we decode XML) is not in scope of this issue and should be addressed separately, once this and NETCONF-571 is addressed.
|