Uploaded image for project: 'netconf'
  1. netconf
  2. NETCONF-590

Refactor NETCONF transport layer

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: High High
    • 7.0.0
    • None
    • netconf

      As a legacy of pre-callhome and protocol-framework world, we have no separation between network-level roles (i.e. session initiation client/server) and NETCONF-level roles (i.e. NETCONF client/server).

      This leads to quite a bit of duplication between netconf-netty-util, callhome-protocol and netconf-{tcp,ssh}, where we have separate netty dispatchers and client/server handling - even though the only difference is who is initiating the network channel – this is detailed in https://tools.ietf.org/html/rfc8071#section-2 . In the context of  Figure 1 there, our technology stack has further complication, because we rely on Apache SSH to handle SSH protocol details and we only attach to the NETCONF channel – which is subject of NETCONF-571.

      Refactor the four components to cleanly separate the connection initiation from other session establishment concerns (authentication and NETCONF negotiation).

        1.
        		 Convert NETCONF server-side to transport-api Sub-task Resolved Ruslan Kashapov
        2.
        		 Convert NETCONF client-side to transport-api Sub-task Resolved Ruslan Kashapov
        3.
        		 Convert Callhome-{protocol, provider} to transport-api Sub-task Resolved Ruslan Kashapov
        4.
        		 Refactor SslHandlerFactory Sub-task Resolved Robert Varga
        5.
        		 Refactor ClientFactoryManagerConfigurator Sub-task Confirmed Unassigned
        6.
        		 HTTP transport implementation Sub-task Resolved Ruslan Kashapov

            rkashapov Ruslan Kashapov
            rovarga Robert Varga
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: