Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Risk identifiedMitigation PlanContingency Plan

CMP interface integration requested, but to date, no pre-built CMP Java libraries have been identified.

If no existing CMP Java client exists that can be used, then we will have to build the API from scratch, which will take time and resources which are in short supply.

We have put the CMP as something we will work on, but cannot commit to.

This means it will not likely to be ready in Dublin, but may be ready in El Alto.


There is no contingency plan for the combination of lack of Java Library and lack of time to write the API from scratch . As a Stretch Goal, we can work on this during Dublin after commitments, in hopes of committing for El Alto.


Explanation: Since AAF Certman would be functioning as intermediate to the Certificate Authority, that CA must exist and be deployed in ONAP before serious work can begin.

We cannot commit to anything that is not testable

There is no way to compensate for lack of CMP based CA. Until this is ready, CMP

Stretch Goal

Access cannot be tested, and therefore, cannot be done. If ONAP works on obtaining

,

and running a CMP based CA in Dublin, then there might be a good chance of committing for El Alto.

  • Resources

Fill out AAF Resources centralized page.

...