...

...

2024-

...

04-

...

Sunil kindly agreed to host this meeting as Thoralf is on holiday.

23

Recording: zoom linkRecording: TODO

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/alarm-go/+/11149 OK, go version update only
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/11234 OK, test case added for IPv6 tests
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11324 PK, test case updated
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11733 OK, generated code from API
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
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-1012 RMR not working in A1 mediator 
   2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
   3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   5. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   6. RIC-989 RMR (minor) security issue - Alexandre will take a look
   7. RIC-972 (Naman) URL for A1 mediator to align with spec.
   8. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   9. 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)
   10. RIC-915 dms_cli for installing xapp not working (raised by James)
   11. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   12. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   14. RIC-894 long idle period (days) causes RMR connection breaks
   15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   17. 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.
   18. RIC-837 RMR is not forwarding messages from E2T to E2M
   19. RIC-835 → 2021-12-07 no news from Viktor
   20. 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 coudl be done with OSC.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26 : 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.
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.
8. Abhijit updates (subteam-ag) ?
   1. 2023-08-22: next release item discussed and RIC-979
   2. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
         1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
   3. 2023-09-12:
      1. changes related to registration API needed in xapp-frame (problem still to be thought of)
      2. something not working in github: IT-25974 - again related to github replication.
   4. 2023-09-26
      1. Abhijit presented his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. We decided to proceed with this.
         
      2. github action problem with master vs g release for replication → ticket.
      3. Abhijit wanted to provide a video for new way of ric deployment
   5. 2023-10-10:
      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
9. Cap Gemini updates (subteam-cg)? 
   1. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
      
      1. Ashish S. (CapGemini) presented this.
      2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
         
         1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
         2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
         3. additional latency comes only from guidance request
         4. xapp-framework could be extended to automatically do E2 guidance requests
   2. 2023-09-26:
      1. first step of new repo created, but still issues with initial files in repo. Thoralf raised request to LF: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26015 
   3. 2023-10-10:
      1. conflictmgr repo is now ready for commits: https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/conflictmgr,general
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".
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
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. Sunil handles today's (Oct-10) meeting as Thoralf is on holiday
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.
2. RICAPP agenda: RICAPP Meetings.

2023-09-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 2023-09-26
      
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/11149 OK, go version update only
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/11234 OK, test case added for IPv6 tests
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11324 PK, test case updated
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11733 OK, generated code from API
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
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-1011 (Nokia fixes) E2 error with cause duplicate-error for all subscriptions requests after resource-limit failure - FIXED
   2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
   3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   5. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   6. RIC-989 RMR (minor) security issue - Alexandre will take a look
   7. RIC-979 (Abhijit will close this one) Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
   8. RIC-972 (Naman) URL for A1 mediator to align with spec.
   9. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   10. 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)
   11. RIC-915 dms_cli for installing xapp not working (raised by James)
   12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   14. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   15. RIC-894 long idle period (days) causes RMR connection breaks
   16. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   17. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   18. 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.
   19. RIC-837 RMR is not forwarding messages from E2T to E2M
   20. RIC-835 → 2021-12-07 no news from Viktor
   21. fixed: RIC-1011, RIC-979
4. James: updates?
   1. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
   2. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
         1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
         2. e.g., existing discussion with John
   3. 2023-08-29: no news
   4. 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.
   5. 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 coudl be done with OSC.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26 : could not participate
6. Sunil updates (subteam-h)?
   1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
   2. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming 
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
      5. DMS delete PI
      6. E2 reset from ric to e2 node
   2. 2023-08-22: we discussed Jira item priority.
   3. 2023-08-29: no news, other than Naman working on the operator implementation.
   4. 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
   5. 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.
8. Abhijit updates (subteam-ag) ?
   1. 2023-05-23
      1. 1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
         2. testing of subscriptions using hw-rust (facing the E2T problem)
   2. 2023-07-18: no news
   3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
   4. 2023-08-22: next release item discussed and RIC-979
   5. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
         1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
   6. 2023-09-12:
      1. changes related to registration API needed in xapp-frame (problem still to be thought of)
      2. something not working in github: IT-25974 - again related to github replication.
   7. 2023-09-26
      1. Abhijit presented his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. We decided to proceed with this.
         
      2. github action problem with master vs g release for replication → ticket.
      3. Abhijit wanted to provide a video for new way of ric deployment
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

   2. 2023-08-22:
      1. Gunja provided reviews for DU support. Nokia to reviewed and merged
         

         1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

      2. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
         
         1. Ashish S. (CapGemini) presented this.
         2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
            
            1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
            2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
            3. additional latency comes only from guidance request
            4. xapp-framework could be extended to automatically do E2 guidance requests
   3. 2023-09-26:
      1. first step of new repo created, but still issues with initial files in repo. Thoralf raised request to LF: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26015 
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
    5. 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".
11. Dhiraj (subteam-r)
    
    1. 2023-07-18: IPv6 changes to come as review
    2. 2023-08-01: working on it.
    3. 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).
    4. 2023-08-29:
       1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
    2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    3. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. 2023-08-22: want to work on RIC-997
    2. 2023-09-12: Thoralf did changes to readthedocs in all near-RT RIC repos. LF informed (link) these changes are needed because some configuration parameters are being removed. No further changes needed due to this. Example: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11747. Note, though, that some repos don't currently generate read-the-docs documention. For the "A1" example, though you see a new documentation version in this URL: https://readthedocs.org/projects/o-ran-sc-ric-plt-a1/builds/
    3. Thoralf on holiday on Oct-10. Sunil?
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.

      2. E2 enhancements, incl. conflict mgmt.

         1. RIC-993 (CG): Near-RT RIC conflict management (*)

         2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

         3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)

         4. RIC-994 (S): Support for E2APv3.0

         5. RIC-995 (S): Support for RIC Query

         6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

         7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)

         8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

         9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1

      3. Other

         1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

         2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

         3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

         4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

         5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

         6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
2. RICAPP agenda: RICAPP Meetings.

2023-09-12

Recording: link to zoom recording

1. 1. (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
4. 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-04-11
      
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
5. 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
6. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1011 (Nokia fixes) E2 error with cause duplicate-error for all subscriptions requests after resource-limit failure
   2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
   3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   5. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
   6. RIC-989 rmr (minor) security issue - Alexandre will take a look
   7. RIC-979 (Abhijit will close this one) Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
   8. RIC-972 (Naman) URL for A1 mediator to align with spec.
   9. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   10. 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)
   11. RIC-915 dms_cli for installing xapp not working (raised by James)
   12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   14. RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
   15. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   16. RIC-894 long idle period (days) causes RMR connection breaks
   17. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   18. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   19. 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.
   20. RIC-837 RMR is not forwarding messages from E2T to E2M
   21. RIC-835 → 2021-12-07 no news from Viktor
   22. fixed: ...
