Recording Policies:

• https://zoom.us/rec/play/uMAuIuyoqG43EtWS4QSDAf4oW9XsKP2s1CQW-fYNzxu3VSIGN1L3Z7YSNOX-H7MYUyogBuINABoVavXq?autoplay=true&startTime=1589371628000

Recording:

• https://zoom.us/rec/play/uJN5Jb2qpj43T9Od5gSDUPB4W9S9eKys03Ufr_sKyEyyAiZRMFKmY-QVa-P18Esz3_IGbSIHAFcb3tcX?autoplay=true&startTime=1591790988000

Anti-Trust Policies:

• LFN Anti-Trust Policy Notice

• GSMA Anti-Trust Policy Notice

Walk-in Items.

• • FMO slides to LFN Board.

    • slides presented by ... . more discussion will occur during FMO.

    • final slides will be presented to LFN Gov Board on 17th June.

  • ODIM presentation.

    • Presentation will be on 16th.

    • send invite to cntt-tech-steering, rm, ra-1, ra2.

  • RM Lead position.

    • ... to lead with support from ...

    • cleanup work needed (feedback received from GSMA by Tom)

      • Will be attached here.

      • to be discuss in RM meeting next.

  • ReadTheDocs (https://cntt-test.readthedocs.io/en/latest/) ...

    • ... will continue investigating with readthedocs.

Technical Steering Topics

• RC-1/RC-2 Joint Spec. ...

  • CNTT RC1 and CNTT RC2 must implement the same test case execution requirements for a smooth overall integration and common playbooks and outputs (conforming with users needs including OVP)

  • In addition to the common methodology/terms, the following points already part of RC1 should be factorized in a common chapter:
    
    

    • CNTT RI and RC toolchains (https://github.com/cntt-n/CNTT/blob/master/doc/ref_cert/lfn/chapters/chapter02.md#211-cntt-ri-and-rc-toolchains)

    • Test case integration requirements (https://github.com/cntt-n/CNTT/blob/master/doc/ref_cert/lfn/chapters/chapter02.md#2.7.2)

    • Testing Cookbook (https://github.com/cntt-n/CNTT/blob/master/doc/ref_cert/lfn/chapters/chapter04.md#43-nfvi-testing-cookbook)

  • All test case selection for RC2 is blocked until a decison is made (duplicating is a falsy alternative)

  • ... ... ... ...  ... ... (add your name if you are interested)

  • ... : linking it to FMO is false from a technical state point. FMO doesn't currently change RC scope and content. It's not a revolution at least from a RC pov.

  • ... : we don't share the same mindsets about FMO (e.g. short vs long term views) and we are not at the same stage:

    • integrating test case in RC2 is urgent at least for one CNTT actor

    • FMO can be interpreted as very minor changes regarding the existing work.

• Webinars & Blogs

  • Edge: July 23rd.

  • NFG: ... please fill in: https://docs.google.com/forms/d/e/1FAIpQLSfH5iJV9vXJ_RRuMMUQd171YH1T2RGjAmmFf2Gp4E3WR19jFw/viewform

  • RC-1: ... please fill in https://docs.google.com/forms/d/e/1FAIpQLSfH5iJV9vXJ_RRuMMUQd171YH1T2RGjAmmFf2Gp4E3WR19jFw/viewform

• vF2F:

  • schedule identified will be presented.

• ONES NA:

  • it is official now that this will be virtual.

• Open Dev Summit 

  • https://www.openstack.org/events/opendev-2020

Review Current AI.

Updates from Officers Items:

• Chief Technical Editor:

• ONAP Technical Coordinator: 

• OPNFV Technical Coordinator:

• CNCF Technical Coordinator: 

• CVC Technical Coordinator: 

• Automation and Tooling:

• ONF: Open Networking Foundation.

• ETSI: