Attendees:
Please @Please add your name in here:
- Michael Bustamente(AT&T)
- Mark Shostak (AT&T)
- Gergely Csatari (Nokia)
- Karine Sevilla (Orange)
- Toshiyasu Wakayama (Toshi, KDDI)
- @Damian Eagle (Telstra)
Agenda:
- Agenda Bashing
- Updates from Technical Call
- Large Merge between original and new Chapter 7 content on Thursday, please review.
- Review of Open Issues
- https://github.com/cntt-n/CNTT/issues/234 - 234
The following capability concerns security for VIM:
“Capability to validate and verify the integrity of a resources management requests coming from NFVO or VNFM”- Need to follow-up
During Wednesday chapter meeting, we agreed to move this content to chapter 7.
My proposal would be to rename §7.10 “NFVI and VIM vendors responsibility “ to add an item on VIM.
- https://github.com/cntt-n/CNTT/issues/239 - 239
The text included in 7.1 and 7.2 is related to chapter 8 "Compliance, verification and certification". - Need to follow-up
It's a wrong copy paste, it must be clean up
- https://github.com/cntt-n/CNTT/issues/234 - 234
- Chapter Outline discussion
- Do we have the right themes: Platform security, VNF SecurityAcceptance, Workload security?
- Is Workload security inclusive of operator responsibilities?
- Review of Platform Security updates
- Review of VNF Security updates
- Round table
- Call for contributors
Minutes:
Add 7.10 “NFVI and VIM vendors responsibility" to outline
Rewrite introduction paragraph
Open an issue on Chapter 1 - 1.7 VIM - Mark
Platform security - API security
VNF Security Lifecycle - Design & Acceptance criteria
Workload security - Discuss tenant isolation without prescribing topology, API Security
Define more about Platform and Workload Security - Damian (Will review next week)