Special Notes:

Each of the three RM sections will get 20 minutes
Given the limited time available, we will focus on identifying issues/actions/next steps, but not solving them right now

...

RM Core (status) (Mark S.)
- StatusEnhancing usability (consistency, completeness, major issues and upgrades)
- Need Issue and volunteer: Determine which caps to eliminate from RMCH-4
- New Content - Container support
- New Content - VNF Design Guidelines Major Issue - HW Profiles and performance- Need Issue and volunteer to own initial content

RM Ops (status) (Ahmed)
- Status
- New Content - OA&M - New MVP Content
  - FM
  - Logging
  - Capacity
  - Provisioning/State (CM)
- LCM - New MVP Content -
  - LCM
  - NFVI scope / areas covered
  - Generic installer model
  - Scope/function/state
  - Node prototypes and creation by installer

...

RM Comp (status) (Victor)
- Status
- Alignment w/ RC on division of responsibility
- Identification and migration of content to RC
- TBD

Open questions
- Should CNTT specify hardware? If so, to what level?
- How to accommodate both homogeneous and heterogeneous server farms?
- Do we need to add a constraints category? (e.g., maximum number of cores you can allocate to a single VNF)
  - For example: | e.nfvi.res.cap.001 | #vCPU | number | Min, Max number of vCPU that can be assigned to a single VNFC | -- Are these Capabilities or Constraints?
- Does the VIM really need its own category of PMs and Caps? (e.g., e.vim.cap.xxx)New Content - Certification and Badging Requirements

Actions:

...