...

...

2024-

...

04-23

Recording: TODO zoom link

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on (end of I release)
      1. TODO
      2022-09-13  We did not check this this time.
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 20222023-05-27. 2022-08-30, 2022-09-13:12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. 2022-09-13: TODO
   2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   3. RIC-915 dms_cli for installing xapp not working (raised by James)
   4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   6. RIC-897 SCTP connection fails with Viavi // update with workaround
   7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   8. RIC-894 long idle period (days) causes RMR connection breaks
   9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   12. RIC-837 RMR is not forwarding messages from E2T to E2M
   13. RIC-835 → 2021-12-07 news from Viktor
   14. fixed: no new fixes.
       
   15. anybody would like to get more familiar with RMR?
   Sunil still to discuss with other team members for other items from subteam-hOther tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
   Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05& 2022-07-19 update:  - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
   
4. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
5. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
6. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
7. 2022-04-26: still open
8. 2022-05-11: expecting to finalize by May-27
9. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
10. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
11. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
12. 2022-08-02: SUNIL SINGH to check any news on RIC-860 or RIC-878?
13. 2022-08-16→2022-08-30->2022-09-13:
14. : some cleanup is needed first.
    
    1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
    2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
    3. test both if they are actually working
    4. 2022-08-30: team currently busy, but will pick up on this again soon
15. 2022-08-30: contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
    1. 2022-09-13: news?
16. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
    1. 2022-04-12
       1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
       2. actual workshop planned for RSAC on Apr-21 9am EDT.
       3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
    2. 2022-04-26
       1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
          
       2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
    3. 2022-05-11:
       1. Currently in the hands of OTF team (Alex)
       2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
          1. 2022-05-30: Thoralf comment in RIC-915
             
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
       
    5. 2022-07-19: James is working on it with LF
       
    6. 2022-08-02: any updates?
       
       1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
       2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
       
    8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
       
    9. 2022-09-13: news?
17. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
    
    1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
    2. 2022-06-21
       1. RIC-642 (python) done
       2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
       
    6. 2022-08-16: any news?
       
       1. one optinion is to cleanup CI first with the approach in RIC-912
       2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
    7. 2022-08-30  Waiting for Any Nguyen to come fully back to work.
       
    8. 2022-09-13: news?
18. 2022-07-05: still one remaining demos.
    
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
19. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
       1. Sprint G release dev sprint 1: Aug-22 to Sep-11
       2. Sprint G release dev sprint 2: Sep-12 to Oct-2
       3. Sprint G release dev sprint 3: Oct-3 to Oct-23
       4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
       5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
20. GRPC vs RMR
    1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
    2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
    3. need to look at Mavenir E2SM-RC proposal.
    4. impact on xapp frameworks will happen as well.
    5. Alexandre mentioned option of using QUIC (grpc over QUIC).
    6. Thoralf to schedule a meeting once a proposal is ready.
    7. 2022-08-16 →2022-08-30 → 2022-09-13: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
21. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
    
    1. 2022-08-30: Subhash presented the results of the discussion - material is here https://wiki.o-ran-sc.org/display/RICP/E2AP+2.0+Design 
22. In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
    1. 2022-09-13: likely the way we go forward
       
23. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
       1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
          
       2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
24. 2022-09-13: Joseph Thaliath to present plans of OSC AI/ML subproject
25. RICAPP agenda: RICAPP Meetings.

2022-08-30 (Tuesday)

Recording: link to zoom recording

...

1. 2022-08-30  We did not check this this time.

...

1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. 2022-08-30 we did not do this this time

...

1. 2022-08-30: TODO
2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
3. RIC-915 dms_cli for installing xapp not working (raised by James)
4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
6. RIC-897 SCTP connection fails with Viavi // update with workaround
7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
8. RIC-894 long idle period (days) causes RMR connection breaks
9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    1. 2021-12-21: Trying to get bandwidth for this during F release.
12. RIC-837 RMR is not forwarding messages from E2T to E2M
13. RIC-835 → 2021-12-07 news from Viktor
14. fixed: no new fixes.
    
15. anybody would like to get more familiar with RMR?

...

1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
3. test both if they are actually working
4. 2022-08-30: team currently busy, but will pick up on this again soon

...

1. 2022-04-12
   1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
   2. actual workshop planned for RSAC on Apr-21 9am EDT.
   3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
   1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
      
   2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
   1. Currently in the hands of OTF team (Alex)
   2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
      1. 2022-05-30: Thoralf comment in RIC-915
         
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
   
5. 2022-07-19: James is working on it with LF
   
6. 2022-08-02: any updates?
   
   1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
   2. James working Sridhar on xTesting.
7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
   
8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
   

...

1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
   1. RIC-642 (python) done
   2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
   
6. 2022-08-16: any news?
   
   1. one optinion is to cleanup CI first with the approach in RIC-912
   2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
7. 2022-08-30  Waiting for Any Nguyen to come fully back to work.
   

...

1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)

...

1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
   1. Sprint G release dev sprint 1: Aug-22 to Sep-11
   2. Sprint G release dev sprint 2: Sep-12 to Oct-2
   3. Sprint G release dev sprint 3: Oct-3 to Oct-23
   4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
   5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)

...

1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to schedule a meeting once a proposal is ready.
7. 2022-08-16 →2022-08-30 no news yet

...

1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
3. Thoralf to schedule another meeting end of May (after F).
4. 2022-06-07: Thoralf will schedule a meeting for week after next week
5. 2022-06-21→2022-07-05: This has to wait for end of July
6. 2022-08-02: meeting scheduled for 2022-08-04
7. 2022-08-30: Subhash presented the results of the discussion - material is here https://wiki.o-ran-sc.org/display/RICP/E2AP+2.0+Design 

...

1. 2022-08-02
   1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      
   2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429

...

1. 1. RIC-1057 gNB unable to connect during high amount of Subscription Requests
   2. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests
   3. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
   4. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation
   5. RIC-1052 Not able to install k8s and helm with Existing Ric installation shell script in document - Done, still some issues are seen, to further check and report issue.
   6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   7. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil, duplicate of 1052(DONE)
      
   8. RIC-1047 crash in E2T metric increment code - WIP
   9. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   10. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   11. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP
   12. RIC-1042 Can't register xApp
   13. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation - Mostly fixed, To be confirmed by Abhijit.
   14. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   15. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   16. RIC-1025 memory leak in routing manager
   17. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   18. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   19. RIC-1015 e2t too High default message size. → Nokia

   20. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   21. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   22. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   23. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   24. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   25. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   26. RIC-915 dms_cli for installing xapp not working (raised by James)
   27. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   28. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   29. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   30. RIC-894 long idle period (days) causes RMR connection breaks
   31. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   32. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   33. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   34. RIC-837 RMR is not forwarding messages from E2T to E2M
   35. RIC-835 → 2021-12-07 no news from Viktor
   36. fixed: 
       
2. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
   6. 2024-03-26: Unavailable today.
   7. 2024-04-23:
3. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23: no news
4. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
   9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
      
   10. 2024-03-09: Absent
   11. 2024-04-23: Not much updates.
       
5. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
   5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
   6. 2024-03-09,2024-04-23: Not available
6. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
   5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
   6. 2024-03-09: Not available.
      
   7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
7. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
   3. 2024-03-26,2024-03-09,2024-04-23: unavailable.
8. Himanshu (subteam-gs) would like to work on RIC-963
   
   1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
   2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
   3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
   4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
   5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
   6. 2024-04-23: Not present
9. Dhiraj (subteam-r)
   
   1. 2023-12-05: moved the IPv6 item  to J release
   2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
   3. 2024-01-26,2024-04-09,2024-04-23: no news.
10. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
11. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
12. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
13. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link,  to include k8s version upgrade, clean up of pending issues.
14. 1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
       1. Sprint J release dev sprint 1: Feb-19 to Mar-10
       2. Sprint J release dev sprint 2: Mar-11 to Mar-31
       3. Sprint J release dev sprint 3: Apr-1 to Apr-21
       4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
       5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
15. RICAPP agenda: RICAPP Meetings.

2024-04-09

Recording: near_rt_ric_09_04-2024.mp4

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on (end of I release)
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1057 gNB unable to connect during high amount of Subscription Requests
   2. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests
   3. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
   4. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation
   5. RIC-1052 Not able to install k8s and helm with Existing Ric installation shell script in document
   6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   7. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil
   8. RIC-1047 crash in E2T metric increment code 
   9. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   10. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   11. RIC-1043 Crash in E2T buildPrometheusList Function 
   12. RIC-1042 Can't register xApp
   13. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   14. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   15. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   16. RIC-1025 memory leak in routing manager
   17. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   18. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   19. RIC-1015 e2t too High default message size. → Nokia

   20. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   21. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   22. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   23. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   24. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   25. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   26. RIC-915 dms_cli for installing xapp not working (raised by James)
   27. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   28. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   29. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   30. RIC-894 long idle period (days) causes RMR connection breaks
   31. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   32. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   33. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   34. RIC-837 RMR is not forwarding messages from E2T to E2M
   35. RIC-835 → 2021-12-07 no news from Viktor
   36. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
   6. 2024-03-26: Unavailable today.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09: no news
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
   9. 2024-03-26: Working on RIC-1049, documentation will also be made.
   10. 2024-03-09: Absent
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
   5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
   6. 2024-03-09: Not available
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:

2022-08-16 (Tuesday)

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/8824 → OK, as only new swagger yaml file for which nothing is implemented yet.
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on May-27-2022. 2022-08-16 we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. 2022-08-16: TODO
   2. RIC-936 change from gcr.io → ghcr.io in master and f-release DONE
   3. RIC-935 flannel namespace change. fixed in master and f-release DONE
   4. RIC-921 fix UT test case in e2mgr to stub time (leftover from review
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/
      e2mgr
      1. ric-dep/+/
      8493)
   5. RIC-915 dms_cli for installing xapp not working (raised by James)
   6. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   7. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   8. RIC-897 SCTP connection fails with Viavi // update with workaround
   9. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   10. RIC-894 long idle period (days) causes RMR connection breaks
   11. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   12. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   13. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   14. RIC-837 RMR is not forwarding messages from E2T to E2M
   15. RIC-835 → 2021-12-07 news from Viktor
   16. fixed: RIC-935, RIC-936
       
   17. anybody would like to get more familiar with RMR?
   Sunil still to discuss with other team members for other items from subteam-hOther tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
   Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05& 2022-07-19 update:  - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
   
4. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
5. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
6. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
7. 2022-04-26: still open
8. 2022-05-11: expecting to finalize by May-27
9. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
10. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
11. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
12. 2022-08-02: SUNIL SINGH to check any news on RIC-860 or RIC-878?
13. 2022-08-16: some cleanup is needed first.
    
    1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
    2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
    3. test both if they are actually working
14. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
    1. 2022-04-12
       1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
       2. actual workshop planned for RSAC on Apr-21 9am EDT.
       3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
    2. 2022-04-26
       1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
          
       2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
    3. 2022-05-11:
       1. Currently in the hands of OTF team (Alex)
       2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
          1. 2022-05-30: Thoralf comment in RIC-915
             
    4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
       
    5. 2022-07-19: James is working on it with LF
       
    6. 2022-08-02: any updates?
       
       1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
       2. James working Sridhar on xTesting.
    7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
       
15. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
    
    1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
    2. 2022-06-21
       1. RIC-642 (python) done
       2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
    5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
       
    6. 2022-08-16: any news?
       
       1. one optinion is to cleanup CI first with the approach in RIC-912
       2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
16. 2022-07-05: still one remaining demos.
    
    1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August → (update 2022-08-16) middle of Sept (Erkki)
17. G release content planning
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
       1. Sprint G release dev sprint 1: Aug-22 to Sep-11
       2. Sprint G release dev sprint 2: Sep-12 to Oct-2
       3. Sprint G release dev sprint 3: Oct-3 to Oct-23
       4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
       5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
18. GRPC vs RMR
    1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
    2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
    3. need to look at Mavenir E2SM-RC proposal.
    4. impact on xapp frameworks will happen as well.
    5. Alexandre mentioned option of using QUIC (grpc over QUIC).
    6. Thoralf to schedule a meeting once a proposal is ready.
    7. 2022-08-16 no news yet
19. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST -> 2022-08-04
    
    1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
    2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
    3. Thoralf to schedule another meeting end of May (after F).
    4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    5. 2022-06-21→2022-07-05: This has to wait for end of July
    6. 2022-08-02: meeting scheduled for 2022-08-04
    7. 2022-08-16: Subhash to present results of discussion in next meeting on 2022-08-30
       
20. RUST as a language for xApps and framework. Will take this in the details in next meeting.
    1. 2022-08-02
       1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
          
       2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
    2. 2022-08-16: repo is now created ->Closed
21. RICAPP agenda: RICAPP Meetings.

2022-08-02 (Tuesday)

Recording: link to zoom recording

...

1. 2022-08-02: no large commits
   

...

1. We take a look at the two links in the beginning of this page: Code coverage reports..
2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
3. Thoralf did this last on May-27-2022. 2022-08-02 we did not do this this time

...

1. 2022-08-02: no new bugs, no new fixes
2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
6. RIC-897 SCTP connection fails with Viavi // update with workaround
7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
8. RIC-894 long idle period (days) causes RMR connection breaks
9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    1. 2021-12-21: Trying to get bandwidth for this during F release.
12. RIC-837 RMR is not forwarding messages from E2T to E2M
13. RIC-835 → 2021-12-07 news from Viktor
14. fixed:no new fixes
    
15. anybody would like to get more familiar with RMR?

...

1. 2022-04-12
   1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
   2. actual workshop planned for RSAC on Apr-21 9am EDT.
   3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
2. 2022-04-26
   1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
      
   2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
3. 2022-05-11:
   1. Currently in the hands of OTF team (Alex)
   2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
      1. 2022-05-30: Thoralf comment in RIC-915
         
4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
   
5. 2022-07-19: James is working on it with LF
   
6. 2022-08-02: any updates?
   
   1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
   2. James working Sridhar on xTesting.

1. 1. 1. 11743 → to be merged by Thoralf Czichy 
         
      2. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      3. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
   5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
   6. 2024-03-09: Not available.
      
2. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
   3. 2024-03-26,2024-03-09: unavailable.
3. Himanshu (subteam-gs) would like to work on RIC-963
   
   1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
   2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
   3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
   4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
   5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
4. Dhiraj (subteam-r)
   
   1. 2023-12-05: moved the IPv6 item  to J release
   2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
   3. 2024-01-26,2024-04-09: no news.
5. Alexandre (subteam-utfpr)
   
   1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
   2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
   3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
   4. 2024-03-26,2024-04-09: No news.
6. Nokia (subteam-n)
   1. RIC-997 postponed to J
   2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
7. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
   1. 2024-03-26: New nomination awaited from TOC.
   2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
8. J release
   
   1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
         1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
   2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
   3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
         
      2. committed items only: all teams (committed) and all teams (committed + tentative).
         
      3. items that are known to require work, but are currently not in J release: link
9. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
10. RICAPP agenda: RICAPP Meetings.

2024-03-26

Recording:  link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on (end of I release)
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   2. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil
   3. RIC-1047 crash in E2T metric increment code 
   4. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   5. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   6. RIC-1043 Crash in E2T buildPrometheusList Function 
   7. RIC-1042 Can't register xApp
   8. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   9. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   10. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   11. RIC-1025 memory leak in routing manager
   12. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   13. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   14. RIC-1015 e2t too High default message size. → Nokia

   15. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   16. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   17. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   18. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   19. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   20. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   21. RIC-915 dms_cli for installing xapp not working (raised by James)
   22. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   23. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   24. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   25. RIC-894 long idle period (days) causes RMR connection breaks
   26. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   27. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   28. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   29. RIC-837 RMR is not forwarding messages from E2T to E2M
   30. RIC-835 → 2021-12-07 no news from Viktor
   31. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
   6. 2024-03-26: Unavailable today.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12,2024-03-26: no news
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
   9. 2024-03-26: Working on RIC-1049, documentation will also be made.
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
   5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
   5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
9. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
   3. 2024-03-26: unavailable.
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26: no news.
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26: No news.
13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
15. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-03-12

Recording:  link to zoom meeting

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on (end of I release)
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04
   2. RIC-1047 crash in E2T metric increment code 
   3. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   4. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   5. RIC-1043 Crash in E2T buildPrometheusList Function 
   6. RIC-1042 Can't register xApp
   7. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   8. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   9. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   10. RIC-1025 memory leak in routing manager
   11. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   12. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   13. RIC-1015 e2t too High default message size. → Nokia

   14. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   15. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   16. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   17. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   18. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   19. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   20. RIC-915 dms_cli for installing xapp not working (raised by James)
   21. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   22. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   23. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   24. RIC-894 long idle period (days) causes RMR connection breaks
   25. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   26. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   27. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   28. RIC-837 RMR is not forwarding messages from E2T to E2M
   29. RIC-835 → 2021-12-07 no news from Viktor
   30. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12: no news
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
9. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr.Good to raise JIRA.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
15. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-02-13

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on (end of I release)
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. new RIC-1047 crash in E2T metric increment code 
   2. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   3. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   4. RIC-1043 Crash in E2T buildPrometheusList Function 
   5. RIC-1042 Can't register xApp
   6. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   7. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   8. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   9. RIC-1025 memory leak in routing manager
   10. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   11. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   12. RIC-1015 e2t too High default message size. → Nokia

   13. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   14. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   15. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   16. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   17. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   18. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   19. RIC-915 dms_cli for installing xapp not working (raised by James)
   20. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   21. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   22. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   23. RIC-894 long idle period (days) causes RMR connection breaks
   24. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   25. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   26. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   27. RIC-837 RMR is not forwarding messages from E2T to E2M
   28. RIC-835 → 2021-12-07 no news from Viktor
   29. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13: no news
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
9. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over teh next weeks.
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
14. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-01-30

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix 
   2. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr 
   3. RIC-1043 Crash in E2T buildPrometheusList Function 
   4. RIC-1042 Can't register xApp
   5. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   6. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   7. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   8. RIC-1025 memory leak in routing manager
   9. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   10. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   11. RIC-1015 e2t too High default message size. → Nokia

   12. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   13. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   14. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   15. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   16. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   17. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   18. RIC-915 dms_cli for installing xapp not working (raised by James)
   19. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   20. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   21. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   22. RIC-894 long idle period (days) causes RMR connection breaks
   23. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   24. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   25. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   26. RIC-837 RMR is not forwarding messages from E2T to E2M
   27. RIC-835 → 2021-12-07 no news from Viktor
   28. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
7. Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30: no news
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
9. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be commited now obtained. IPv6-related commits expected over teh next weeks.
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. RIC-997 postponed to J
14. J release
    
    1. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
    2. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-01-16

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   2. RIC-1031Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   3. RIC-1032 → RIC-1035 - we cpontinue with this under RIC-1035 (discussed with Abhijit in the project meeting)
   4. RIC-1025 memory leak in routing manager
   5. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   6. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   7. RIC-1015 e2t too High default message size. → Nokia

   8. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   9. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   10. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   11. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look
   12. RIC-991 CVE-2023-40997 RMR related (not a duplicate) - Alexandre will take a look → DONE
   13. RIC-989 CVE-2023-40998 RMR (minor) security issue - Alexandre will take a look → DONE
   14. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   15. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   16. RIC-915 dms_cli for installing xapp not working (raised by James)
   17. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   18. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   19. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   20. RIC-894 long idle period (days) causes RMR connection breaks
   21. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   22. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   23. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   24. RIC-837 RMR is not forwarding messages from E2T to E2M
   25. RIC-835 → 2021-12-07 no news from Viktor
   26. fixed: RIC-991, RIC-989
       
4. James: updates?
   1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
   2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
   5. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   6. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-29: no news, other than Naman working on the operator implementation.
   2. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
         1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
   3. 2023-09-26:
      
      1. kubernetes operator new repo needed or not?
         1. xapp deployment → appmgr or ricdms
         2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
   5. 2023-11-21:
      1. k8s operator commits - needs to be finalized.
   6. 2023-12-05: Naman gave an update on status of Samsung items
   7. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16 No news.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

      1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

      2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.

      3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".

...

1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
2. 2022-06-21
   1. RIC-642 (python) done
   2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
4. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
5. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
   

...

1. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)

...

1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
2. Sprint dates
   1. Sprint G release dev sprint 1: Aug-22 to Sep-11
   2. Sprint G release dev sprint 2: Sep-12 to Oct-2
   3. Sprint G release dev sprint 3: Oct-3 to Oct-23
   4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
   5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)

...

1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
3. need to look at Mavenir E2SM-RC proposal.
4. impact on xapp frameworks will happen as well.
5. Alexandre mentioned option of using QUIC (grpc over QUIC).
6. Thoralf to scheduke a meeting once a proposal is ready.

...

1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
3. Thoralf to schedule another meeting end of May (after F).
4. 2022-06-07: Thoralf will schedule a meeting for week after next week
5. 2022-06-21→2022-07-05: This has to wait for end of July
6. 2022-08-02: meeting scheduled for 2022-08-04
   

...

1. 2022-07-19 no news
2. 2022-08-02 → move to bug sections (Thoralf added this as comment to RIC-894)

...

1. 2022-08-02
   1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
      
   2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429

...

2022-07-19 (Tuesday)

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).2022-07-19:
   we did not do this this time
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on May-27-2022. 2022-07-19 we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. 2022-07-19: we did not check this this time.
   2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
   4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   6. RIC-897 SCTP connection fails with Viavi // update with workaround
   7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   8. RIC-894 long idle period (days) causes RMR connection breaks
   9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   12. RIC-837 RMR is not forwarding messages from E2T to E2M
   13. RIC-835 → 2021-12-07 news from Viktor
   14. fixed:no new fixes
       
   15. anybody would like to get more familiar with RMR?
Sunil still to discuss with other team members for other items from subteam-hOther tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05& 2022-07-19 update:  - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)

4. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
5. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
6. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
7. 2022-04-26: still open
8. 2022-05-11: expecting to finalize by May-27
9. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
10. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
11. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
12. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
    1. 2022-04-12
       1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
       2. actual workshop planned for RSAC on Apr-21 9am EDT.
       3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
    2. 2022-04-26
       1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
          
       2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
    3. 2022-05-11:
       1. Currently in the hands of OTF team (Alex)
       2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
          1. 2022-05-30: Thoralf comment in RIC-915
             
    4. 2022-06-21: XTesting proposed as alternative to OTF
    5. 2022-07-19: James is workin on it with LF
       
13. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
    
    1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
    2022-06-21
    2. RIC-642 (python) done
    RIC-705 and RIC-641 being worked on by Anh Nguyen:
    3. 2023-11-07: addressing review comments of
    4. https://gerrit.o-ran-sc.org/r/c/ric-plt/
    xapp-frame-cpp
    5. submgr/+/
    8561
    6. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
    7. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
