...

1. All the members continuing to test Guilin functionality are requested to update Track-wise test cases regularly for the remaining P2 test cases. Any bugs that will be reported will be solved in the Master branch, and may become part of Guilin Maintenance and/or Honolulu release. We will update the details in the wiki.
2. Details of Honolulu priority topics for our use case, and company commitments are documented in Honolulu Requirements.
3. All participating companies are requested to contribute to at least 1 Global Requirement (earlier NFR) - it can be in the same component(s) they are contributing to.
4. For considering resource occupancy level/capacity for NSI/NSSI selection, details of the proposal will be documented in E2E Network Slicing.
5. For using CPS to persist RAN configuration data related to our use case, the approach outlined for SON in SON_Normalization.pptx can be followed.  Config DB API details can be found at Config DB#APIDocumentation. The presentation given by CPS team on the basic concepts is available at CPS concepts. AP: Our team should review and bring up any concerns/queries for discussion with the CPS team during next week.
6. We propose to organize 2 demos in Jan:
   1. E2E use case demo: It can be in an LFN vF2F event if it happens in Jan or Feb, otherwise, we will request for a slot in the Use Case Realization meetings (Wed).
   2. RAN Slicing demo: This will be mainly to showcase the interoperability with O-RAN NFs, and demonstrate RAN Slicing functionality. O-RAN folks will also be invited for this.

Recording