...
Use Case Overview & Description
(description of U/CThe Certificate Management Protocol (CMP) is an Internet protocol used for obtaining X.509 digital certificates in a public key infrastructure (PKI). It is described in RFC 4210 and is one of two protocols so far to use the Certificate Request Message Format (CRMF), described in RFC 4211, with the other protocol being Certificate Management over CMS (CMC), described in RFC 5273. An obsolete version of CMP is described in RFC 2510, the respective CRMF version in RFC 2511. CMP messages are encoded in ASN.1, using the DER method and usually transported over HTTP. CMP (Certificate Management Protocol) Server & Client (completed in R6)
Use Case Key Information
| TOPIC | DESCRIPTION | WIKI PAGE | ||||||||
| Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee |
| ||||||||
| Architecture S/C info | Information on the Architecture sub-committee presentation |
| ||||||||
| Architecture Review Presentation made | ||||||||||
| Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |||||||||
| Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case | |||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: @xyz Pawel Baniewski USE KEY CONTACTS: | |||||||||
| Meetings Register & Recordings | Link to Use Case Team meetings. |
...
This section describes Business Drivers needs. These business drivers are presented on the Requirements Sub-committee and should also be put into the release requirements sub-committee page.
Executive Summary - The CMPv2 work in R8 will develop (1) Integration with Cert- (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")
Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").
Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").
Manager (certificate enrollment solution recommended by OOM) and (2) DCAE further integration (expected to be completed by R7 bug fixes). This requirement improves ONAP Security with CMPv2. CMP is used by multiple operations including Plug and Play, and NetConf operation. In R6 CMPv2 Certificate Service and basic development was implemented. Integration with server & client to the certificate service was completed. There are also two ONAP bordering component that were integrated with the certificate service with interfaces to SDN-C and DCAE. See the REQ-431: https://jira.onap.org/browse/REQ-431?src=confmacro
Business Impact - The enhancement to CMPv2 operation will improve security management within ONAP and affects multiple ONAP functions and use cases, including Plug and Play (PNF registration) and NetConf. As with all security functionality within ONAP, Security is a fundamental aspect of FCAPS, being the "S" for security management.
Business Markets - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.
Funding/Financial Impacts - Potential OPEX savings with enhanced security to prevent breaches and prevent security compromisesFunding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case).
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): 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. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
Development Status
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK | |||
| DCAE | |||
| DMaaP | |||
| External API | |||
| HOLMES | |||
| MODELING | |||
Multi-VIM / Cloud | |||
| OOF | |||
| OOM | |||
| POLICY | |||
| PORTAL | |||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | |||
| VF-C | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS |
...
*Each Requirement should be tracked by its own User Story in JIRA
USE CASE DIAGRAM
...