7. James: updates?
   1. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
   2. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
         1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
         2. e.g., existing discussion with John
   3. 2023-08-29: no news
   4. 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.
8. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22 : could not participate
9. Sunil updates (subteam-h)?
   1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
   2. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
10. Subhash/Naman updates (subteam-s) ?
    1. 2023-08-01:
       1. E2AP v3.0 → we took a look at what changes are coming 
       2. A1 enhancements
       3. considering upgrade of ubuntu and k8s
       4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
       5. DMS delete PI
       6. E2 reset from ric to e2 node
    2. 2023-08-22: we discussed Jira item priority.
    3. 2023-08-29: no news, other than Naman working on the operator implementation.
    4. 2023-09-12:
       1. We had a meeting with John and Denis on non-rt RIC compatibilty. 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
       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
11. Abhijit updates (subteam-ag) ?
    1. 2023-05-23
       1. 1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
          2. testing of subscriptions using hw-rust (facing the E2T problem)
    2. 2023-07-18: no news
    3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
    4. 2023-08-22: next release item discussed and RIC-979
    5. 2023-08-29:
       1. created RIC-1004 for release I item.
       2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
          1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
    6. 2023-09-12:
       1. changes related to registration API needed in xapp-frame (problem still to be thought of)
       2. something not working in github: IT-25974 - again related to github replication.
12. Cap Gemini updates (subteam-cg)? 
    1. 2023-08-01

       1. Gunja to present conflict management design

       2. thinking about adding support for DU in E2T/E2M/RNIB in I release

    2. 2023-08-22:Gunja provided reviews for DU support. Nokia to reviewed and merged
        https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node
    3. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
       
       1. Ashish S. (CapGemini) presented this.
       2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
          1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
          2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
          3. additional latency comes only from guidance request
          4. xapp-framework could be extended to automatically do E2 guidance requests
13. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
    5. 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".
14. Dhiraj (subteam-r)
    
    1. 2023-07-18: IPv6 changes to come as review
    2. 2023-08-01: working on it.s
    3. 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).
    4. 2023-09-29:
       1. got clarity on license issues and now waiting for internal approval.
15. Alexandre (subteam-utfpr)
    
    1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
    2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
16. Nokia (subteam-n)
    1. 2023-08-22: want to work on RIC-997
    2. 2023-09-12: Thoralf did changes to readthedocs in all near-RT RIC repos. LF informed (link) these changes are needed because some configuration parameters are being removed. No further changes needed due to this. Example: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11747. Note, though, that some repos don't currently generate read-the-docs documention. For the "A1" example, though you see a new documentation version in this URL: https://readthedocs.org/projects/o-ran-sc-ric-plt-a1/builds/
17. 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. E2 enhancements, incl. conflict mgmt.

         1. RIC-993 (CG): Near-RT RIC conflict management (*)

         2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

         3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)

         4. RIC-994 (S): Support for E2APv3.0

         5. RIC-995 (S): Support for RIC Query

         6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

         7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)

         8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

         9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1

      2. Other

         1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

         2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

         3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

         4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

         5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

         6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
2. RICAPP agenda: RICAPP Meetings.

...

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

...

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-04-11
      
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xappric-framedep/+/10923 OK, module version updates only
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-1002 Abnormal signaling process cause E2Term crash (this could be a security issue)
   2. RIC-1001 RMR service should verify route tables.
   3. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
   4. RIC-989 rmr (minor) security issue - Alexandre will take a look
   5. RIC-979 Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
   6. RIC-972 URL for A1 mediator to align with spec.
   7. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   8. 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)
   9. RIC-915 dms_cli for installing xapp not working (raised by James)
   10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   12. RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
   13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   14. RIC-894 long idle period (days) causes RMR connection breaks
   15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   17. 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.
   18. RIC-837 RMR is not forwarding messages from E2T to E2M
   19. RIC-835 → 2021-12-07 no news from Viktor
   20. fixed: ...
4. James: updates?
   1. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
   2. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
         1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
         2. e.g., existing discussion with John
   3. 2023-08-29: no news
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22 : could not participate
6. Sunil updates (subteam-h)?
   1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming 
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
      5. DMS delete PI
      6. E2 reset from ric to e2 node
   2. 2023-08-22: we discussed Jira item priority.
   3. 2023-08-29: no news, other than Naman working on the operator implementation.
8. Abhijit updates (subteam-ag) ?
   1. 2023-05-23
      1. 1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
         2. testing of subscriptions using hw-rust (facing the E2T problem)
   2. 2023-07-18: no news
   3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
   4. 2023-08-22: next release item discussed and RIC-979
   5. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
         1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

   2. 2023-08-22:
      1. Gunja provided reviews for DU support. Nokia to reviewed and merged
         

         1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

      2. Conflict management status? Thoralf checked by e-mail after the meeting. Presentation by Gunja planned for Sep-12
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
    5. 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".
11. Dhiraj (subteam-r)
    
    1. 2023-07-18: IPv6 changes to come as review
    2. 2023-08-01: working on it.
    3. 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).
    4. 2023-09-29:
       1. got clarity on license issues and now waiting for internal approval.
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
    2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
13. Nokia (subteam-n)
    1. 2023-08-22: want to work on RIC-997
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. E2 enhancements, incl. conflict mgmt.

         1. RIC-993 (CG): Near-RT RIC conflict management (*)

         2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

         3. RIC-967 (CG) xApp-facing interface for subscription delete required (added on 2023-08-23)

         4. RIC-994 (S): Support for E2APv3.0

         5. RIC-995 (S): Support for RIC Query

         6. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

         7. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (Dhiraj interested as reviewer, but we had earlier discussion on this)

         8. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

         9. RIC-963 (GS) modify src code to be more lenient in ordering of IEs in ASN.1

      2. Other

         1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

         2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

         3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

         4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

         5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

         6. RIC-1004 (AG): Xapp Rust Framework enhancement after initial basic Xapp Framework Support
2. RICAPP agenda: RICAPP Meetings.

2023-08-22 (exceptionally one week later than normal)

Recording: link to zoom recording

...

1. Last checked on 2023-04-11
   
   1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only

