...

RIC project meetings are open to the public and held on Tuesdays at 2pm UTC (winter) and 1pm UTC (summer).  World Time Zone Map

Zoom 1 Info:

...

...

2024-

...

04-

...

23

Recording: zoom link

1. Every time: Check rule RC-4 (link) that all L for CII compliance improvements we should do this from now oncheck that all large or XL commits of the last two weeks have also new unit tests. This is our policy. add a regular item in the meeting (once pwer month) to check code coverage

2021-02-16

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_02_16.mp4

1. discuss how to proceed with RIC-184. OTF,. robot. Maybe schedule another meeting during this week,

• update from HCL: User stories created under RIC-184 (InProgress)
  
  1. • Got credentials for OSC lab created for Alok  facilitated by Felix.
     • Requested Felix, for rest of the credentials for HCL team members
     • Working with HCL local IT team for VPN client whitelisting

...

RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress

• We be going through the content shared by Thoralf from previous effort of opentracing based work

RIC-731- [Static code and test coverage for E2] -  90% Completed.

• Blocked for Developer’s response.

RIC-671 [Achieve level "passing" in CII]

• Internally discussed the requirements for Epic.
• Need a setup call with Thoralf this week for clarifying & grooming the stories. Alok created a gap analysis. Alok to call for a meeting.

RIC-150 - Perform e2e RIC benchmarking

                Subtask: RIC-741   Verify Subscription flow using RMR API Subscription Request and response verification done using kubectl api and calculated latency on RoundTripTime of subscription flow in nanobot automation

                Subtask: RIC-742 Verify Indication flow using RMR API  Currently working on latest code of bouncer xapp and e2sim to validate the indication message flow locally using nanobot. Working on CDF (distribution function) plotting to represent latency vs throughput on the message flow.

RIC-743 Create multiple e2sim for RIC benchmarking

                Benchmarking the code with 1500+ E2SIM, But the result is not stable (only 50 or 700 E2 nodes are connected). "moving up from 50 is not yet stable". Currently checking on this.

1.   Try to make this reproducible. Maybe someone from E2T/E2M can take a look at it,

RIC-744 Verify the E2E communication for multiple e2sim // adding the sleep timer after every GNB sub request that has reduced the number of message rejection on subMgr side. It like the 1 is rejected out of 5 messages. //                               Debugging the issue // continue by e-mail with committers.

...

1. 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 - 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: 
       
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.
   7. 2024-04-23:
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,2024-04-23: 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 - Done
      
   10. 2024-03-09: Absent
   11. 2024-04-23: Not much updates.
       
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,2024-04-23: Not available
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
   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.
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,2024-03-09,2024-04-23: 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.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
    6. 2024-04-23: Not present
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,2024-04-09,2024-04-23: 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,2024-04-09,2024-04-23: 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.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
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,  to include k8s version upgrade, clean up of pending issues.
16. 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)
17. 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:
      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.
      
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,2024-03-09: 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.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
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,2024-04-09: 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,2024-04-09: 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.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
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
16. 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)
17. 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".
    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 teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    4. 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.
    5. 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. 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. 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)
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 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:
       
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
   2. 2024-01-16
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: no news. Wants to re-valuate tickets (earlier assigned to HCL).
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
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 teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    4. 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.
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

    4. 2023-12-05: moved the IPv6 item  to J release
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. 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.
       
15. 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 
   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: RIC-972
       
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. 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
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
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
         
      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.
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. TODO-discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation

      3. TODO-thoralf-to-ask-Gunja-to-present
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. Rahul to send a mail on the type of octet strings we might have.

...

2021-02-02

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_02_02.part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2021_02_02.part2.mp4

1. We would like to introduce a minor branch from Cherry in which we combine Cherry with the xApp onboarding feature. This way we have a stable branch (as compared to master) against which xApps can be developed that require this change.
   1. fixes done to cherry we will also do to "cherry-plus-onboarding" (exact branch date to be checked with Felix, but it should be  soon (this or next week)).
   2. only branch is in components that actually have a change.
   3. all Dawn features continue on master (no similar approach for such features)
