Attendees:

Please add your name in here:

1. Kelvin Edmison (Nokia)
2. Pankaj Goyal (AT&T)
3. Mark Shostak
4. Al Morton (AT&T)
5. Rabi Abdel (VF)
6. Tomas Fredberg (Ericsson)
7. Ulrich Kleber (Huawei)
8. Karine Sevilla (Orange)
9. Trevor Cooper (Intel)
10. Jisu Park (GSMA)
11. Toshiyasu Wakayama (KDDI)
12. Ahmed El Sawaf ( STC)

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
• Weekly RM meetings are intended to
  
  • Identify owners for new Issues
  • Track open Issues
  • Address technical issues that cannot be resolved online (i.e. resolve stalls)

Agenda:

• Linux Foundation Anti-Trust Policy Notice
• GSMA Anti-Trust Policy Notice
• Agenda bashing
• Review Baldy release priorities 
  • https://wiki.lfnetworking.org/display/LN/CNTT+Baldy
  • identify owners for RM-related work items

• RM Core (status) (Kelvin)
  • Define Backward Compatibility for CNTT
    • Follow-up on any decisions  at TSC level
    • https://github.com/cntt-n/CNTT/issues/1008
  • VNF Evolution Strategy 
    • https://github.com/cntt-n/CNTT/issues/1007
  • CNTT Networking / Generic Fabric Model
    • read-out of meetings in past week
    • https://github.com/cntt-n/CNTT/issues/960 

• RM Ops (status) (Ahmed)
  • Issues

• RM Comp (status) (Victor)
  • TBD

• Open questions
  • TBD

• New Business

Actions:

• General
  •  None at this time
    
•  Core
  • None at this time
• Ops
  • None at this time
• Comp
  • None at this time

Minutes:

• TSC guidance given on backwards compatibility: up to 3 releases, should cover issue 

• Networking/Generic Fabric meeting readout
  • RM has many gaps
  • Need to start with creating normalized terminology
  • need to define gaps and high-level architecture to be included
  • conclusion: have 2 parallel track
    • short-term focused on baldy
    • long-term focused on making it clear how SDN can fit into the reference model

• open discussion on short-term Baldy network deliverables
  • focus on requirements of the workloads for networking (e.g. gaps in workload characterization in chapter 2?)
  • use issue 960 for the discussion
  • create a separate issue for any long-term networking deliverables