+ Kiran Hi Steve, Kiran is working on adding contributors/committers. He is also working with Gildas and LF on seed code approval. I would let Kiran to provide status.
Thanks Srini From: Stephen Terrill [mailto:[email protected]] Sent: Friday, January 12, 2018 1:37 AM To: Addepalli, Srinivasa R <[email protected]>; [email protected]; KOYA, RAMPRASAD <[email protected]> Subject: RE: [onap-tsc] Certificate and Secret Management Project to become subproject of AAF Hi Srini, Ram, Thanks. Then we should quickly bring this back to the TSC for an vote on the updated scope. I hope it can be done by email Looking at the definition though, I have the following comments: https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project - Scope: in the certificate manager, I understood that it can be create certificates, or go through to an external authority. - Update the "architecture" to include the latest (see chris presentation at the last TSC). - I assume Srini that you and your team would be added as contributors at least? BR, Steve From: Addepalli, Srinivasa R [mailto:[email protected]] Sent: 11 January 2018 15:05 To: Stephen Terrill <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [onap-tsc] Certificate and Secret Management Project to become subproject of AAF Scope of AAF is updated to include Secret Management and private key security. Certificate management & Secure communication was already part of the scope. So, in summary, all the scope of CSM is now part of AAF scope. Thanks Srini From: Stephen Terrill [mailto:[email protected]] Sent: Wednesday, January 10, 2018 10:36 PM To: Addepalli, Srinivasa R <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [onap-tsc] Certificate and Secret Management Project to become subproject of AAF Hi Sri, Ram, Thanks for the update - this has been good work. Do we need to update the project scope for AAF, or did RAM consider it within the existing scope? BR, Steve From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Addepalli, Srinivasa R Sent: 11 January 2018 05:25 To: [email protected]<mailto:[email protected]> Subject: [onap-tsc] Certificate and Secret Management Project to become subproject of AAF We (Intel and TM) have proposed 'Certificate and Secret Management (CSM)' as a separate project for Beijing release. Details are here: https://wiki.onap.org/pages/viewpage.action?pageId=16008548. Both architecture subcommittee and security subcommittee recommended us to make it part of AAF for following reasons: - Contain projects explosion. - Consolidate all security services in one project. - Why AAF? - AAF is already providing authentication and authorization services. Based on recommendation, we have approached AAF team. AAF team (thanks to Ram, Jonathan, Sai and Sunil) accepted it to be part of AAF for Beijing release. All the scope of CSM is accepted by AAF team including certificate management, secret management, HW key protection and Mutual TLS among ONAP services. With this, we will remove CSM from the "Proposed Projects" and put it under AAF. Please do let us know if there are any questions. Thanks Intel & TM team (Original proposers of CSM)
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