2. Moved the following items from subteam-n back to subteam-n-proposal
   

   1. RIC-71 Subscription manager: Better debugging capabilities

   2. RIC-226 fix for SDL (C++) silent hang

   3. RIC-330 Merge individual library repos (lib) python into framework repo. Also for C++ and for Golang

   4. RIC-366 A1 API as higher abstraction level in xapp framework SDK (golang)higher abstraction level in xapp framework SDK (golang)

   5. RIC-373 O1 mediator to check health of all platform components and expose this via O1

   6. RIC-421 O1 mediator to handle restart gracefully

3. please check your contribution plan and mark things as "soft commitment" like subteam-X. and things that you don't commit to as "subteam-X-proposal". Once done, send me a e-mail with that fact. Deadline: Feb-9-2021
   1. links under §7.5 in Jira usage conventions
4. A1-EI
   1. only minor update to slideset and that serves as design proposal according to which implementation is done. A1-EI_v2.pptx
5. configuration update concept.
   1. further discussion by mail.
6. A1 mediator and RMR lib update?
   1. updating A1 mediator with latest RMR image. Matti to add thoralf in mail thread on this
7. RICAPP agenda: RICAPP Meetings.

2021-01-21 4th meeting on Dawn planning

Recording: RIC_and_RICAPP_dawn_planning_2021_01_21.part1.mp4 and RIC_and_RICAPP_dawn_planning_2021_01_21.part2.mp4

1. discuss CII badging page: CII status: near-RT RIC
   
   1. HCL wanted to some work related to CII: (1) code scanning for vulnerabilities (owasp tool and more tools) (2) continuation of static code analysis (E2T)
      1. contact on LF side is: trishan de lanerolle (tdelanerolle@linuxfou....org)
   2. HCL Sangeetha take a look if we can do dsomething for CII "The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project."
2. RIC-671 mark to E and Dawn
3. RIC-636 and RIC-635 Ramesh is checking
4. RIC–114: Thoralf to remove from HCL and create new item for INflux-based time series support. Thoralf created RIC-734 after the mneeting and removed RIC.-114 from HCL and dawn
5. RIC-682 (Samsung) - look if the only remaining item in it (RIC-382) make sense and if you want to work on this.

2021-01-19

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_01_19.mp4

1. Implementation of RIC-114 (redis time series plugin) - Ramesh
   1. move out from Dawn: RIC-114
   2. create new item for InfluxDB Relay integration and unless we see issues we include it always into Near-RT platform, but only for xApp usage. No need to have an abstract SDL interface that hides the actual underlying Time-series DB. Still to be discussed: Only put this in xApp framework if we can fully hide the fact that it is InfluxDB or put dependency on InfluxDB into xapp framework. Pending Also WG3 work.
2. E2APv1.1 vs E2APv2.0 and do we upgrade to E2APv1.1. Do we define configuration transfer and OID in E2 Setup as mandatory (as in E2APv2.0) even if in E2APv1.1 they are optional?
   1. E2SIM work also needed. Need to bring this up in TOC as it might affect other E2 nodes implementations on DU/CU.
   2. thoralf to schedule a meeting on this with Rahul/Subhash/Rittwik for next week Wednesday/Thursday
3. FYI: Dhiraj (committer in E2T) would like to have discussion with Alok on RIC-731. He (Dhiraj) will call a meeting, To get some understanding of how this was done for other repos and what Alok is planing.
4. Subhash wants to discuss A1-EI. We agreed to

   1. A1 mediator should provide the mechanism to receive EIJobResult and further send it to xApp over RMR.

   2. xApp should use preconfigured EITypeID  to create EIJob.
5. going through current list of Dawn items and checking commitments - meeting on Thursday, 8am, ET.
6. RICAPP agenda: RICAPP Meetings.

2021-01-05

Recording: near_rt_ricplatform_and_ricapp_meeting_2021_01_05.mp4