...

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

...

1. RIC-1002 Abnormal signaling process cause E2Term crash (this could be a security issue)
2. RIC-1001 RMR service should verify route tables.
3. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
4. RIC-989 rmr (minor) security issue - Alexandre will take a look
5. new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 
6. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile DONE
7. RIC-979 Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
8. RIC-972 URL for A1 mediator to align with spec.
9. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
10. 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)
11. RIC-915 dms_cli for installing xapp not working (raised by James)
12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
14. RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
15. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
16. RIC-894 long idle period (days) causes RMR connection breaks
17. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
18. RIC-857 sporadically RMR takes multiple minutes before being "ready"
19. 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.
20. RIC-837 RMR is not forwarding messages from E2T to E2M
21. RIC-835 → 2021-12-07 no news from Viktor
22. fixed: RIC-986

...

1. Himanshu presented the integration of SDRAN-fork of OAI (with SDRAN E2 support added) and how the CU connects to OSC RIC

...

1. 2023-01-31:
   1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
   2. Subhash asked for a wiki page documenting this work.
   3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
      1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
      2. Tacker-based deployment needs to be checked.
2. 2023-03-14, 2023-03-28 : no news
3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
4. 2023-04-25: no updates
5. 2023-05-09:
   1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
      1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
      2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
      3. Input from other subprojects, incl. our near-RT RIC project?
   2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
6. 2023-05-23 → no news
7. 2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/
   1. usage of robot test cases (from it/test) is still something that James is thinking about.
   2. Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.
8. 2023-08-01:
   1. O2 integration with OSC RIC is still pending with WR.
   2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
9. 2023-08-22:
   1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
      1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
      2. e.g., existing discussion with John

...

1. 2023-08-22 : could not participate

...

1. 2023-07-18, 2023-08-01, 2023-08-22: no news

...

1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
   
   1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
      1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
         1. Thoralf to create JIRA item for this
         2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
         3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
         4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
      2. Integration with AI/ML project: kserve_adapter
         1. data pipeline (Hoejoo's e-mail)
            1. 2023-01-31 not discussed in today's meeting
2. 2023-03-14:
   1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
   2. A1 mediator nanobot integration still under work
3. 2023-03-28: work continues
   
4. 2023-04-11: E2 reset work in submgr is now under work.
5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
6. 2023-05-09:
   1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      
   2. A1 bug fixes being almost ready.
   3. A1 mediator nanobot might be delayed.
   4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
7. 2023-05-23
   1. E2 reset (from E2 node): done
   2. KServe adapter still being worked on.
   3. nanobot integration still being worked on.
8. 2023-07-18: no news, planning for I release
9. 2023-08-01:
   1. E2AP v3.0 → we took a look at what changes are coming 
   2. A1 enhancements
   3. considering upgrade of ubuntu and k8s
   4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
   5. DMS delete PI
   6. E2 reset from ric to e2 node
10. 2023-08-22: we discussed Jira item priority.

...

1. Thoralf raised support request to LF. Reminders sent. Still no solution.

...

1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
   
2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.

...

1. working on RNIB support in rust (https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10906) and next step hw-rust.

...

1. RIC-977 (subscription API) - pls. merge.
2. RIC-978 pls. try to complete during this week.
3. issues with E2 simulator → to get in contact with Naman and Subhash

...

1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
2. testing of subscriptions using hw-rust (facing the E2T problem)

...

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

2024-03-26

Recording:  link to zoom recording

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

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

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

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

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

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

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

2024-03-12

Recording:  link to zoom meeting

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

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

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

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

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

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

...

1. 2023-03-14
   1. RIC-851 done
   2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
2. 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-23: no news.
3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
   
4. 2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July
5. 2023-08-01

   1. Gunja to present conflict management design

   2. thinking about adding support for DU in E2T/E2M/RNIB in I release

6. 2023-08-22:
   1. Gunja provided reviews for DU support. Nokia to reviewed and merged
      

      1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

   2. conflit management status?

...

1. code changes, but difficult to test as difficult to change order of IEs in message.
2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.

...

1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
3. 2023-07-18: IPv6 changes to come as review
4. 2023-08-01: working on it.
5. 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).

...

1. 2023-05-23: no news
2. 2023-06-06:
   1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
   2. seems also to be a bug in interface name solution in RMR. Remember to create a JIRA item (RIC-987)
3. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."

...

1. GRPC vs RMR
   1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
   2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09, 2023-05-23, 2023-07-18: no update
2. 2023-08-22: want to work on RIC-997

...

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): link

      1. E2 enhancements, incl. conflict mgmt.

         1. RIC-993 (CG): Near-RT RIC conflict management (*)

         2. RIC-933 (CG) : Adding support for DU in E2T/E2M/RNIB

         3. RIC-994 (S): Support for E2APv3.0

         4. RIC-995 (S): Support for RIC Query

         5. RIC-996 (S) Support for Subscription modifications (dhiraj interested as reviewer)

         6. RIC-387 (S): Support for E2 reset from RIC to RAN (completes also RIC-383) (prio1) (dhiraj interested as reviewer, but we had earlier discussion on this)

         7. RIC-997 (N): Handling of RIC Error indication _during_ E2 setup

         8. RIC-963 (GS)modify src code to be more lenient in ordering of IEs in ASN.1

      2. Other

         1. RIC-998 (S): K8S operators for deploying/undeploy xApps(*(1))

         2. RIC-999 (S): A1 alignment with A1AP (still under investigation. Minimum is using correct URL) (*(1))

         3. RIC-954 (S): DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli) (1)

         4. Already in H: RIC-985 (UTFPR) IPv6 support for RMR 

         5. RIC-1000 (R): Support for only-IPv6 in RIC-internal interfaces

         6. Abhijit will create issue and send e-mail
2. RICAPP agenda: RICAPP Meetings.

2023-08-01

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-04-11
      
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xappric-framedep/+/10923 OK, module version updates only11743 → to be merged by Thoralf Czichy 
         
      2. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      3. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
2. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
3. 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. 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.
5. Alexandre (subteam-utfpr)
   
   1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
   2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
   3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
6. Nokia (subteam-n)
   1. RIC-997 postponed to J
   2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
7. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
8. J release
   
   1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
         1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
   2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
   3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
         
      2. committed items only: all teams (committed) and all teams (committed + tentative).
         
      3. items that are known to require work, but are currently not in J release: link

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. 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
11. Every time: Check if there are new bug reports in JIRA: link
    1. new: RIC-991 rmr related (not a duplicate) - Alexandre will take a look
    2. new: RIC-989 rmr (minor) security issue - Alexandre will take a look
    3. new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 
    4. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile
    5. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
    6. RIC-972 URL for A1 mediator to align with spec.
    7. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    8. 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)
    9. RIC-915 dms_cli for installing xapp not working (raised by James)
    10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    12. RIC-897 SCTP connection fails with Viavi // update with workaround
    13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    14. RIC-894 long idle period (days) causes RMR connection breaks
    15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    17. 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.
    18. RIC-837 RMR is not forwarding messages from E2T to E2M
    19. RIC-835 → 2021-12-07 no news from Viktor
    20. fixed:
12. Himanshu: demo on the OAI CU <--> OSC RIC integration
    1. Himanshu presented the integration of SDRAN-fork of OAI (with SDRAN E2 support added) and how the CU connects to OSC RIC
13. James: updates?
    1. 2023-01-31:
       1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
       2. Subhash asked for a wiki page documenting this work.
       3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
          1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
          2. Tacker-based deployment needs to be checked.
    2. 2023-03-14, 2023-03-28 : no news
    3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
    4. 2023-04-25: no updates
    5. 2023-05-09:
       1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
          1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
          2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
          3. Input from other subprojects, incl. our near-RT RIC project?
       2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    6. 2023-05-23 → no news
    7. 2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/
       1. usage of robot test cases (from it/test) is still something that James is thinking about.
       2. Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.
    8. 2023-08-01:
       1. O2 integration with OSC RIC is still pending with WR.
       2. OAI was discussed in last week's TOC, and it seems OAI license is not blokcer for using OAI in OSC-labs.
14. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-04-25:
       1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
       2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
       3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
    2. 2023-05-09
       1. question related to O1 (for stats handling without Vespa) - see RIC-798
    3. 2023-05-23
       1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
       2. E2 → Alexandre to review - 2023-06-06: merged
    4. 2023-06-06: Prashant posted in O-RAN WG3 on O1 a question related on the why of notifications + SFTP. No reply yet.
       1. 2023-07-18: feedback was that this is a 3GPP issue. Not further following up on this.
    5. 2023-06-18: Thoralf-AP: remove all items above as they are done
15. Sunil updates (subteam-h)?
    1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
    2. 2023-05-23: all items from HCL to be moved to I release.
       
    3. 2023-07-18, 2023-08-01: no news
