+1 From: Pete Koat Date: 2017-07-13 09:39 To: Xinhui Li CC: [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: Re: [onap-tsc] Vulnerability Management subcommittee (and TSC Action) +1
On Jul 12, 2017 5:55 PM, "Xinhui Li" <[email protected]> wrote: +1 From: <[email protected]> on behalf of Lingli Deng <[email protected]> Date: Thursday, 13 July 2017 at 8:43 AM To: 'Alla Goldner' <[email protected]>, 'Jason Hunt' <[email protected]>, "[email protected]" <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [onap-tsc] Vulnerability Management subcommittee (and TSC Action) +1 Lingli From: [email protected] [mailto:[email protected]] On Behalf Of Alla Goldner Sent: 2017年7月13日 2:50 To: Jason Hunt <[email protected]>; [email protected] Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: Re: [onap-tsc] Vulnerability Management subcommittee (and TSC Action) +1 -------- Original Message -------- Subject: Re: [onap-tsc] Vulnerability Management subcommittee (and TSC Action) From: Jason Hunt <[email protected]> Date: Jul 12, 2017, 7:24 PM To: [email protected] +1 Regards, Jason Hunt Executive Software Architect, IBM Phone: +1-314-749-7422 Email: [email protected] Twitter: @DJHunt ----- Original message ----- From: Stephen Terrill <[email protected]> Sent by: [email protected] To: "[email protected]" <[email protected]> Cc: David Jorm <[email protected]>, "SPATSCHECK, OLIVER \(OLIVER\)" <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: [onap-tsc] Vulnerability Management subcommittee (and TSC Action) Date: Sat, Jul 8, 2017 4:22 PM Hi Fellow TSC members, As indicated in the last TSC meeting I will forward the proposed participants for the vulnerability management sub-committee and who should be on that list. As a reminder, the vulnerability management subcommittee is to handle the reception to resolution of received vulnerabilities according to our agreed procedures: https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management Proposed members Oliver Spatscheck from ATT Amy Zwarico from ATT Ruan He from Orange Arul Nambi from Amdocs This will be supported by: Stephen Terrill (to link with the security subcommittee and coordinator) Phil Robb (link to LF) David Jorm (whom has experience on this from other forum and will phase out when up and running) To: All TSC members, as this is the proposal from the security sub-committee we should decide on whether to accept the proposal or no, my suggestion (unless there is objection to this process) is that a +1/0/-1 via email is an acceptable way forward. (obviously I am +1), so please reply accordingly to formalize this. To: Phil/Casey/Kenny: Once approved, please add the above to the security email list. To: Oliver, Amy, Ruan, Arul. Firstly, thank-you for stepping up. When the confirmation is complete I suggest that you decide who is chair and revert back to the TSC this information for confirmation. To: All PTLs. Just a reminder, support will be needed when processing vulnerabilities. I am sure that we all agree that this will be necessary. Best Regards, Steve. STEPHEN TERRILL Technology Specialist DUIC, Systems and Technology Development Unit IP & Cloud Business Unit, IT & Cloud Products Ericsson Ericsson R&D Center, via de los Poblados 13 28033, Madrid, Spain Phone +34 339 3005 Mobile +34 609 168 515 [email protected] www.ericsson.com Legal entity: Ericsson España S.A, compay registration number ESA288568603. This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer _______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc 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 _______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