1. discuss RIC-708  on whether AT&T or Samsung can work on the python and c++ subitem for the xapp framework (mentioned in description of RIC-708). Matti said the python part AT&T could work on. To be checked by Matti.
2. E2AP 1.1 spec high level discussion (raised by Rahul) - slideset presented, next step is to continue by e-mail disucssion (Matti, Thoralf, E2M/E2T committers, )
3. A1-EI discussion. Subhash waiting for comments from Matti. Also there was some discussion on the "EI result object" (received by xApp/near-RT RIC). EI result object expected top be provided by EI data producer, while job is managed by non-rt RIC. I.e., there's an interface between non-RT RIC and EI data producer on informing about jobs (and URL targets for the EI result objects).
4. HCL (Alok) to report on quick analysis on "more advanced" LF CI/CD pipeline that we might want to use in context of OTF (integration track).
   1. uses gitlab-based CI. for continuing testing LF uses XTESTING
   2. Alok shared the link from opnfv: http://testresults.opnfv.org/functest/xtesting/
   3. Alok still discuss with nanobot folks and Felix how current verification is done. (infrastructure testing?)
   4. Subhash asked about existing robot test cases and how they would be integrated.
   5. Ramesh commented that ONAP is more aligned with LFN and that's one of the reasons we are looking into this.
5. RICAPP agenda: RICAPP Meetings.

2020-12-22

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_12_22.mp4

1. we started 15 minutes late
2. next meeting Jan-5-2021
3. For 2021: HCL (Alok) to report on quick analysis on "more advanced" LF CI/CD pipeline that we might want to use in context of OTF (integration track).
4. A1/EI implementation plan A1-EI-HLD.pptx
5. RICAPP agenda: RICAPP Meetings.

2020-12-08 dawn planning

Recording: RIC_and_RICAPP_dawn_planning_2020_12_08_part1.mp4 , RIC_and_RICAPP_dawn_planning_2020_12_08_part2.mp4 and RIC_and_RICAPP_dawn_planning_2020_12_08_part3.mp4

2020-12-08 main project meeting

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_12_08_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_12_08_part2.mp4

1. CII badging status (end of Cherry) needs to be filled in: CII status: near-RT RIC
   1. nobody volunteered. Thoralf to do this.
2. committers changed for E2T and E2Mgr. For A1, for ric-dep
   1. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5249 ric-dep
   2. 2023-11-07: addressing review comments of
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/
   e2mgr
   4. submgr/+/
   5196 e2mgr
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/5195 e2
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/5238 a1
3. Dawn planning: See §7.5 for filters for Dawn planning. We use labels:
   1. preliminarily committed: subteam-n, subteam-h / h1, subteam-s / s1 / s2, subteam-a
   2. proposal to other team: subteam-n-proposal, subteam-s-proposal, subteam-h-proposal, subteam-a-proposal
4. demos in December for Dec-17? let me know if there's something to demo.
   
   1. HCL proposed demo of benchmarking
5. meeting on Dec-22? We will keep the meeting. What about Jan-5? Also ok.
6. HCL status
   
   1. • HCL: RIC-149: Review comments completed. Merged. DONE
      • HCL: RIC-150: Code committed and Merged. completed part in Cherry (log-base checking), but more work in Dawn (API based checking)
      • HCL: RIC-109: Merged. marked as DONE
      • HCL: RIC-360: Code submitted & Merged CLOSE once gerrit review in RIUC-678 is done (see open review https://gerrit.o-ran-sc.org/r/c/it/dep/+/5237)
      • HCL: RIC-509: Merged. CLOSE in JIRA DONE

      In Progress:

      • Enhancing E2E packet flow between xapp and e2sim by adding APIs to capture and parse the packets
      • RIC indication message decoded in bouncer xapp. Multi E2 connection setup in progress.
7. Samsung: no updates related to Cherry.
8. RICAPP agenda: RICAPP Meetings.

For Dawn planning meeting:

1. 1. 11681 tomorrow. Then we should be able to merge this.
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

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. ...
5. 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.
2. RICAPP agenda: RICAPP Meetings.
3. Dawn-R7 starts this week and is up to about Mar-5, Dawn-R8 starts Mar-6 and ends ~Apr-26
4. RIC-705/RIC-706 subteam-s or subteam-a?

Older meeting minutes

check from here: Project meetings (old)

...