Business Driver

Executive Summary -This feature aims to enhance NETCONF and YANG support in ONAP:

• Support for additional IETF RFCs, including RFC7589 (NETCONF/TLS)
• Support NETCONF-based configuration in certain ONAP use cases, including PNF initial configuration as part of PnP

Business Impact - It provides capabilities which ONAP service providers will find useful for network functions providing a NETCONF interface for configuration management.

Business Markets - These capabilities are generic and can be used for any network function supporting NETCONF.

Funding/Financial Impacts - the development of NETCONF communications from ONAP to xNFs will enable many other use cases which impact OPEX (thus indirectly this U/C saves OPEX).

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Frankfurt Scope

1. Improvements to certificate handling for NETCONF/TLS. For AAF development, there is overlap with other use cases involving external communication to xNFs.
   
2. For Frankfurt, there is also proposal to change the SO PNF workflow to use the new building block approach. This would impact the workflow configuration steps as well. See also PNF PLUG and PLAY in R6 Frankfurt.

Previous Release

R4 Dublin page: 5G - Configuration with NETCONF

Epics

REQ-76 - Getting issue details... STATUS

Project Impact

List of PTLs:Approved Projects

Test Status