...

• Tom Kivlin
• Satish Verma (Spirent)
• Pankaj Goyal (AT&T)
• Olivier Smith (MATRIXX)
• Rihab Banday (Ericsson)

Agenda and Minutes:

• Antitrust notices
  • Linux Foundation Anti-Trust Policy Notice
  • GSMA Anti-Trust Policy Notice
• Walk-in items
  • Baraque Release Highlights for RA2 (Baraque Release Highlights)
    • RA2 Requirements are relatively stable
    • RA2 Specification is now in a state where it can be used by RI/RC/VI
  • Review current status versus Baraque plan (change freeze starts 14th September):
    • Chapter02 - CNF requirements missing
    • Chapter03 - some sections still missing content (issues have been created to deal with these)
    • Chapter04 - relying on below PRs being completed
    • Chapter05 - relying on issues/1581 being assigned and a PR being created/merged
    • Chapter06 - OK
• Project review
  • Chapter 4 restructuring
    • https://github.com/cntt-n/CNTT/blob/master/doc/ref_arch/kubernetes/chapters/chapter04.md

    • 4.4 Container runtimes - issues/1636 - Satish Verma

      • Presented a slide about the plan
      • The contribution will contain a set of runtimes and their parameters

    • 4.9 Kubernetes workloads - issues/1853 - Gergely Csatari , Taylor Carpenter , Riccardo Gasparetto Stori , Olivier Smith

      • The chapter was originally empty
      • Ch2 level is handled in issues/1496
      • Do we need to move to backlog, or can someone create some content to review in time for 14th September PR merge deadline?
  • https://github.com/cntt-n/CNTT/projects/10
    • Please take the issue without assignee and self assign them
• AOB
• Actions/Next steps
  • Frederick to present a quick NSM intro in one of the future meetings
  • Stale issues - propose we close if in To-do and no PR created after ?? days/weeks/months
    • No objections - Tom Kivlinto create proposal
  • Network specification - Tom Kivlinproposal to replace table 4-5 with a diagram that shows the architecture, with an associated table showing which part of the architecture deals with each requirement.  e.g. I don't think it's relevant that the multiplexer has to provide Network Policies as existing CNI plugins that the multiplexer calls can (and perhaps should) deal with that.   (Do we need a "Unix" principle - "do one thing, well"?)
  • Tom Kivlin to create an issue on the backlog

...