14. 2022-07-05: still two remaining demos.
    
    1.  2022-07-19: RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Shobha)
       1. new function in https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/nodeb-rnib.git;a=blob;f=reader/rNibReader.go -> GetRanFunctionDefinition()
       2. C version via creader (see https://packagecloud.io/o-ran-sc/release/packages/debian/stretch/rnib_1.2.5_all.deb)
       3. play video "RIC_888.mp4" from tmp folder (remember ... → "share sound")
    2. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
       
    3. 2022-07-19: Thoralf uploaded demo on deploying RIC, connecting the simulator project's E2 (node) simulator, Nokia simulator and deploy the hw-go xapp as well: 2022-05-24 Release F
15. F release wrap up
    1. 2022-07-05 & 2022-07-19: F release. See demo page: Release criteria checklist - Release F, Near-RT RIC (F release) = image list, F Release = summary, 2022-05-24 Release F = demos.
G release content planning
16. 1. 11681 tomorrow. Then we should be able to merge this.
    2. 2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    3. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    4. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
17. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be commited now obtained. IPv6-related commits expected over teh next weeks.
18. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
19. Nokia (subteam-n)
    1. RIC-997 postponed to J
20. J release
    
    1. We
we
21. 1. mark items that you are >90% sure (=”committed”) to work on during
2H2022
22. 1. 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for
G
23. 1. J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
       1. Sprint G release dev sprint 1: Aug-22 to Sep-11
       2. Sprint G release dev sprint 2: Sep-12 to Oct-2
       3. Sprint G release dev sprint 3: Oct-3 to Oct-23
       4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
       5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)
    3. GRPC vs RMR
       1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
       2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
       3. need to look at Mavenir E2SM-RC proposal.
       4. impact on xapp frameworks will happen as well.
       5. Alexandre mentioned option of using QUIC (grpc over QUIC).
    4. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
       1. 2022-04-26: in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
       2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
       3. Thoralf to schedule another meeting end of May (after F).
       4. 2022-06-07: Thoralf will schedule a meeting for week after next week
       5. 2022-06-21→2022-07-05: This has to wait for end of July
    5. Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
       1. 2022-07-19 no news
    6. RUST as a language for xApps and framework. Will take this in the details in next meeting.
       1. 2022-07-19 TOC approved ric-plt/xapp-frame-rust is ready for content. ric-app/hw-rust still to be created
       2. 2022-07-19 go through commit steps
    7. RICAPP agenda: RICAPP Meetings.

    2022-07-05 (Tuesday)

    Recording: link to zoom recording

    1. 1. 1. Example Nokia J release: link
    1. 1. input for release candidates: left ovleft oversers and generally open items, RSAC
       2. Sprint dates
          1. TODO - general timeframe: Jan-June 2024

    
    

    1. RICAPP agenda: RICAPP Meetings.

    
    

    2023-12-19 demo meeting instead of the normal project meeting, same time slot

    2023-12-05

    Recording: link to zoom recording
    

    1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
       1. Last checked on 2023-09-26
          1.  https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11898 OK (simple alarms, but we created RIC-1028 for a more general test mock framework)
          2. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 OK, since deployment acts as test
          3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12025 ok, lots of code, but very generic. Naman will try to add test case
          4. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12032 OK, only go.sum file
          5. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11895 OK (simple alarms, but we created RIC-1028 for a more general test mock framework)
       Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).2022-07-05:
       we did not do this this time
    2. every second time: Review code coverage stats and blocker code smells
       1. We take a look at the two links in the beginning of this page: Code coverage reports..
       2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
       3. Thoralf did this last on May2023-27-2022. 2022-07-05 05-23:  we did not do this this time
    3. Every time: Check if there are new bug reports in JIRA: link
       1. 2022-07-05: we did not check this this time.
       2. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
       3. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
       4. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       5. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
       6. RIC-897 SCTP connection fails with Viavi // update with workaround
       7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       8. RIC-894 long idle period (days) causes RMR connection breaks
       9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
           1. 2021-12-21: Trying to get bandwidth for this during F release.
       12. RIC-837 RMR is not forwarding messages from E2T to E2M
       13. RIC-835 → 2021-12-07 news from Viktor
       14. fixed:no new fixes
           
       15. anybody would like to get more familiar with RMR?
       Sunil still to discuss with other team members for other items from subteam-hOther tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
       Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05& 2022-07-19 update:  - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
       
    4. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
    5. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
    6. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
    7. 2022-04-26: still open
    8. 2022-05-11: expecting to finalize by May-27
    9. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    10. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
    11. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
        1. 2022-04-12
           1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
           2. actual workshop planned for RSAC on Apr-21 9am EDT.
           3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
        2. 2022-04-26
           1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
              
           2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
        3. 2022-05-11:
           1. Currently in the hands of OTF team (Alex)
           2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
              1. 2022-05-30: Thoralf comment in RIC-915
                 
        4. 2022-06-21: Xtesting proposed as alternative to OTF
        5. 2022-07-05: Any news from James?
    12. Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
        
        1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
        2. 2022-06-21
           1. RIC-642 (python) done
           2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
        3. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-py) out of the F release. Which means they are likely early G release features.
    13. 2022-07-05: still two remaining demos.
        
        1. No demo today (plan for 2022-07-19) 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
        2. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
           
        3. 2022-07-05: Thoralf uploaded demo on deploying RIC, connecting the simulator project's E2 (node) simulator, Nokia simulator and deploy the hw-go xapp as well: 2022-05-24 Release F
    14. F release wrap up
        1. 2022-07-05 & 2022-07-19: F release. See demo page: Release criteria checklist - Release F, Near-RT RIC (F release) = image list, F Release = summary, 2022-05-24 Release F = demos.
    15. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
        1. 2022-04-26:
           1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
           2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
           3. Thoralf to schedule another meeting end of May (after F).
           4. 2022-06-07: Thoralf will schedule a meeting for week after next week
        2. 2022-06-21→2022-07-05: This has to wait for end of July
    16. Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
        1. 2022-07-05 no news
    17. RUST as a language for xApps and framework. Will take this in the details in next meeting.
        1. 2022-06-21: We had a meeting on this last week and proposal for TOC is in the making. Two new components: ric-plt/xapp-frame-rust and ric-app/hw-rust)
        2. 2022-07-05:
           1. addition of ric-plt/xapp-frame-rust and ric-app/hw-rust was approved by TOC on Jun-23-2022.
              
           2. Thoralf to create the repos once back from holiday (mid July)
    18. RICAPP agenda: RICAPP Meetings.

    2022-06-21 (Tuesday)

    Recording: link to zoom recording

    1. 1. RIC-1025 memory leak in routing manager
       2. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

       3. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

       4. RIC-1015 e2t too High default message size. → Nokia

       5. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

       6. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

       7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
       8. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look
       9. RIC-991 CVE-2023-40997 RMR related (not a duplicate) - Alexandre will take a look
       10. RIC-989 CVE-2023-40998 RMR (minor) security issue - Alexandre will take a look
       11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
       12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
       13. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
       14. RIC-915 dms_cli for installing xapp not working (raised by James)
       15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
       17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       18. RIC-894 long idle period (days) causes RMR connection breaks
       19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       21. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
           1. 2021-12-21: Trying to get bandwidth for this during F release.
       22. RIC-837 RMR is not forwarding messages from E2T to E2M
       23. RIC-835 → 2021-12-07 no news from Viktor
       24. fixed:
           
    2. James: updates?
       1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
       2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
          1. ODU-high and near-RT RIC (currently using stub).
          2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
          3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
          4. James will check with Sunil on issues he has with the test cases
          5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
       3. 2023-10-24
          1. updates from O-RAN f-2-f:
             1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
             2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
                1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
                2. more discussion coming at the joint OSC/OAI workshop in Boston
             3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
          2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
       4.  2023-11-07
          1. James is working with Taiwan lab on making sure we have good coverage
       5. 2023-11-21
          1. was at OSC-OAI conference
          2. could start using team accounts to test beds from Colosseum (NU) and ARA
          3. discussed with Bimo (Taiwan lab) on pair-wise testing
          4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    3. Prashant's work in near-RT RIC(subteam-p)
       1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
       2. 2024-01-16
    4. Sunil updates (subteam-h)?
       1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
       2. 2023-11-07: Not in the call today
       3. 2023-11-21: no updates. Difficult to find engineers working on this.
       4. 2024-01-16: no news. Wants to re-valuate tickets (earlier assigned to HCL).
    5. Subhash/Naman updates (subteam-s) ?
       1. 2023-08-29: no news, other than Naman working on the operator implementation.
       2. 2023-09-12:
          1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
          2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
             1. Thoralf sent instructions to John → DONE
          3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
          4. Naman also works on the operator implementation
       3. 2023-09-26:
          
          1. kubernetes operator new repo needed or not?
             1. xapp deployment → appmgr or ricdms
             2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
          2. What happened to kserve adapter? → Subhash can check.
       4. 2023-11-07
          1. Naman presented his k8s operator work. Naman used Kubebuilder
          2. still working on operator to deploy RIC platform
       5. 2023-11-21:
          1. k8s operator commits - needs to be finalized.
       6. 2023-12-05: Naman gave an update on status of Samsung items
    6. Abhijit updates (subteam-ag) ?
       1. 2023-10-24:
          1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
             
          2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
             
          3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia
             
          4. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
          5. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    7. Cap Gemini updates (subteam-cg)? 
       1. 2023-11-07: after discussions on the topic we would like to proceed with

          1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

          2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.

          3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
          4. TODO-thoralf-to-ask-Gunja-to-present- Thoralf
    8. Himanshu (subteam-gs) would like to work on RIC-963
       
       1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
    9. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
       1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8368 OK cleanup of ric-dep and it-dep (only copied code)
       2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493 OK
       3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/8569 OK
    10. every second time: Review code coverage stats and blocker code smells
        1. We take a look at the two links in the beginning of this page: Code coverage reports..
        2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
        3. Thoralf did this last on May-27-2022. Not done this time
    11. Every time: Check if there are new bug reports in JIRA: link
        RIC-921 fix UT test case in e2mgr to stub time (leftover from review
        1. 2023-11-07: addressing review comments of
        2. https://gerrit.o-ran-sc.org/r/c/ric-plt/
        e2mgr
        3. submgr/+/
        8493)
        4. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
        5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
        6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
        7. RIC-897 SCTP connection fails with Viavi // update with workaround
        8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
        9. RIC-894 long idle period (days) causes RMR connection breaks
        10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
        11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
        12. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
            1. 2021-12-21: Trying to get bandwidth for this during F release.
        13. RIC-837 RMR is not forwarding messages from E2T to E2M
        14. RIC-835 → 2021-12-07 news from Viktor
        15. fixed: RIC-920 (gNB ID fix)
            
        16. anybody would like to get more familiar with RMR?
    12. Sunil still to discuss with other team members for other items from subteam-h
        1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
           
           1. Sangeetha working on RIC-860, done, but code still to be checked in.  
           2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 
           3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
           4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
              
           5. 2022-04-26: still open
           6. 2022-05-11: expecting to finalize by May-27
           7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    13. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
        1. 2022-04-12
           1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
           2. actual workshop planned for RSAC on Apr-21 9am EDT.
           3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
        2. 2022-04-26
           1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
              
           2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
        3. 2022-05-11:
           1. Currently in the hands of OTF team (Alex)
           2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
              1. 2022-05-30: Thoralf comment in RIC-915
                 
        4. 2022-06-21: Xtesting proposed as alternative to OTF
    14.  Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
        
        1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
        2. 2022-06-21
           1. RIC-642 (python) done
           2. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cpp/+/8561
    15. 2022-06-21: demo held on 2022-07-06. Remaining demos planned for 2022-06-21
        
        1. No demo today (plan for 2022-07-19) 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
        2. 10min RIC-916 new reconnect timer in E2 to reject new connect for x seconds (dhiraj)
        3. 10min RIC-642 xapp-frame-py subscription REST interface → end of August (Erkki)
           
    16. F release wrap up
        1. see §6 in Jira usage conventions
        2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
        3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
           1. See demo page: 2022-05-24 Release F
    17. New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
        1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
           1. 2022-04-26:
              1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
              2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
              3. Thoralf to schedule another meeting end of May (after F).
              4. 2022-06-07: Thoralf will schedule a meeting for week after next week
              5. 2022-06-21: This has to wait for end of July
                 
    18. Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
    19. RUST as a language for xApps and framework. Will take this in the details in next meeting.
        1. 2022-06-21: We had a meeting on this last week and proposal for TOC is in the making. Two new components: ric-plt/xapp-frame-rust and ric-app/hw-rust)
        2. Approved by the TOC.
    20. RICAPP agenda: RICAPP Meetings.

    2022-06-07 (Tuesday)

    Recording: link to zoom recording

    1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
       1. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/8324  OK (commit of previously reviewed files in e2ap branch)
       2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8303 OK (commit of previously reviewed files in e2ap branch)
       3. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/8323 OK (commit of previously reviewed files in e2ap branch)
          
       4. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/8332 OK (change in proto file that caused changes in generated files)
       5. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8368 OK (lots of code moved from it/dep repo)
    2. every second time: Review code coverage stats and blocker code smells
       1. We take a look at the two links in the beginning of this page: Code coverage reports..
       2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
       3. Thoralf did this on May-27-2022 - no surprises
       4. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-02-13 → 2022-05-26)
       5. ric-plt/appmgr 19,3 // 1 major bug (2022-01-30 → 2022-02-13 → 2022-05-26)
       6. ric-plt/e2mgr 88,6 → 87,7 // no bugs (2021-11-18 → 2022-02-14 → 2022-05-27)
       7. ric-plt/lib/rmr 86,1 // no bugs (2021-11-23 → 2022-02-08 → 2022-05-24)
       8. ric-plt/sdlgo 90,2 → 90,5 // no bugs (2022-01-31 → 2022-02-14 → 2022-05-27)
       9. ric-plt/submgr 51,4 // no bugs (2022-01-30 → 2022-02-13 → 2022-05-27)
       10. ric-plt/tracelibcpp 0,0 // 1 major bug (2022-01-25 → 2022-02-08 → 2022-05-24)
       11. ric-plt/tracelibgo 96,2 //0 bugs (2022-01-30 → 2022-02-13 → 2022-05-27)
       12. ric-plt/xapp-frame 0,0 // no bugs (2021-11-22 → 2022-02-13 → 2022-05-26)
       13. ric-plt/xapp-frame-cpp 95,6 → 96,3 // no blocker bugs (2022-01-26 → 2022-02-00 → 2022-05-25)
           
    3. Every time: Check if there are new bug reports in JIRA: link
       1. RIC-915 dms_cli for installing xapp not working (raised by James) (2022-05-30 Thoralf added comment in the case)
       2. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       3. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
       4. RIC-897 SCTP connection fails with Viavi // update with workaround
       5. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       6. RIC-894 long idle period (days) causes RMR connection breaks
       7. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       8. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       9. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
          1. 2021-12-21: Trying to get bandwidth for this during F release.
       10. RIC-837 RMR is not forwarding messages from E2T to E2M
       11. RIC-835 → 2021-12-07 news from Viktor
       12. fixed: no new fixes
           
       13. anybody would like to get more familiar with RMR?
    4. Sunil still to discuss with other team members for other items from subteam-h
       1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
          
          1. Sangeetha working on RIC-860, done, but code still to be checked in.
          2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
          3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
          4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
             
          5. 2022-04-26: still open
          6. 2022-05-11: expecting to finalize by May-27
          7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
    5. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
       1. 2022-04-12
          1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
          2. actual workshop planned for RSAC on Apr-21 9am EDT.
          3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
       2. 2022-04-26
          1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
             
          2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
       3. 2022-05-11:
          1. Currently in the hands of OTF team (Alex)
          2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
             1. 2022-05-30: Thoralf comment in RIC-915
                
    6. Progress on E2APv2.0?
       1. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
          1. kpimon
          2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
          3. all hello-world xapps (hw-go already uses submgr REST ifc)
             1. hw-go issue with old xapp frame lib used. - needs to be updated.
          4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
             1. done, but not yet open for review.
             2. 2022-05-30: Simulator worked fine, but thoralf raised SIM-99 for supporting source-address binding in the simulator
          5. 2022-05-31: as we're not ready with RIC-641 (cpp) and RIC-642 (python) we decided to still keep RMR enabled as interface provided by the subscription manager. RIC-642 is almost ready, and I understand RIC-641 is also being worked on.  07-06-2022 - RIC-641 HCL team is working on this.   
          6. 07-06-2022: E2APv2.0 - Code merged
       2. in DU
          1. 2022-02-23 user-30c9d reported in TOC that this work is done.
    7. RIC-641 Sandeep (HCL) is working on this. Work is progressing.
       
       1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
       2. 2022-04-26: working on it
       3. 2022-05-11: news? Could be handled as exception to be worked on during May-15 to Jun-5 so we can still include this into F.
       4. 2022-06-07: Any news?
    8. F release wrap up
       1. see §6 in Jira usage conventions
       2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
       3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
          1. See demo page: 2022-05-24 Release F
          2. 2022-07-06 demo held. Remaining demos planned for 2022-06-21
             
             1. 5 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID. (Manoj)
             2. 10min RIC-916 new reconnect timer in E2 to reject new connect for x seconds
    9. New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
       1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
          1. 2022-04-26:
             1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
             2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
             3. Thoralf to schedule another meeting end of May (after F).
             4. 2022-06-07: Thoralf will schedule a meeting for week after next week
    10. Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S.
    11. Note - 6-7-2022 : Matti send a mail on this.  RUST as a language for xApps and framework. Will take this in the details in next meeting.
    12. RICAPP agenda: RICAPP Meetings.

    2022-05-24

    we used this slot as demo meeting for the F release. Demo recording: 2022-05-24 Release F

    2022-05-11 (exceptionally Wednesday)

    Recording: link to zoom recording

    1. 1. 11681 tomorrow. Then we should be able to merge this.
       2. 2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
       3. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. Dhiraj (subteam-r)
       
       1. 2023-08-22:
          1. checking compliance/license issues
          2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
       2. 2023-08-29:
          1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes

       3. 2023-11-07

          1. license topic still be discussed. Was working on an other project for last months

       4. 2023-12-05: moved the IPv6 item  to J release
    3. Alexandre (subteam-utfpr)
       
       1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
       2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    4. Nokia (subteam-n)
       1. RIC-997 postponed to J
    5. Demo
       1. We will use the project meeting slot for the demos
       2. Naman to demo k8s operator deployment of platform (xapp part already done) and also A1 creating a policy.
       3. Adding support for DU in E2T/E2M/RNIB - >thoralf can do if not Gunja.
          
    6. I release content
       1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    1. 1. input for release candidates: left overs and generally open items, RSAC
       2. Sprint dates
          1. Sprint I release dev sprint 1: Aug-21 to Sep-10
          2. Sprint I release dev sprint 2: Sep-11 to Oct-1
          3. Sprint I release dev sprint 3: Oct-2 to Oct-22
          4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
          5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
       3. Plan (v03 as of 2023-08-18):
          1. I release plan moved to I release page.
          2. Thoralf will start generating images next week (Dec-11 - Dec-13)
    2. RICAPP agenda: RICAPP Meetings.

    2023-11-21

    Recording: link to zoom recording
    

    1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
       1. Last checked on 2023-09-26
          1.  TODO
    2. every second time: Review code coverage stats and blocker code smells
       1. We take a look at the two links in the beginning of this page: Code coverage reports..
       2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
       3. Thoralf did this last on 2023-05-23:  we did not do this this time
    3. Every time: Check if there are new bug reports in JIRA: link
       1. RIC-1025 memory leak in routing manager
       2. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

       3. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

       4. RIC-1015 e2t too High default message size. → Nokia

       5. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

       6. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

       7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
       8. RIC-1001 RMR service should verify route tables - Alexandre will take a look
       9. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
       10. RIC-989 RMR (minor) security issue - Alexandre will take a look
       11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
       12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
       13. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
       14. RIC-915 dms_cli for installing xapp not working (raised by James)
       15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
       17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       18. RIC-894 long idle period (days) causes RMR connection breaks
       19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       21. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
           1. 2021-12-21: Trying to get bandwidth for this during F release.
       22. RIC-837 RMR is not forwarding messages from E2T to E2M
       23. RIC-835 → 2021-12-07 no news from Viktor
       24. fixed:
           
    4. James: updates?
       1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
       2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
          1. ODU-high and near-RT RIC (currently using stub).
          2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
          3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
          4. James will check with Sunil on issues he has with the test cases
          5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
       3. 2023-10-24
          1. updates from O-RAN f-2-f:
             1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
             2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
                1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
                2. more discussion coming at the joint OSC/OAI workshop in Boston
             3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
          2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
       4.  2023-11-07
          1. James is working with Taiwan lab on making sure we have good coverage
       5. 2023-11-21
          1. was at OSC-OAI conference
          2. could start using team accounts to test beds from Colosseum (NU) and ARA
          3. discussed with Bimo (Taiwan lab) on pair-wise testing
          4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    5. Prashant's work in near-RT RIC(subteam-p)
       1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    6. Sunil updates (subteam-h)?
       1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
       2. 2023-11-07: Not in the call today
       3. 2023-11-21: no updates. Difficult to find engineers working on this.
    7. Subhash/Naman updates (subteam-s) ?
       1. 2023-08-29: no news, other than Naman working on the operator implementation.
       2. 2023-09-12:
          1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
          2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
             1. Thoralf sent instructions to John → DONE
          3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
          4. Naman also works on the operator implementation
       3. 2023-09-26:
          
          1. kubernetes operator new repo needed or not?
             1. xapp deployment → appmgr or ricdms
             2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
          2. What happened to kserve adapter? → Subhash can check.
       4. 2023-11-07
          1. Naman presented his k8s operator work. Naman used Kubebuilder
          2. still working on operator to deploy RIC platform
       5. 2023-11-21:
          1. k8s operator commits - needs to be finalized.
    8. Abhijit updates (subteam-ag) ?
       1. 2023-10-24:
          1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
             
          2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
             
          3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia
             
          4. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
          5. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    9. Cap Gemini updates (subteam-cg)? 
       1. 2023-11-07: after discussions on the topic we would like to proceed with

          1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

          2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.

          3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
          4. TODO-thoralf-to-ask-Gunja-to-present- Thoralf
    10. Himanshu (subteam-gs) would like to work on RIC-963
        
        1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
        2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
        3. 2023-11-21: as discussed in the beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    11. Dhiraj (subteam-r)
        
        1. 2023-08-22:
           1. checking compliance/license issues
           2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
        2. 2023-08-29:
           1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes

        3. 2023-11-07

           1. license topic still be discussed. Was working on an other project for last months

    12. Alexandre (subteam-utfpr)
        
        1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
        2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    13. Nokia (subteam-n)
        1. .RIC-997 likely being postponed.
    14. I release content
    1. 1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       2. input for release candidates: left overs and generally open items, RSAC
       3. Sprint dates
          1. Sprint I release dev sprint 1: Aug-21 to Sep-10
          2. Sprint I release dev sprint 2: Sep-11 to Oct-1
          3. Sprint I release dev sprint 3: Oct-2 to Oct-22
          4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
          5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
       4. Plan (v03 as of 2023-08-18):
          1. I release plan moved to I release page.

          1. 
             

    2. RICAPP agenda: RICAPP Meetings.

    2023-11-07

    Recording: link to zoom recording
    

    1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
       1. Last checked on 2023-09-26
          
          1. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
          2. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11889 ok. included test cases
          3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/11999 actually small changes, but as this is generated code, no need for test cases. Actually hand-written code is coming in another review together with test code.
    2. every second time: Review code coverage stats and blocker code smells
       1. We take a look at the two links in the beginning of this page: Code coverage reports..
       2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
       3. Thoralf did this last on 2023-05-23:  we did not do this this time
    3. Every time: Check if there are new bug reports in JIRA: link
       1. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

       2. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

       3. RIC-1015 e2t too High default message size. → Nokia

       4. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

       5. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

       6. RIC-1009 E2Mgr API can be improperly invoked → TODO-thoralf-converted-this-to-Epic
       7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
       8. RIC-1001 RMR service should verify route tables - Alexandre will take a look
       9. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
       10. RIC-989 RMR (minor) security issue - Alexandre will take a look
       11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
       12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
       Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
       1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/8127 ok
       2. https://gerrit.o-ran-sc.org/r/c/ric-plt/stslgo/+/8112 ok
       3. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8136 ok
       4. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/8147 ok - as only files only moved from other repo
       5. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8196 ok
       6. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8215 ok
       7. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8218 ok
       8. RIC-921 fix UT test case in e2mgr to stub time (leftover from review
       9. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7592 ok
    4. every second time: Review code coverage stats and blocker code smells
       1. We take a look at the two links in the beginning of this page: Code coverage reports..
       2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
       3. We did not do this today.
          
    5. 1. e2mgr/+/8493)
       2. RIC-915 dms_cli for installing xapp not working (raised by James)
       Every time: Check if there are new bug reports in JIRA: link
       2. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       3. RIC-903 901 new (from PW) DefaultUser setup fails when authentication is enabled for InfluxDB. 2022-05-11: fixed
       4. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
       5. RIC-897 SCTP connection fails with Viavi // update with workaround
       6. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       7. RIC-894 long idle period (days) causes RMR connection breaks
       8. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail. 2022-05-11: fixed
          
          1. could be staging repo related (10004) vs release repo (10002) for the base image
       9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
           1. 2021-12-21: Trying to get bandwidth for this during F release.
       12. RIC-837 RMR is not forwarding messages from E2T to E2M
       13. RIC-835 → 2021-12-07 news from Viktor
       14. fixed: RIC-903, RIC-890, RIC-891, RIC-892
           
       15. anybody would like to get more familiar with RMR?
    6. 2022-06-07: We plan to release in June. Thoralf will coordinate creation of container images by e-mail.
       1. F release tasks for releasing the container images: Near-RT RIC (F release)
       2. F release status: F Release
       3. F release criteria checklist (filled in by Thoralf): Release criteria checklist - Release F
    7. Sunil still to discuss with other team members for other items from subteam-h
       1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
          
          1. Sangeetha working on RIC-860, done, but code still to be checked in.
          2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
          3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
          4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
          5. 2022-04-26: still open
          6. 2022-05-11: expecting to finalize by May-27
    8. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
       1. 2022-04-12
          1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
          2. actual workshop planned for RSAC on Apr-21 9am EDT.
          3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
       2. 2022-04-26
          1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
             
          2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
       3. 2022-05-11:
          1. Currently in the hands of OTF team (Alex)
          2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
    9. Progress on E2APv2.0?
       1. in ric platform and simulators?
          1. 2022-04-26
             1. subscription manager change for E2APv2.0 is now in E2APv2.0 branch
             2. config update message support coming this week.
             3. after this cleanup of small things here and there that are still needed.
          2. 2022-05-10
             1. thoralf suggests May-13 as day for moving E2AP branch to master
                1. Subhash agrees. So let's aim for that.
                2. Subhash to list which Config transfer failure cases move into next release (just left-over create JIRA item)
             2. Nokia has already tested some E2APv2.0 procedures with Nokia simulator (like E2 setup, subscription success case)
             3. Subhash still working on simulator in sim project
       2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
          1. kpimon
          2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
          3. all hello-world xapps (hw-go already uses submgr REST ifc)
             1. hw-go issue with old xapp frame lib used. - needs to be updated.
          4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
             1. done, but not yet open for review.
       3. in DU
          1. 2022-02-23 user-30c9d reported in TOC that this work is done.
    10. RIC-641 Sandeep (HCL) is working on this. Work is progressing.
        
        1. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
        2. 2022-04-26: working on it
        3. 2022-05-11: news? Could be handled as exception to be worked on during May-15 to Jun-5 so we can still include this into F.
    11. F release wrap up
        1. see §6 in Jira usage conventions
        2. Thoralf to go through JIRA and check status of items. Thoralf might send e-mails to get current status.
        3. Thoralf to organize sprint demos for May-24, at 9am ET in an extended timeslot of the project meeting.
           1. See demo page: 2022-05-24 Release F
    12. New contribution proposals: Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
        1. Meeting on E2 Reset scheduled for Apr-13->Apr-20 9:30am IST
           1. 2022-04-26:
              1. in the meeting we discussed various ways how E2 reset can be implemented. We decided to check current specifications by O-RAN on how to support E2 Reset and how to align contributions with it.
              2. timer limitation still to be discussed and whether we can two implementations (with timer/without timer)
              3. Thoralf to schedule another meeting end of May (after F).
    13. 1. BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
        2. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
        3. RIC-894 long idle period (days) causes RMR connection breaks
        4. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
        5. RIC-857 sporadically RMR takes multiple minutes before being "ready"
        6. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
           1. 2021-12-21: Trying to get bandwidth for this during F release.
        7. RIC-837 RMR is not forwarding messages from E2T to E2M
        8. RIC-835 → 2021-12-07 no news from Viktor
        9. fixed: RIC-972
           
    14. James: updates?
        1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
        2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
           1. ODU-high and near-RT RIC (currently using stub).
           2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
           3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
           4. James will check with Sunil on issues he has with the test cases
           5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
        3. 2023-10-24
           1. updates from O-RAN f-2-f:
              1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
              2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
                 1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
                 2. more discussion coming at the joint OSC/OAI workshop in Boston
              3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
           2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
        4.  2023-11-07
           1. James is working with Taiwan lab on making sure we have good coverage
    15. Prashant's work in near-RT RIC(subteam-p)
        1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    16. Sunil updates (subteam-h)?
        1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
        2. 2023-11-07: Not in the call today
    17. Subhash/Naman updates (subteam-s) ?
        1. 2023-08-29: no news, other than Naman working on the operator implementation.
        2. 2023-09-12:
           1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
           2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
              1. Thoralf sent instructions to John → DONE
           3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
           4. Naman also works on the operator implementation
        3. 2023-09-26:
           
           1. kubernetes operator new repo needed or not?
              1. xapp deployment → appmgr or ricdms
              2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
           2. What happened to kserve adapter? → Subhash can check.
        4. 2023-11-07
           1. Naman presented his k8s operator work. Naman used Kubebuilder
           2. still working on operator to deploy RIC platform
    18. Abhijit updates (subteam-ag) ?
        1. 2023-10-24:
           1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0
              
           2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 
           3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it.
    19. Cap Gemini updates (subteam-cg)? 
        1. 2023-11-07: after discussions on the topic we would like to proceed with

           1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

           2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well. TODO-discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation

           3. TODO-thoralf-to-ask-Gunja-to-present
    20. Himanshu (subteam-gs) would like to work on RIC-963
        
        1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
        2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
    21. Dhiraj (subteam-r)
        
        1. 2023-08-22:
           1. checking compliance/license issues
           2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
        2. 2023-08-29:
           1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes

        3. 2023-11-07

           1. license topic still be discussed. Was working on an other project for last months

    22. Alexandre (subteam-utfpr)
        
        1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
        2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    23. Nokia (subteam-n)
        1. ...
    24. I release content
    1. 1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       2. input for release candidates: left overs and generally open items, RSAC
       3. Sprint dates
          1. Sprint I release dev sprint 1: Aug-21 to Sep-10
          2. Sprint I release dev sprint 2: Sep-11 to Oct-1
          3. Sprint I release dev sprint 3: Oct-2 to Oct-22
          4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
          5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
       4. Plan (v03 as of 2023-08-18):
          1. I release plan moved to I release page
    Pranesh raised the issue of message drops after idle times of about 15 minutes. Could be the same as RIC-894. May or not be related to K8S
    2. 1. 1. .
    3. RICAPP agenda: RICAPP Meetings.

    Older meeting minutes

    check from here: Project meetings (old)

    ...