...

• Github Issue Review: Candidates for closing
  • https://github.com/cntt-n/CNTT/issues/1251
    • OSS/BSS are explicitly excluded
    • No reference in the diagram to OSS/BSS
  • https://github.com/cntt-n/CNTT/issues/343
    • Use cases no longer in RM (moved to tech document)
  • https://github.com/cntt-n/CNTT/issues/395
    • Is this fully the domain of RI/RC now?
  • https://github.com/cntt-n/CNTT/issues/365, More Operation and LCM Requirement
    • Is this explicitly declared as out-of-scope as per the description in Chapter 01?
    • How to incorporate the feedback from the LCM meeting?
  • https://github.com/cntt-n/CNTT/issues/175 (define extensibility and scalability of profiles)
    • Can this be closed as duplicate of the VNF evolution work?

• Any Other Business
  • Live discussion of  
    • https://github.com/cntt-n/CNTT/pull/1493
    • https://github.com/cntt-n/CNTT/pull/1521

Actions:

Minutes:

• Issue 1251:
  • Decision: Leave open, remove from Baldy, as it was not in the top 5 priorities for the Baldy release.  Move to backlog
• Issue 343: 
  • Decision:   Closing this issue, per @rabi-abdel, as the use cases have moved to the Tech chapter.
• Issue 395: 
  • Decision per meeting 2020-04-29: to leave this discussion to RI/RC meetings where OPNFV engagement is occuring. 
• Issue 365
  • Leave open, remove from Baldy, as it was not in the top 5 priorities for the Baldy release.  Move to backlog
• Issue 175:
  • Close as duplicate of the extensions framework issue, and against the VNF evolution framework issue.
    • Extensions framework pull: https://github.com/cntt-n/CNTT/pull/1354
    • VNF backward evolution: https://github.com/cntt-n/CNTT/issues/1008
    • VNF forward evolution: https://github.com/cntt-n/CNTT/issues/1009