Hi Don, all, I believe this would be covered under Release requirements, once we define those.
Best regards, Alla From: onap-tsc-bounces at lists.onap.org [mailto:[email protected]] On Behalf Of Don Clarke Sent: Thursday, April 20, 2017 8:48 AM To: Christopher Donley (Chris) <Christopher.Donley at huawei.com>; onap-tsc at lists.onap.org Cc: Ed Warnicke <eaw at cisco.com> Subject: Re: [onap-tsc] Updated TSC Charter Chris, Regulators are concerned about the impact of virtualization on the resilience of critical national infrastructures (they have turned-up at ETSI NFV meetings). Will there be a formalized ONAP process to minimize security vulnerabilities and/or undertake risk analysis in relation to critical components of the platform? I don't see anything in the charter, would these aspects fall under (e.g.) the TSC Responsibility for "defining release quality standards"? I don't think this should be left to individual project teams to figure out. Thanks, Don. From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of Christopher Donley (Chris) Sent: Wednesday, April 19, 2017 9:45 AM To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Cc: Ed Warnicke Subject: [onap-tsc] Updated TSC Charter Dear TSC, On behalf of the Charter drafting team, please find attached an updated version of the TSC Charter incorporating your suggestions and feedback from the last review. We have attempted to highlight the open issues that need a decision from the TSC. We are sending this draft with the intention that you review it in preparation for discussion and voting during our next TSC meeting. Chris, Steve, Ed, Lingli, Alla, and Phil This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170420/a221de6c/attachment.html>