16. Subhash/Naman updates (subteam-s) ?
    1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
       
       1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
          1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
             1. Thoralf to create JIRA item for this
             2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
             3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
             4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
          2. Integration with AI/ML project: kserve_adapter
             1. data pipeline (Hoejoo's e-mail)
                1. 2023-01-31 not discussed in today's meeting
    2. 2023-03-14:
       1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
       2. A1 mediator nanobot integration still under work
    3. 2023-03-28: work continues
       
    4. 2023-04-11: E2 reset work in submgr is now under work.
    5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
    6. 2023-05-09:
       1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
          
       2. A1 bug fixes being almost ready.
       3. A1 mediator nanobot might be delayed.
       4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    7. 2023-05-23
       1. E2 reset (from E2 node): done
       2. KServe adapter still being worked on.
       3. nanobot integration still being worked on.
    8. 2023-07-18: no news, planning for I release
    9. 2023-08-01:
       1. E2AP v3.0 → we took a look at what changes are coming
       2. A1 enhancements
       3. considering upgrade of ubuntu and k8s
       4. deploying RIC and xapps using k8S operator
       5. DMS delete PI
       6. E2 reset from ric to e2 node
17. Abhijit updates (subteam-ag) ?
18. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
    1. Thoralf raised support request to LF. Reminders sent. Still no solution.
2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.

19. 2023-03-28: working on RIC-969 and part of RIC-957
20. 2023-04-11:
    1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
       
    2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
21. 2023-04-25
    1. working on RNIB support in rust (https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10906) and next step hw-rust.
22. 2023-05-09
    1. RIC-977 (subscription API) - pls. merge.
    2. RIC-978 pls. try to complete during this week.
    3. issues with E2 simulator → to get in contact with Naman and Subhash
23. 2023-05-23
    1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
    2. testing of subscriptions using hw-rust (facing the E2T problem)
24. 2023-07-18: no news
25. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
Cap Gemini updates (subteam-cg)? 
1. 2023-03-14
   1. RIC-851 done
   2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
2. 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-23: no news.
3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
   
4. 2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July
5. 2023-08-01

6. Gunja to present conflict management design

thinking about adding support for DU in E2T/E2M/RNIB in I release
26. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-0612-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-01: feedback from Anssi on submgr received and incorporating these changes.
    5. 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.
    6. 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.
27. 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
    Dhiraj (subteam-r)
    
    1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
    2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
    3. 2023-07-18: IPv6 changes to come as review
    4. 2023-08-01: working on it.
28. Alexandre (subteam-utfpr)
    
    1. 2023-0508-23: no news29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-0609-06:
    3. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
    seems also to be a bug in interface name solution in RMR. Remember to create a JIRA item26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
29. Nokia (subteam-n)
    1. GRPC vs RMR
       1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
       2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09, 2023-05-23, 2023-07-18: no update
    2. RIC-997 postponed to J
    3. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
30. 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
    I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I 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. input for release candidates: left overs and generally open items, RSAC
       2. Sprint dates
          1. Sprint G release dev sprint 1: Aug-21 to Sep-10
          2. Sprint G release dev sprint 2: Sep-11 to Oct-1
          3. Sprint G release dev sprint 3: Oct-2 to Oct-22
          4. Sprint G release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
          5. Sprint G release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
       3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
       4. 2023-07-18: Naman proposed E2APv3.0 update and some A1 changes
          1. E2APv3.0 changes for existing functionality (possible item for release I) - to be sent by e-mail.
             1. Dhiraj to be involved.
          2. Changes for A1 to achieve spec compliance (for the URL change we could do it in a backwards compatible way)
          3. E2 Reset from RIC to RAN
       5. 2023-07-18: (Dhiraj) IPv6 changes
       6. 2023-07-18: (Thoralf) RIC Error indication during E2 setup
       7. 2023-07-18: (Dhiraj) (not committed, but can prepare a list on where dynamic log level change is missing)
       8. 2023-08-01: Summary of plans:

          1. E2-related

             1. Near-RT RIC conflict management

             2. Adding support for DU in E2T/E2M/RNIB

             3. Support for E2APv3.0

             4. Support for RIC Query

             5. Support for Subscription modifications

             6. Support for E2 reset from RIC to RAN

             7. Handling of RIC Error indication _during_ E2 setup.

             8. RIC-963 modify src code to be more lenient in ordering of IEs in ASN.1

          2. Other

             1. K8S operators for deploying xApps

             2. A1 alignment with A1AP (still under investigation. Minimum is using correct URL)

             3. DMS Rest API support for deleting/undeploy xApps (DMS REST is 2nd ifc addressing same space as dmscli)

             4. IPv6 support for RMR

             5. Support for only-IPv6 in RIC-internal interfaces

    2. RICAPP agenda: RICAPP Meetings.

    2023-07-18

    Recording: link to zoom recording
    

    1. 1. 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)
    4. 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-04-11
          
          1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
    5. 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
    6. Every time: Check if there are new bug reports in JIRA: link
       1. new: RIC-989 rmr (minor) security issue
       2. new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 
       3. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile
       4. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
       5. RIC-972 URL for A1 mediator to align with spec.
       6. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
       7. 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)
       8. RIC-915 dms_cli for installing xapp not working (raised by James)
       9. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       10. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMANDRIC-897 SCTP connection fails with Viavi // update with workaround
       11. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       12. RIC-894 long idle period (days) causes RMR connection breaks
       13. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       14. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       15. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.2021-12-21: Trying to get bandwidth for this during F releaseresponse.
       16. RIC-837 RMR is not forwarding messages from E2T to E2M
       17. RIC-835 → 2021-12-07 no news from Viktor
       18. fixed: 
           
    7. James: updates?
       1. 2023-01-31:
          1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
          2. Subhash asked for a wiki page documenting this work.
          3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
             1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
             2. Tacker-based deployment needs to be checked.
       2. 2023-03-14, 2023-03-28 : no news
       3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
       4. 2023-04-25: no updates
       5. 2023-05-09:
          1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
             1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
             2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
             3. Input from other subprojects, incl. our near-RT RIC project?
          2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
       6. 2023-05-23 → no news
       7. 2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/
          1. usage of robot test cases (from it/test) is still something that James is thinking about.
          2. Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.
       8. 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.
       9. 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.
       10. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    8. Prashant's work in near-RT RIC(subteam-p)
       1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    9. 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
    10. 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
    11. 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 
              
        Prashant's work in near-RT RIC
        1. 2023-04-25:
           1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
           2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
           3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
        2. 2023-05-09
           1. question related to O1 (for stats handling without Vespa) - see RIC-798
        3. 2023-05-23
           1. no progress in review on the plain helm chart based deployment in
           2. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1ric-dep/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
           3. E2 → Alexandre to review - 2023-06-06: merged
        4. 2023-06-06: Prashant posted in O-RAN WG3 on O1 a question related on the why of notifications + SFTP. No reply yet.
           1. 2023-07-18: feedback was that this is a 3GPP issue. Not further following up on this.
        5. 2023-06-18: Thoralf-AP: remove all items above as they are done
    12. Sunil updates?
        1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
        2. 2023-05-23: all items from HCL to be moved to I release.
           
        3. 2023-07-18: no news
    13. Subhash/Naman updates?
        1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
           
           1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
              1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
                 1. Thoralf to create JIRA item for this
                 2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
                 3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
                 4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
              2. Integration with AI/ML project: kserve_adapter
                 1. data pipeline (Hoejoo's e-mail)
                    1. 2023-01-31 not discussed in today's meeting
        2. 2023-03-14:
           1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
           2. A1 mediator nanobot integration still under work
        3. 2023-03-28: work continues
           
        4. 2023-04-11: E2 reset work in submgr is now under work.
        5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
        6. 2023-05-09:
           1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
              
           2. A1 bug fixes being almost ready.
           3. A1 mediator nanobot might be delayed.
           4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
        7. 2023-05-23
           1. E2 reset (from E2 node): done
           2. KServe adapter still being worked on.
           3. nanobot integration still being worked on.
        8. 2023-07-18: no news, planning for I release
    Abhijit updates?
    14. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
        1. Thoralf raised support request to LF. Reminders sent. Still no solution.
    2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
    
    15. 2023-03-28: working on RIC-969 and part of RIC-957
    16. 2023-04-11:
        1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
           
        2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
    17. 2023-04-25
        1. working on RNIB support in rust (https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10906) and next step hw-rust.
    18. 2023-05-09
        1. RIC-977 (subscription API) - pls. merge.
        2. RIC-978 pls. try to complete during this week.
        3. issues with E2 simulator → to get in contact with Naman and Subhash
    19. 2023-05-23
        1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
        2. testing of subscriptions using hw-rust (facing the E2T problem)
    20. 2023-07-18: no news
    21. Cap Gemini updates? 
        1. 2023-03-14
           1. RIC-851 done
           2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
        2. 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-23: no news.
        3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
           
        4. 2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July
    22. Himanshu would like to work on RIC-963
        
        1. code changes, but difficult to test as difficult to change order of IEs in message.
        2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
        3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    23. Dhiraj
        1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
        2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
        3. 2023-07-18: IPv6 changes to come as review
    24. Alexandre
        1. 2023-05-23: no news
        2. 2023-06-06:
           1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
           2. seems also to be a bug in interface name solution in RMR. Remember to cretae a JIRA item
    25. 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.
        2. input for release candidates: left overs and generally open items, RSAC
        3. Sprint dates
           1. Sprint G release dev sprint 1: Aug-21 to Sep-10
           2. Sprint G release dev sprint 2: Sep-11 to Oct-1
           3. Sprint G release dev sprint 3: Oct-2 to Oct-22
           4. Sprint G release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
           5. Sprint G release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
        4. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
        5. 2023-07-18: Naman proposed E2APv3.0 update and some A1 changes
           1. E2APv3.0 changes for existing functionality (possible item for release I) - to be sent by e-mail.
              1. Dhiraj to be involved.
           2. Changes for A1 to achieve spec compliance (for the URL change we could do it in a backwards compatible way)
           3. E2 Reset from RIC to RAN
        6. 2023-07-18: (Dhiraj) IPv6 changes
        7. 2023-07-18: (Thoralf) RIC Error indication during E2 setup
        8. 2023-07-18: (Dhiraj) (not committed, but can prepare a list on where dynamic log level change is missing)
    26. GRPC vs RMR
        1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
        2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09, 2023-05-23, 2023-07-18: no update
    27. RICAPP agenda: RICAPP Meetings.

    2023-07-04

    Since neither Thoralf nor Sunil can host this meeting it is cancelled.

    2023-06-20

    we did the demo meeting in the timeslot: link

    2023-06-06

    Recording: partial-only: link to zoom recording
    

    1. 1. 1. 11743 → to be merged by Thoralf Czichy 
             
          2. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
          3. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
       2. 2024-01-16, 2024-01-30: No news.
    2. Cap Gemini updates (subteam-cg)? 
       1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
       2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 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.
    4. 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.
    5. Alexandre (subteam-utfpr)
       
       1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
       2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    6. Nokia (subteam-n)
       1. RIC-997 postponed to J
    7. 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
    4. 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-04-11
          
          1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
    5. 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
    6. Every time: Check if there are new bug reports in JIRA: link
       1. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile
       2. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
       3. RIC-974 done: Errors running example ping/pong application in `xapp-frame-py`, incl. new release of builder image. Can be closed after that.
       4. RIC-972 URL for A1 mediator to align with spec.
       5. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
       6. 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)
       7. RIC-915 dms_cli for installing xapp not working (raised by James)
       8. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       9. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
       10. RIC-897 SCTP connection fails with Viavi // update with workaround
       11. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       12. RIC-894 long idle period (days) causes RMR connection breaks
       13. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       14. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       15. 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.
       16. RIC-837 RMR is not forwarding messages from E2T to E2M
       17. RIC-835 → 2021-12-07 no news from Viktor
       18. fixed: RIC-974, RIC-980, RIC-981
           
    7. H release status page: H Release#Near-Real-timeRANIntelligentControllerPlatform(E2Interface)(RICPLT) → 2023-06-06 we checked the status
       1. Thoralf expects everything to be ready by Jun-22
    8. O-RAN SC end of release of near-RT RIC: Demo scheduled for 2 weeks from now: 2023-06-20 Release H
    9. Demo videos (Prashant, Subhash, Gunja) for O-RAN face-to-face to be ready this week: upload video here: Material for O-RAN June f2f in Osaka  Jinri will combine

    2022-12-13, 2023-01-17: Bin Yang asked about O2 for RIC platform deployment and xapp deployment. Need to discuss on this topic. O-cloud is deployed in AT&T and Taiwan lab.

    10. The current platform deployment scripts might not be in line with O2 envisions
    11. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    12. O2-D(MS) is relevant to RIC platform.
    13. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    14. 2023-01-31: No news yet
    15. 2023-02-14: No news yet, Thoralf received e-mail on this from James. Still to check.
    16. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
    17. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
    2023-03-28:no news
    18. 2023-04-11: Tacker team provided ideas on SMO architecture (in context of RSAC). No immediate action items for Near-RT RIC platform project
    19. 2023-04-25, 2023-05-09, 2023-05-23: no news
    20. James: updates?
        1. 2023-01-31:
           1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
           2. Subhash asked for a wiki page documenting this work.
           3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
              1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
              2. Tacker-based deployment needs to be checked.
        2. 2023-03-14, 2023-03-28 : no news
        3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
        4. 2023-04-25: no updates
        5. 2023-05-09:
           1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
              1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
              2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
              3. Input from other subprojects, incl. our near-RT RIC project?
           2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
        6. 2023-05-23 → no news
    21. Prashant's work in near-RT RIC
        1. 2023-04-25:
           1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
           2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
           3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
        2. 2023-05-09
           1. question related to O1 (for stats handling without Vespa) - see RIC-798
        3. 2023-05-23https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
        4. E2 → Alexandre to review - 2023-06-06: merged
        5. 2023-06-06: Prashant posted in O-RAN WG3 on O1 a question related on the why of notifications + SFTP. No reply yet.
    22. Sunil updates?
        1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
        2. 2023-05-23: all items from HCL to be moved to I release.
           
    23. Subhash/Naman updates?
        1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
           
           1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
              1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
                 1. Thoralf to create JIRA item for this
                 2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
                 3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
                 4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
              2. Integration with AI/ML project: kserve_adapter
                 1. data pipeline (Hoejoo's e-mail)
                    1. 2023-01-31 not discussed in today's meeting
        2. 2023-03-14:
           1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
           2. A1 mediator nanobot integration still under work
        3. 2023-03-28: work continues
           
        4. 2023-04-11: E2 reset work in submgr is now under work.
        5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
        6. 2023-05-09:
           1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
              
           2. A1 bug fixes being almost ready.
           3. A1 mediator nanobot might be delayed.
           4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
        7. 2023-05-23
           1. E2 reset (from E2 node): done
           2. KServe adapter still being worked on.
           3. nanobot integration still being worked on.
    Abhijit updates?
    24. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
        1. Thoralf raised support request to LF. Reminders sent. Still no solution.
    2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
    
    25. 2023-03-28: working on RIC-969 and part of RIC-957
    26. 2023-04-11:
        1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
           
        2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
    27. 2023-04-25
        1. working on RNIB support in rust (https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10906) and next step hw-rust.
    28. 2023-05-09
        1. RIC-977 (subscription API) - pls. merge.
        2. RIC-978 pls. try to complete during this week.
        3. issues with E2 simulator → to get in contact with Naman and Subhash
    29. 2023-05-23
        1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
        2. testing of subscriptions using hw-rust (facing the E2T problem)
    30. Cap Gemini updates? 
        1. 2023-03-14
           1. RIC-851 done
           2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
        2. 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-23: no news.
        3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
           
    31. Himanshu would like to work on RIC-963
        
        1. code changes, but difficult to test as difficult to change order of IEs in message.
        2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    32. Dhiraj
        1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
        2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed). 
    33. Alexandre
        1. 2023-05-23: no news
        2. 2023-06-06:
           1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
           2. seems also to be a bug in interface name solution in RMR. Remember to cretae a JIRA item.
    34. H release content
        
        1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
        2. Sprint dates
           1. Sprint H release dev sprint 1: Feb-20´to Mar-12
           2. Sprint H release dev sprint 2: Mar-13 to Apr-2
           3. Sprint H release dev sprint 3: Apr-3 to Apr-23
           4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
           5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
        3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
    35. GRPC vs RMR
        1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
        2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09, 2023-05-23: no update
    36. RICAPP agenda: RICAPP Meetings.

    2023-05-23

    Recording: link to zoom recording
    

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

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

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

          3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
          4. TODO-thoralf-to-ask-Gunja-to-present- Thoralf
    8. Himanshu (subteam-gs) would like to work on RIC-963
       
       1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
       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.
    9. 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
    10. Alexandre (subteam-utfpr)
        
        1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
        2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    11. Nokia (subteam-n)
        1. RIC-997 postponed to J
    12. 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.
           
    13. 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".
    11. 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-04-11
           
           1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
    12. 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
    13. Every time: Check if there are new bug reports in JIRA: link
        1. RIC-980 new-and-doneNaman Reading Configuration for rmr from config file
        2. RIC-981 new-and-doneNaman Missing health check checking the Db connection through SDL even when the a1 name space is not present in db
        3. RIC-979 Decode Error with e2sim on e2term Pod - AP-Subhash/Naman add logs
        4. RIC-974 done: Errors running example ping/pong application in `xapp-frame-py`, incl. new release of builder image. Can be closed after that.
        5. RIC-972 URL for A1 mediator to align with spec.
        6. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
        7. 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)
        8. RIC-915 dms_cli for installing xapp not working (raised by James)
        9. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
        10. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
        11. RIC-897 SCTP connection fails with Viavi // update with workaround
        12. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
        13. RIC-894 long idle period (days) causes RMR connection breaks
        14. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
        15. RIC-857 sporadically RMR takes multiple minutes before being "ready"
        16. 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.
        17. RIC-837 RMR is not forwarding messages from E2T to E2M
        18. RIC-835 → 2021-12-07 no news from Viktor
        19. fixed: RIC-974, RIC-980, RIC-981
            

    2022-12-13, 2023-01-17: Bin Yang asked about O2 for RIC platform deployment and xapp deployment. Need to discuss on this topic. O-cloud is deployed in AT&T and Taiwan lab.

    14. The current platform deployment scripts might not be in line with O2 envisions
    15. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    16. O2-D(MS) is relevant to RIC platform.
    17. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    18. 2023-01-31: No news yet
    19. 2023-02-14: No news yet, Thoralf received e-mail on this from James. Still to check.
    20. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
    21. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
    2023-03-28:no news
    22. 2023-04-11: Tacker team provided ideas on SMO architecture (in context of RSAC). No immediate action items for Near-RT RIC platform project
    23. 2023-04-25, 2023-05-09, 2023-05-23: no news
    24. Prashant's work in near-RT RIC
        1. 2023-04-25:
           1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
           2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
           3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
        2. 2023-05-09
           1. question related to O1 (for stats handling without Vespa) - see RIC-798
        3. 2023-05-23
           1. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11127?usp=search and two more minor ones to be reviewed Naman/Subhash during this week
           2. E2 → Alexandre to review
    25. James: updates?
        1. 2023-01-31:
           1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
           2. Subhash asked for a wiki page documenting this work.
           3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
              1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
              2. Tacker-based deployment needs to be checked.
        2. 2023-03-14, 2023-03-28 : no news
        3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
        4. 2023-04-25: no updates
        5. 2023-05-09:
           1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
              1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
              2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
              3. Input from other subprojects, incl. our near-RT RIC project?
           2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
        6. 2023-05-23 → no news
    26. Sunil updates?
        1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no news
        2. 2023-05-23: all items from HCL to be moved to I release.
           
    27. Subhash/Naman updates?
        1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
           
           1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
              1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
                 1. Thoralf to create JIRA item for this
                 2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
                 3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
                 4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
              2. Integration with AI/ML project: kserve_adapter
                 1. data pipeline (Hoejoo's e-mail)
                    1. 2023-01-31 not discussed in today's meeting
        2. 2023-03-14:
           1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
           2. A1 mediator nanobot integration still under work
        3. 2023-03-28: work continues
           
        4. 2023-04-11: E2 reset work in submgr is now under work.
        5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
        6. 2023-05-09:
           1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
              
           2. A1 bug fixes being almost ready.
           3. A1 mediator nanobot might be delayed.
           4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
        7. 2023-05-23
           1. E2 reset (from E2 node): done
           2. KServe adapter still being worked on.
           3. nanobot integration still being worked on.
    28. Abhijit updates?
        1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
           1. Thoralf raised support request to LF. Reminders sent. Still no solution.
        2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
        
        2. 2023-03-28: working on RIC-969 and part of RIC-957
        3. 2023-04-11:
           1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
              
           2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
        2023-04-25working on RNIB support in rust (
        4. 2023-11-07: addressing review comments of
        5. https://gerrit.o-ran-sc.org/r/c/ric-plt/
        xapp-frame-rust
        6. submgr/+/
        10906) and next step hw-rust.
        7. 2023-05-09
           1. RIC-977 (subscription API) - pls. merge.
           2. RIC-978 pls. try to complete during this week.
           3. issues with E2 simulator → to get in contact with Naman and Subhash
        8. 2023-05-23
           1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
           2. testing of subscriptions using hw-rust (facing the E2T problem)
    29. Cap Gemini updates? 
        1. 2023-03-14
           1. RIC-851 done
           2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
        2. 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-23: no news.
        3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
           
    30. Himanshu would like to work on RIC-963
        
        1. code changes, but difficult to test as difficult to change order of IEs in message.
    31. Dhiraj
        1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
    32. Alexandre
        1. 2023-05-23: no news
    33. 1. 11681 tomorrow. Then we should be able to merge this.
        2. 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.
    34. 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

    35. 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
    36. Nokia (subteam-n)
        1. .RIC-997 likely being postponed.
    37. I H release content
    1. 1. we mark items that you are >90% sure (=”committed”) to work on during
    1H2023
    2. 1. 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for
    H
    3. 1. 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.
    4. Sprint dates
       1. Sprint H release dev sprint 1: Feb-20´to Mar-12
       2. Sprint H release dev sprint 2: Mar-13 to Apr-2
       3. Sprint H release dev sprint 3: Apr-3 to Apr-23
       4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
       5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    5. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
    GRPC vs RMR
    6. 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.
    7. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09, 2023-05-23: no update
    8. 1. 1. 
             

    9. 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-0409-1126
          
          1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rustsubmgr/+/10906 OK tests includedhttps://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/10907 OK, tests included11681 ok, (not yet merged)
          2. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11023 OK, tests included11889 ok. included test cases
          3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rustricdms/+/10918 OK, as files are generated11999 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 20222023-05-27, 2022-11-22, 2023-03-28, 2023-04-1123:  we did not do this this time
    3. Every time: Check if there are new bug reports in JIRA: link
       1. RIC-974 Errors running example ping/pong application in `xapp-frame-py`, incl. new release of builder image. Can be closed after that.
       2. RIC-972 URL for A1 mediator to align with spec.
       3. DONE: RIC-971 Fix potential segfaults and double free corruption (in E2T)
       4. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
       5. 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)
       6. RIC-915 dms_cli for installing xapp not working (raised by James)
       7. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
       8. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
       9. RIC-897 SCTP connection fails with Viavi // update with workaround
       10. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
       11. RIC-894 long idle period (days) causes RMR connection breaks
       12. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
       13. RIC-857 sporadically RMR takes multiple minutes before being "ready"
       14. 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.
       15. RIC-837 RMR is not forwarding messages from E2T to E2M
       16. RIC-835 → 2021-12-07 no news from Viktor
       17. fixed: RIC-971
           

       2022-12-13, 2023-01-17: Bin Yang asked about O2 for RIC platform deployment and xapp deployment. Need to discuss on this topic. O-cloud is deployed in AT&T and Taiwan lab.

    4. The current platform deployment scripts might not be in line with O2 envisions
    5. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    6. O2-D(MS) is relevant to RIC platform.
    7. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    8. 2023-01-31: No news yet
    9. 2023-02-14: No news yet, Thoralf received e-mail on this from James. Still to check.
    10. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
    11. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
    2023-03-28:no news
    12. 2023-04-11: Tacker team provided ideas on SMO architecture (in context of RSAC). No immediate action items for Near-RT RIC platform project
    13. 2023-04-25, 2023-05-09: no news
    14. Prashant's work in near-RT RIC
        1. 2023-04-25:
           1. Prashant updated call flow for A1 polciy status update. Will send it for review RIC-973.
           2. Prashant, pls. create JIRA item for the Golang implementation related to policytypes: RIC-975 → DONE
           3. Prashant, pls. create JIRA item for the SCTP E2 timeout change.  RIC-976 Three reviews, but only one is valid
        2. 2023-05-09
           1. question related to O1 (for stats handling without Vespa) - see RIC-798
    15. James: updates?
        1. 2023-01-31:
           1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
           2. Subhash asked for a wiki page documenting this work.
           3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
              1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
              2. Tacker-based deployment needs to be checked.
        2. 2023-03-14, 2023-03-28 : no news
        3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
        4. 2023-04-25: no updates
        5. 2023-05-09:
           1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
              1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
              2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
              3. Input from other subprojects, incl. our near-RT RIC project?
           2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    16. Sunil updates?
        1. 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25: no news
        2. 2023-05-09 no news
           
    17. Subhash/Naman updates?
        1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
           
           1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
              1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
                 1. Thoralf to create JIRA item for this
                 2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
                 3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
                 4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
              2. Integration with AI/ML project: kserve_adapter
                 1. data pipeline (Hoejoo's e-mail)
                    1. 2023-01-31 not discussed in today's meeting
        2. 2023-03-14:
           1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
           2. A1 mediator nanobot integration still under work
        3. 2023-03-28: work continues
           
        4. 2023-04-11: E2 reset work in submgr is now under work.
        5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
        6. 2023-05-09:
           1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
              
           2. A1 bug fixes being almost ready.
           3. A1 mediator nanobot might be delayed.
           4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    18. 1. 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
            
    19. 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
    20. Prashant's work in near-RT RIC(subteam-p)
        1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    21. 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
    22. 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
    23. 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.
    24. 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
    25. 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".
        Abhijit updates?
        1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
           1. Thoralf raised support request to LF. Reminders sent. Still no solution.
        2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
        
        2. 2023-03-28: working on RIC-969 and part of RIC-957
        3. 2023-04-11:
           1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
              
           2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
        2023-04-25working on RNIB support in rust (
        4. 2023-11-07: addressing review comments of
        5. https://gerrit.o-ran-sc.org/r/c/ric-plt/
        xapp-frame-rust
        6. submgr/+/
        10906) and next step hw-rust.
        7. 2023-05-09
           1. RIC-977 (subscription API) - pls. merge.
           2. RIC-978 pls. try to complete during this week.
           3. issues with E2 simulator → to get in contact with Naman and Subhash
    26. Cap Gemini updates? 
        1. 2023-03-14
           1. RIC-851 done
           2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
        2. 2023-03-28, 2023-04-11, 2023-04-25: no news.
        3. 2023-05-09 no news.
    27. Himanshu would like to work on RIC-963
        
        1. code changes, but difficult to test as difficult to change order of IEs in message.
    28. 1. 11681 tomorrow. Then we should be able to merge this.
    29. 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

    30. 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
    31. Nokia (subteam-n)
        1. ...
    32. I H release content
    1. 1. we mark items that you are >90% sure (=”committed”) to work on during
    1H2023
    2. 1. 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for
    H
    3. 1. 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
    4. 1. conventions.
       2. input for release candidates: left overs and generally open items, RSAC
    .
    5. 2. Sprint dates
          1. Sprint
    H
    6. 1. 1. I release dev sprint 1:
    Feb-20´to Mar-12
    7. 1. 1. Aug-21 to Sep-10
          2. Sprint
    H
    8. 1. 1. I release dev sprint 2:
    Mar
    9. 1. 1. Sep-
    13
    10. 1. 1. 11 to
    Apr
    11. 1. 1. Oct-
    2
    12. 1. 1. 1
           2. Sprint
    H
    13. 1. 1. I release dev sprint 3:
    Apr
    14. 1. 1. Oct-
    3
    15. 1. 1. 2 to
    Apr
    16. 1. 1. Oct-
    23
    17. 1. 1. 22
           2. Sprint
    H
    18. 1. 1. I release dev sprint 4:
    Apr
    19. 1. 1. Oct-
    24
    20. 1. 1. 23 to
    May
    21. 1. 1. Nov-
    14
    22. 1. 1. 12 (last planned development sprint)
           2. Sprint
    H
    23. 1. 1. I release dev sprint 5:
    May
    24. 1. 1. Nov-
    15
    25. 1. 1. 13 to
    Jun
    26. 1. 1. Dec-
    4
    27. 1. 1. 3 (only for unplanned last-minute development items)
    28. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
    GRPC vs RMR
    29. 1. Plan (v03 as of 2023-08-18):
           1. I release plan moved to I release page.
    30. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28, 2023-04-11, 2023-04-25, 2023-05-09: no update
    32. RICAPP agenda: RICAPP Meetings.

    ...