2025 06 12

Recording 

Meeting Recording:

Agenda

• Scribe: David Kinsey (AT&T)

• Previous scribe: 

  • 2025 => June: AT&T; May: Nokia; April: NTT Docomo; March: DTAG; February: China Mobile; January: Viavi2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes  May 29, 2025 Jun 5, 2025

   3. Next Meeting Jun 19, 2025 

   4. Release Update

      1. New repo requests

         1. 05-08: AIMLFW repository approved by TOC

   5. New business

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. Tooling budget update 

      2. SCCL enforcement

   7. Old Business

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision:  Lack of Quorum Meeting minutes not reviewed

3. Release

   1. 06-05: Release Vote 06-26 TOC Meeting

   2. 06-05: RSAC will work with PTLs to complete release highlights

   3. 05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.

   4. 05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.

   5. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 05-29: Some strategies to work on CVE’s -

         1. companies using OSC code in their product would solve these CVE issues, to comply by providing the same fixes in OSC too.

         2. Scanning and reporting of CVE’s is welcome, however the fixing of CVE’s is not guaranteed.

         3. Scanning code based on the production code rather than the prototype code.

         4. For maintainablity, common/production base image could be regularly updated by LF.

         5. Document all the CVE’s raised with a Jira possibly. PTL’s to check and analyse the reports for thier respective projects.

      2. 05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.

      3. 05-15: Need some actions on this. Waiting for David .

   2. Rutgers Access Policies

      1. 05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.

   3. k8s version deprecation

      1. 05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. OSFG updates:

      1. Workshop:

         1. 06-05: 2nd Workshop outline from OSFG, looking for 2-day venue and date in September.

         2. 05-29: Workshop updates like potential open source projects that are interested, issues with addressing CVE’s in open src,LF projects working with ORAN can attend ORAN events post approvals.

         3. 05-22: Workshop is on 05-23.

      2. O-RAN SCCL enforcement:

         1. 06-05: OSARP reviewed by OCOP. Some comments taken, edits in progress.

         2. 06-05: Document might be ready to be approved by July Train but WGs won’t be able to adopt it in time. Therefore, looking for post July Train completion and adoption.

         3. 06-05: Might be able to take a copy early if merged into the main branch by the WG. License has to be applied by O-RAN before a copy can be taken.

         4. 05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc

   2. IEEE GLOBECOM 2025 O-RAN workshop

      1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

   3. ORAN Tooling

      1. 06-05: O-RAN CFO needs to understand the business value of open source

      2. 05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.

   4. OSC/OSFG Update for TSC

      1. 06-05: Deck reviewed and updated

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

      1. 05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .

      2. 05-08: Panels reservation required. Need to check further.

7. Old Business

   1. RSAC co-chair

      1. 04-17: no update; still looking for. 

   2. Project Updates

      1. RSAC -  @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.

         2. 05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   3. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work

      1. 05-15: No updates.

   4. Internship update

8. Meeting Summary and Closure

• Next Meeting Jun 19, 2025 starts by 18:15

2025 06 05

Recording 

Meeting Recording:

Agenda

• Scribe: David Kinsey (AT&T)

• Previous scribe: 

  • 2025 => June: AT&T; May: Nokia; April: NTT Docomo; March: DTAG; February: China Mobile; January: Viavi

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes  May 29, 2025 

   3. Next Meeting Jun 12, 2025 

   4. Release Update

      1. New repo requests

         1. 05-08: AIMLFW repository approved by TOC

   5. New business

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. Tooling budget update 

      2. SCCL enforcement

   7. Old Business

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision:  Lack of Quorum Meeting minutes not reviewed

3. Release

   1. 06-05: Release Vote 06-26 TOC Meeting

   2. 06-05: RSAC will work with PTLs to complete release highlights

   3. 05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.

   4. 05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.

   5. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 05-29: Some strategies to work on CVE’s -

         1. companies using OSC code in their product would solve these CVE issues, to comply by providing the same fixes in OSC too.

         2. Scanning and reporting of CVE’s is welcome, however the fixing of CVE’s is not guaranteed.

         3. Scanning code based on the production code rather than the prototype code.

         4. For maintainablity, common/production base image could be regularly updated by LF.

         5. Document all the CVE’s raised with a Jira possibly. PTL’s to check and analyse the reports for thier respective projects.

      2. 05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.

      3. 05-15: Need some actions on this. Waiting for David .

   2. Rutgers Access Policies

      1. 05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.

   3. k8s version deprecation

      1. 05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. OSFG updates:

      1. Workshop:

         1. 06-05: 2nd Workshop outline from OSFG, looking for 2-day venue and date in September.

         2. 05-29: Workshop updates like potential open source projects that are interested, issues with addressing CVE’s in open src,LF projects working with ORAN can attend ORAN events post approvals.

         3. 05-22: Workshop is on 05-23.

      2. O-RAN SCCL enforcement:

         1. 06-05: OSARP reviewed by OCOP. Some comments taken, edits in progress.

         2. 06-05: Document might be ready to be approved by July Train but WGs won’t be able to adopt it in time. Therefore, looking for post July Train completion and adoption.

         3. 06-05: Might be able to take a copy early if merged into the main branch by the WG. License has to be applied by O-RAN before a copy can be taken.

         4. 05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc

   2. IEEE GLOBECOM 2025 O-RAN workshop

      1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

   3. ORAN Tooling

      1. 06-05: O-RAN CFO needs to understand the business value of open source

      2. 05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.

   4. OSC/OSFG Update for TSC

      1. 06-05: Deck reviewed and updated

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

      1. 05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .

      2. 05-08: Panels reservation required. Need to check further.

7. Old Business

   1. RSAC co-chair

      1. 04-17: no update; still looking for. 

   2. Project Updates

      1. RSAC -  @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.

         2. 05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   3. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work

      1. 05-15: No updates.

   4. Internship update

8. Meeting Summary and Closure

• Next Meeting Jun 12, 2025

2025 05 29

Recording 

Meeting Recording: link

Agenda

• Scribe: @abdulwahid.w  (Nokia)

• Previous scribe: 

  • 2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes  May 22, 2025 

   3. Next Meeting Jun 5, 2025 

   4. Release Update

      1. New repo requests

         1. 05-08: AIMLFW repository approved by TOC

   5. New business

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. Tooling budget update 

      2. SCCL enforcement

   7. Old Business

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision: @Ankit Barve Motion to Approve; Seconded by @David Kinsey [AT&T] . No Objections. May 29, 2025  Minutes approved. 

3. Release

   1. 05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.

   2. 05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.

   3. 04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf

   4. 04-03: @Sally Cooper : PR has been approved. PR will post  Apr 3, 2025

   5. 03-27: @Sally Cooper: waiting for the last approval from Intel, but it should come in. Logo solved.

   6. 03-20: not all input from PTLs received. Discussion about objective continues. Most of the project participating in RSAC knows what to do, but it needs to be documented.

   7. 03-13: Schedule under L-Release Timeline - Releases - Confluence/Wiki. We are finishing sprint 1. PLT asked to update the objectives.

   8. 03-06: No news. Next release planned for June, following 3 releases per year.

   9. Release Votes (checklist) and Approval

   10. New repo request

       1. 04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by  @James Li; No objections. Motion was carried.

       2. 04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.

   11. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 05-29: Some strategies to work on CVE’s -

         1. companies using OSC code in their product would solve these CVE issues, to comply by providing the same fixes in OSC too.

         2. Scanning and reporting of CVE’s is welcome, however the fixing of CVE’s is not guaranteed.

         3. Scanning code based on the production code rather than the prototype code.

         4. For maintainablity, common/production base image could be regularly updated by LF.

         5. Document all the CVE’s raised with a Jira possibly. PTL’s to check and analyse the reports for thier respective projects.

      2. 05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.

      3. 05-15: Need some actions on this. Waiting for David .

      4. 04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.

      5. 03-27: @Martin Skorupski page Common Vulnerabilities and Exposures (CVE) updated with status column. @Sridhar Rao will also improve the LNF scans as we go from Jenkins to Gitlab actions. The scan will work only on build. Infrastructure is there (https://github.com/lfit/releng-reusable-workflows ) and open to anyone who wants to try it.

      6. 03-20: @Martin Skorupski there is a table at RSAC wiki with status. In discussion with PTLs. Will add columns for release when CVE was discovered and resolved. 

      7. 03-12: @Martin Skorupski: feedback period running. @David Kinsey [AT&T]: maybe it is too general, some CVEs were already closed. Someone should look at the new CVEs. If something is corrected, it should be mentioned in our release notes. The CVD process of O-RAN covers the update of CVE status in the database. We need just to report the updates to O-RAN.

      8. 03-12: @Jakub Novy [DTAG]: do we have a statement in OSC's code that we provide it "as is"? @David Kinsey [AT&T] / @Martin Skorupski: it is in both licenses we are using.

      9. 03-06: From WG11 towards OSC. There is a new CVE discovered (CVE-2024-34035, CVE-2024-34036). WG11 asks position of OSC regarding CVEs. @Martin Skorupski: we are contribution driven, so we cannot guarantee that it will be fixed. Draft of the statement is here: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333381634/Common+Vulnerabilities+and+Exposures+CVE. @Martin Skorupski to share via mail and TOC to approve next week(s).

   2. Rutgers Access Policies

      1. 03-06: @Martin Skorupski: Request for AccessPolicies by Rutgers (new O-RAN-SC Lab): draft answer to 4 questions here:  OWL- Open Wireless Lab#O-RAN-SC-Access-and-Use-Policy

         1. @Tracy Van Brakle: Keysight and Viavi wants to have a special ID to track the usage of their tools. @Martin Skorupski:How should be the access approved? By OSC TOC.

      2. 03-13: access list here: OWL- Open Wireless Lab - Requirements and Software Architecture Committee - Confluence/Wiki, not yet fully implemented.

      3. 05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.

   3. k8s version deprecation

      1. 05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. 04-24:  @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.

   2. 04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.

   3. 04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.

   4. 03-27: @David Kinsey [AT&T] no update about tooling, will provide next week.

   5. 03-27: @Sridhar Rao logo now fixed.

   6. 03-20: @Sridhar Rao there is an O-RAN logo at http://docs.o-ran-sc.org . @David Kinsey [AT&T] It is there since beginning. If O-RAN does not approve it, we can change it. @James Li to reach out to PTL for DOC project, Wichen Ni

   7. 03-06: @Tracy Van Brakle OSC development efforts in Rutgers will be supported by new tools (O-RU, RICtest). Finalizing the procurement with O-RAN office now.

   8. OSFG updates:

      1. Workshop:

         1. 05-29: Workshop updates like potential open source projects that are interested, issues with addressing CVE’s in open src,LF projects working with ORAN can attend ORAN events post approvals.

         2. 05-22: Workshop is on 05-23.

         3. 04-24: registration was requested if attend to OAI workshop either in person of remotely.

         4. 04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.

         5. 04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.

         6. 04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista; 

         7. 03-27: workshop will be in Kista, Irfan and John will be present, not David. Local contact known to align details. David will share the agenda with Sridhar. John will manage the booking of a room.

         8. 03-20: @Sridhar Rao will reach to other LNF projects if they are interested if the date is decided. @David Kinsey [AT&T] if its in Kista, then the date is set. It is not sure if its full day/half day. @Sridhar Rao will make a poll to see who from OSC can join on 23rd of May. @James Li will add a topic on Monday's OSFG call to prepare a paragraph about it which Sridhar can share with other projects.

         9. 03-20: @David Kinsey [AT&T]can send a mail to reflector about the possible topics. Will push at OSFG. No other update.

         10. 03-13: currently three options, see below. 

         11. OAI workshop

             1. 04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.

             2. 03-13: @David Kinsey [AT&T] May 21-22 (Wed-Thu) in Kista, Sweeden. If we would be present, we need to start preparing the line-up. So far we do not have the confirmation from various communities if they can attend - deadline is in two weeks, it will be difficult to manage. https://openairinterface.org/summer-2025-workshop-the-openairinterface-path-to-ai-driven-6g/  

             3. 03-13: @John Keeney (Ericsson EST) might be able to secure an Ericsson location in Kista.

         12. Open Source workshop:

             1. 03-13: Other option is to join the LNF at end of June in Denver. We would still need to work on it soon. https://events.linuxfoundation.org/open-source-summit-north-america/

             2. 03-06: @Tracy Van Brakle we should discuss demos with OAI and Nephio - better to wait for David and Irfan to be back

         13. Workshop at O-RAN F2F

             1. 03-13: Possible, It will be difficult to collocate due to large overlap with other O-RAN meetings. OSC co-chairs are also active in the WGs as well as many of the TOC members.

      2. O-RAN SCCL enforcement:

         1. 05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc

         2. 04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed. 

         3. 04-17: @Jakub Novy [DTAG] in progress, trying to get closed.

         4. 03-20: @Jakub Novy [DTAG]: still waiting for O-RAN legeal, OCOP clarifications.

         5. 03-13: @Jakub Novy [DTAG]: in progress, pending confirmation from O-RAN legal.

         6. 03-06: @Jakub Novy [DTAG]: in progress, received feedback during F2F, demo repo prepared, OSARP document is under development.

      3. Collaboration with OAI (lab interconnection) and Nephio

         1. 03-20: @Martin Skorupski OAI and Nephio artifacts are already in one lab in France, so it works.

         2. 03-06: no update

      4. OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.

         1. 03-06: no update

      5.  Face-to-Face Meeting

         1. 03-06: Jinri: good event. We discussed the collaboration with standardization part, workshop, there were on-site and on-line demos. Next F2F planned for June.

   9. 3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination

      1. 04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system. 

   10. IEEE GLOBECOM 2025 O-RAN workshop

       1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

   11. ORAN Tooling

       1. 05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

      1. 05-08: Panels reservation required. Need to check further.

      2. 05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .

7. Old Business

   1. RSAC co-chair

      1. 04-17: no update; still looking for. 

      2. 04-10: no update. still looking for a new RSAC co-chair.

   2. 03-20: still looking for a new RSAC co-chair.

   3. 02-13: RSAC: We'll begin that solicitation today for another RSAC co-chair, as Ritwick confirmed this week he doesn't have the capacity to continue. Anybody who wants to self nominate or knows somebody that would be interested can propose

   4. Project Updates

      1. RSAC - @Rittwik Jana or @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.

         2. 05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.

         3. 04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.

         4. 04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.

         5. 04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)

         6. 03-27: @bimo fransiscus asisi: There is a Discussion End-to-End Integration page to have end-to-end call in INT project. Call for anyone who wants to participate. There is one energy use case from TIFG. It was discussed at the RSAP. Feedback welcomed.

         7. 01-09: @Ray-Guang Cheng: Problem with integrated O-DU not communicating with TM-500. @David Kinsey [AT&T]:Need project help to debug. RSAC to help do incremental builds to identify when disconnect occurs: 1) ODULOW → TM500 2) xFAPI->ODULOW→TM500 5) ODUHIGH->xFAPI->ODULOW→TM500. Need to isolate since all three components indicate they don't have a defect but integrated build doesn't work.

         8. SMO blueprint

            1. 04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   5. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work

      1. 05-15: No updates.

      2. 03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu

      3. 03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.

      4. 03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.

      5. 03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.

      6. 03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.

   6. Internship update

8. Meeting Summary and Closure

•  

  • 03-27: @David Kinsey [AT&T] out on  May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.

  • 03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks. 

  • Next Meeting Jun 5, 2025 starts by 18:15

2025 05 22

Recording 

Meeting Recording: link

Agenda

• Scribe: @abdulwahid.w  (Nokia)

• Previous scribe: 

  • 2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes  May 15, 2025 

   3. Next Meeting May 29, 2025 

   4. Release Update

      1. New repo requests

         1. 08.05: AIMLFW repository approved by TOC

   5. New business

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. Tooling budget update 

      2. SCCL enforcement

   7. Old Business

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision:  @David Kinsey [AT&T] Motion to Approve; Seconded by @Ultan.Kelly . No Objections. May 22, 2025  Minutes approved. 

3. Release

   1. 05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.

   2. 05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.

   3. 04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf

   4. 04-03: @Sally Cooper : PR has been approved. PR will post  Apr 3, 2025

   5. 03-27: @Sally Cooper: waiting for the last approval from Intel, but it should come in. Logo solved.

   6. 03-20: not all input from PTLs received. Discussion about objective continues. Most of the project participating in RSAC knows what to do, but it needs to be documented.

   7. 03-13: Schedule under L-Release Timeline - Releases - Confluence/Wiki. We are finishing sprint 1. PLT asked to update the objectives.

   8. 03-06: No news. Next release planned for June, following 3 releases per year.

   9. Release Votes (checklist) and Approval

   10. New repo request

       1. 04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by  @James Li; No objections. Motion was carried.

       2. 04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.

   11. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 05-22: To think on on strategy as a blog/write up on how the CVE’s are handled. Still waitig on this. @Sridhar Rao may have some insights.

      2. 05-15: Need some actions on this. Waiting for David .

      3. 04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.

      4. 03-27: @Martin Skorupski page Common Vulnerabilities and Exposures (CVE) updated with status column. @Sridhar Rao will also improve the LNF scans as we go from Jenkins to Gitlab actions. The scan will work only on build. Infrastructure is there (https://github.com/lfit/releng-reusable-workflows ) and open to anyone who wants to try it.

      5. 03-20: @Martin Skorupski there is a table at RSAC wiki with status. In discussion with PTLs. Will add columns for release when CVE was discovered and resolved. 

      6. 03-12: @Martin Skorupski: feedback period running. @David Kinsey [AT&T]: maybe it is too general, some CVEs were already closed. Someone should look at the new CVEs. If something is corrected, it should be mentioned in our release notes. The CVD process of O-RAN covers the update of CVE status in the database. We need just to report the updates to O-RAN.

      7. 03-12: @Jakub Novy [DTAG]: do we have a statement in OSC's code that we provide it "as is"? @David Kinsey [AT&T] / @Martin Skorupski: it is in both licenses we are using.

      8. 03-06: From WG11 towards OSC. There is a new CVE discovered (CVE-2024-34035, CVE-2024-34036). WG11 asks position of OSC regarding CVEs. @Martin Skorupski: we are contribution driven, so we cannot guarantee that it will be fixed. Draft of the statement is here: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333381634/Common+Vulnerabilities+and+Exposures+CVE. @Martin Skorupski to share via mail and TOC to approve next week(s).

   2. Rutgers Access Policies

      1. 03-06: @Martin Skorupski: Request for AccessPolicies by Rutgers (new O-RAN-SC Lab): draft answer to 4 questions here:  OWL- Open Wireless Lab#O-RAN-SC-Access-and-Use-Policy

         1. @Tracy Van Brakle: Keysight and Viavi wants to have a special ID to track the usage of their tools. @Martin Skorupski:How should be the access approved? By OSC TOC.

      2. 03-13: access list here: OWL- Open Wireless Lab - Requirements and Software Architecture Committee - Confluence/Wiki, not yet fully implemented.

      3. 05-15: Couple of new servers assigned, totally 10 servers available. Work is needed to get those up and running.

   3. k8s version deprecation

      1. 05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. 04-24:  @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.

   2. 04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.

   3. 04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.

   4. 03-27: @David Kinsey [AT&T] no update about tooling, will provide next week.

   5. 03-27: @Sridhar Rao logo now fixed.

   6. 03-20: @Sridhar Rao there is an O-RAN logo at http://docs.o-ran-sc.org . @David Kinsey [AT&T] It is there since beginning. If O-RAN does not approve it, we can change it. @James Li to reach out to PTL for DOC project, Wichen Ni

   7. 03-06: @Tracy Van Brakle OSC development efforts in Rutgers will be supported by new tools (O-RU, RICtest). Finalizing the procurement with O-RAN office now.

   8. OSFG updates:

      1. Workshop:

         1. 05-22: Workshop is on 05-23.

         2. 04-24: registration was requested if attend to OAI workshop either in person of remotely.

         3. 04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.

         4. 04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.

         5. 04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista; 

         6. 03-27: workshop will be in Kista, Irfan and John will be present, not David. Local contact known to align details. David will share the agenda with Sridhar. John will manage the booking of a room.

         7. 03-20: @Sridhar Rao will reach to other LNF projects if they are interested if the date is decided. @David Kinsey [AT&T] if its in Kista, then the date is set. It is not sure if its full day/half day. @Sridhar Rao will make a poll to see who from OSC can join on 23rd of May. @James Li will add a topic on Monday's OSFG call to prepare a paragraph about it which Sridhar can share with other projects.

         8. 03-20: @David Kinsey [AT&T]can send a mail to reflector about the possible topics. Will push at OSFG. No other update.

         9. 03-13: currently three options, see below. 

         10. OAI workshop

             1. 04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.

             2. 03-13: @David Kinsey [AT&T] May 21-22 (Wed-Thu) in Kista, Sweeden. If we would be present, we need to start preparing the line-up. So far we do not have the confirmation from various communities if they can attend - deadline is in two weeks, it will be difficult to manage. https://openairinterface.org/summer-2025-workshop-the-openairinterface-path-to-ai-driven-6g/  

             3. 03-13: @John Keeney (Ericsson EST) might be able to secure an Ericsson location in Kista.

         11. Open Source workshop:

             1. 03-13: Other option is to join the LNF at end of June in Denver. We would still need to work on it soon. https://events.linuxfoundation.org/open-source-summit-north-america/

             2. 03-06: @Tracy Van Brakle we should discuss demos with OAI and Nephio - better to wait for David and Irfan to be back

         12. Workshop at O-RAN F2F

             1. 03-13: Possible, It will be difficult to collocate due to large overlap with other O-RAN meetings. OSC co-chairs are also active in the WGs as well as many of the TOC members.

      2. O-RAN SCCL enforcement:

         1. 05-22: Demo is not presented to ORAN. Document is almost ready for approval, probably for June release. License(example template) is available in o-ran.org/scc

         2. 04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed. 

         3. 04-17: @Jakub Novy [DTAG] in progress, trying to get closed.

         4. 03-20: @Jakub Novy [DTAG]: still waiting for O-RAN legeal, OCOP clarifications.

         5. 03-13: @Jakub Novy [DTAG]: in progress, pending confirmation from O-RAN legal.

         6. 03-06: @Jakub Novy [DTAG]: in progress, received feedback during F2F, demo repo prepared, OSARP document is under development.

      3. Collaboration with OAI (lab interconnection) and Nephio

         1. 03-20: @Martin Skorupski OAI and Nephio artifacts are already in one lab in France, so it works.

         2. 03-06: no update

      4. OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.

         1. 03-06: no update

      5.  Face-to-Face Meeting

         1. 03-06: Jinri: good event. We discussed the collaboration with standardization part, workshop, there were on-site and on-line demos. Next F2F planned for June.

   9. 3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination

      1. 04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system. 

   10. IEEE GLOBECOM 2025 O-RAN workshop

       1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

   11. ORAN Tooling

       1. 05-22: AT&T wil not be able to take the funds from ORAN to buy tools. Till then need strategy touse with the existing stubs and simulators for testing.

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

      1. 05-08: Panels reservation required. Need to check further.

      2. 05-15: Professor Ray to attend F2F in June, one panel reserved for ORAN .

7. Old Business

   1. RSAC co-chair

      1. 04-17: no update; still looking for. 

      2. 04-10: no update. still looking for a new RSAC co-chair.

   2. 03-20: still looking for a new RSAC co-chair.

   3. 02-13: RSAC: We'll begin that solicitation today for another RSAC co-chair, as Ritwick confirmed this week he doesn't have the capacity to continue. Anybody who wants to self nominate or knows somebody that would be interested can propose

   4. Project Updates

      1. RSAC - @Rittwik Jana or @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 05-22: Post reconfiguration TM500 is able to connect to ODU low. Professor Vipin working on the xFAPI issue by removing the code dependency on the module. Legal issues to be addressed as some code used is licensed.

         2. 05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.

         3. 04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.

         4. 04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.

         5. 04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)

         6. 03-27: @bimo fransiscus asisi: There is a Discussion End-to-End Integration page to have end-to-end call in INT project. Call for anyone who wants to participate. There is one energy use case from TIFG. It was discussed at the RSAP. Feedback welcomed.

         7. 01-09: @Ray-Guang Cheng: Problem with integrated O-DU not communicating with TM-500. @David Kinsey [AT&T]:Need project help to debug. RSAC to help do incremental builds to identify when disconnect occurs: 1) ODULOW → TM500 2) xFAPI->ODULOW→TM500 5) ODUHIGH->xFAPI->ODULOW→TM500. Need to isolate since all three components indicate they don't have a defect but integrated build doesn't work.

         8. SMO blueprint

            1. 04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   5. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work

      1. 05-15: No updates.

      2. 03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu

      3. 03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.

      4. 03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.

      5. 03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.

      6. 03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.

   6. Internship update

8. Meeting Summary and Closure

•  

  • 03-27: @David Kinsey [AT&T] out on  May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.

  • 03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks. 

  • Next Meeting May 29, 2025

2025 05 15

Recording 

Meeting Recording: link

Agenda

• Scribe: @abdulwahid.w  (Nokia)
  
  

• Previous scribe: 

  • 2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes May 8, 2025 

   3. Next Meeting May 22, 2025 

   4. Release Update

      1. New repo requests

         1. 08.05: AIMLFW repository approved by TOC

   5. New business

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. Tooling budget update 

      2. SCCL enforcement

   7. Old Business

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision:  @Avinash Bhat Motion to Approve; Seconded by @Jakub Novy [DTAG]. No Objections. May 8, 2025  Minutes approved. 

3. Release

   1. 05-15: Inputs from RSAC F2F meeting could be taken for Release announcement.

   2. 05-15: Release scanning scheduled in June 1st week, can be moved ahead unless any issue from any of the PTL’s.

   3. 04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf

   4. 04-03: @Sally Cooper : PR has been approved. PR will post  Apr 3, 2025

   5. 03-27: @Sally Cooper: waiting for the last approval from Intel, but it should come in. Logo solved.

   6. 03-20: not all input from PTLs received. Discussion about objective continues. Most of the project participating in RSAC knows what to do, but it needs to be documented.

   7. 03-13: Schedule under L-Release Timeline - Releases - Confluence/Wiki. We are finishing sprint 1. PLT asked to update the objectives.

   8. 03-06: No news. Next release planned for June, following 3 releases per year.

   9. Release Votes (checklist) and Approval

   10. New repo request

       1. 04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by  @James Li; No objections. Motion was carried.

       2. 04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.

   11. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 05-15: Need some actions on this. Waiting for David .

      2. 04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.

      3. 03-27: @Martin Skorupski page Common Vulnerabilities and Exposures (CVE) updated with status column. @Sridhar Rao will also improve the LNF scans as we go from Jenkins to Gitlab actions. The scan will work only on build. Infrastructure is there (https://github.com/lfit/releng-reusable-workflows) and open to anyone who wants to try it.

      4. 03-20: @Martin Skorupski there is a table at RSAC wiki with status. In discussion with PTLs. Will add columns for release when CVE was discovered and resolved. 

      5. 03-12: @Martin Skorupski: feedback period running. @David Kinsey [AT&T]: maybe it is too general, some CVEs were already closed. Someone should look at the new CVEs. If something is corrected, it should be mentioned in our release notes. The CVD process of O-RAN covers the update of CVE status in the database. We need just to report the updates to O-RAN.

      6. 03-12: @Jakub Novy [DTAG]: do we have a statement in OSC's code that we provide it "as is"? @David Kinsey [AT&T] / @Martin Skorupski: it is in both licenses we are using.

      7. 03-06: From WG11 towards OSC. There is a new CVE discovered (CVE-2024-34035, CVE-2024-34036). WG11 asks position of OSC regarding CVEs. @Martin Skorupski: we are contribution driven, so we cannot guarantee that it will be fixed. Draft of the statement is here: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333381634/Common+Vulnerabilities+and+Exposures+CVE. @Martin Skorupski to share via mail and TOC to approve next week(s).

   2. Rutgers Access Policies

      1. 03-06: @Martin Skorupski: Request for AccessPolicies by Rutgers (new O-RAN-SC Lab): draft answer to 4 questions here:  OWL- Open Wireless Lab#O-RAN-SC-Access-and-Use-Policy

         1. @Tracy Van Brakle: Keysight and Viavi wants to have a special ID to track the usage of their tools. @Martin Skorupski:How should be the access approved? By OSC TOC.

      2. 03-13: access list here: OWL- Open Wireless Lab - Requirements and Software Architecture Committee - Confluence/Wiki, not yet fully implemented.

      3. 05-15: Couple of new servers assigned, totally 10 servers available. Work is needed toget those up and running.

   3. k8s version deprecation

      1. 05-15: @Avinash Bhat: Requests for using newer version of k8s. Bimo mentioned the plan is to use single k8s version to support integration work. Need confirmations from PTL's( required changes and efforts for upgrading) and agree on version.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. 04-24:  @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.

   2. 04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.

   3. 04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.

   4. 03-27: @David Kinsey [AT&T] no update about tooling, will provide next week.

   5. 03-27: @Sridhar Rao logo now fixed.

   6. 03-20: @Sridhar Rao there is an O-RAN logo at docs.o-ran-sc.org. @David Kinsey [AT&T] It is there since beginning. If O-RAN does not approve it, we can change it. @James Li to reach out to PTL for DOC project, Wichen Ni

   7. 03-06: @Tracy Van Brakle OSC development efforts in Rutgers will be supported by new tools (O-RU, RICtest). Finalizing the procurement with O-RAN office now.

   8. OSFG updates:

      1. Workshop:

         1. 04-24: registration was requested if attend to OAI workshop either in person of remotely.

         2. 04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.

         3. 04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.

         4. 04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista; 

         5. 03-27: workshop will be in Kista, Irfan and John will be present, not David. Local contact known to align details. David will share the agenda with Sridhar. John will manage the booking of a room.

         6. 03-20: @Sridhar Rao will reach to other LNF projects if they are interested if the date is decided. @David Kinsey [AT&T] if its in Kista, then the date is set. It is not sure if its full day/half day. @Sridhar Rao will make a poll to see who from OSC can join on 23rd of May. @James Li will add a topic on Monday's OSFG call to prepare a paragraph about it which Sridhar can share with other projects.

         7. 03-20: @David Kinsey [AT&T]can send a mail to reflector about the possible topics. Will push at OSFG. No other update.

         8. 03-13: currently three options, see below. 

         9. OAI workshop

            1. 04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.

            2. 03-13: @David Kinsey [AT&T] May 21-22 (Wed-Thu) in Kista, Sweeden. If we would be present, we need to start preparing the line-up. So far we do not have the confirmation from various communities if they can attend - deadline is in two weeks, it will be difficult to manage. https://openairinterface.org/summer-2025-workshop-the-openairinterface-path-to-ai-driven-6g/ 

            3. 03-13: @John Keeney (Ericsson EST) might be able to secure an Ericsson location in Kista.

         10. Open Source workshop:

             1. 03-13: Other option is to join the LNF at end of June in Denver. We would still need to work on it soon. https://events.linuxfoundation.org/open-source-summit-north-america/

             2. 03-06: @Tracy Van Brakle we should discuss demos with OAI and Nephio - better to wait for David and Irfan to be back

         11. Workshop at O-RAN F2F

             1. 03-13: Possible, It will be difficult to collocate due to large overlap with other O-RAN meetings. OSC co-chairs are also active in the WGs as well as many of the TOC members.

      2. O-RAN SCCL enforcement:

         1. 04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed. 

         2. 04-17: @Jakub Novy [DTAG] in progress, trying to get closed.

         3. 03-20: @Jakub Novy [DTAG]: still waiting for O-RAN legeal, OCOP clarifications.

         4. 03-13: @Jakub Novy [DTAG]: in progress, pending confirmation from O-RAN legal.

         5. 03-06: @Jakub Novy [DTAG]: in progress, received feedback during F2F, demo repo prepared, OSARP document is under development.

      3. Collaboration with OAI (lab interconnection) and Nephio

         1. 03-20: @Martin Skorupski OAI and Nephio artifacts are already in one lab in France, so it works.

         2. 03-06: no update

      4. OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.

         1. 03-06: no update

      5.  Face-to-Face Meeting

         1. 03-06: Jinri: good event. We discussed the collaboration with standardization part, workshop, there were on-site and on-line demos. Next F2F planned for June.

   9. 3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination

      1. 04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system. 

   10. IEEE GLOBECOM 2025 O-RAN workshop

       1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

      1. 05-08: Panels reservation required. Need to check further.

      2. 05-15: James to attend F2F in June, one panel reserved for ORAN .

7. Old Business

   1. RSAC co-chair

      1. 04-17: no update; still looking for. 

      2. 04-10: no update. still looking for a new RSAC co-chair.

   2. 03-20: still looking for a new RSAC co-chair.

   3. 02-13: RSAC: We'll begin that solicitation today for another RSAC co-chair, as Ritwick confirmed this week he doesn't have the capacity to continue. Anybody who wants to self nominate or knows somebody that would be interested can propose

   4. Project Updates
      
      

      1. RSAC - @Rittwik Jana or @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 05-15: E2E integration for F2F demo. Needs to track integrations of various ORAN projects. Slack could be use to get updates centrally. @John Keeney (Ericsson EST) and Bimo to work together on resolving the integration issues.

         2. 04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.

         3. 04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.

         4. 04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)

         5. 03-27: @bimo fransiscus asisi: There is a Discussion End-to-End Integration page to have end-to-end call in INT project. Call for anyone who wants to participate. There is one energy use case from TIFG. It was discussed at the RSAP. Feedback welcomed.

         6. 01-09: @Ray-Guang Cheng: Problem with integrated O-DU not communicating with TM-500. @David Kinsey [AT&T]:Need project help to debug. RSAC to help do incremental builds to identify when disconnect occurs: 1) ODULOW → TM500 2) xFAPI->ODULOW→TM500 5) ODUHIGH->xFAPI->ODULOW→TM500. Need to isolate since all three components indicate they don't have a defect but integrated build doesn't work.

         7. SMO blueprint

            1. 04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   5. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work

      1. 05-15: No updates.

      2. 03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu

      3. 03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.

      4. 03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.

      5. 03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.

      6. 03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.

   6. Internship update

       8. Meeting Summary and Closure

•  

  • 03-27: @David Kinsey [AT&T] out on  May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.

  • 03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks. 

  • Next Meeting May 22, 2025 : @Martin Skorupski is tentative.  Will send a mail on the next meeting based on Jinri and David's availability.
    
    

2025 05 08

Recording 

Meeting Recording:

Agenda

• Scribe: @abdulwahid.w  (Nokia)
  
  

• Previous scribe: 

  • 2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes Apr 17, 2025 

   3. Next Meeting May 8, 2025 

   4. Release Update

      1. New repo requests

         1. 08.05: AIMLFW repository approved by TOC

   5. New business

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. Tooling budget update 

      2. SCCL enforcement

   7. Old Business

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision:  @Ankit Barve Motion to Approve; Seconded by @Sandeep Sarma (Ericsson); No Objections. Apr 24, 2025  Minutes approved. 

3. Release
   
   

   1. 04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf

   2. 04-03: @Sally Cooper : PR has been approved. PR will post  Apr 3, 2025

   3. 03-27: @Sally Cooper: waiting for the last approval from Intel, but it should come in. Logo solved.

   4. 03-20: not all input from PTLs received. Discussion about objective continues. Most of the project participating in RSAC knows what to do, but it needs to be documented.

   5. 03-13: Schedule under L-Release Timeline - Releases - Confluence/Wiki. We are finishing sprint 1. PLT asked to update the objectives.

   6. 03-06: No news. Next release planned for June, following 3 releases per year.

   7. Release Votes (checklist) and Approval

   8. New repo request

      1. 04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by  @James Li; No objections. Motion was carried.

      2. 04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.

   9. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.

      2. 03-27: @Martin Skorupski page Common Vulnerabilities and Exposures (CVE) updated with status column. @Sridhar Rao will also improve the LNF scans as we go from Jenkins to Gitlab actions. The scan will work only on build. Infrastructure is there (https://github.com/lfit/releng-reusable-workflows) and open to anyone who wants to try it.

      3. 03-20: @Martin Skorupski there is a table at RSAC wiki with status. In discussion with PTLs. Will add columns for release when CVE was discovered and resolved. 

      4. 03-12: @Martin Skorupski: feedback period running. @David Kinsey [AT&T]: maybe it is too general, some CVEs were already closed. Someone should look at the new CVEs. If something is corrected, it should be mentioned in our release notes. The CVD process of O-RAN covers the update of CVE status in the database. We need just to report the updates to O-RAN.

      5. 03-12: @Jakub Novy [DTAG]: do we have a statement in OSC's code that we provide it "as is"? @David Kinsey [AT&T] / @Martin Skorupski: it is in both licenses we are using.

      6. 03-06: From WG11 towards OSC. There is a new CVE discovered (CVE-2024-34035, CVE-2024-34036). WG11 asks position of OSC regarding CVEs. @Martin Skorupski: we are contribution driven, so we cannot guarantee that it will be fixed. Draft of the statement is here: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333381634/Common+Vulnerabilities+and+Exposures+CVE. @Martin Skorupski to share via mail and TOC to approve next week(s).

   2. Rutgers Access Policies

      1. 03-06: @Martin Skorupski: Request for AccessPolicies by Rutgers (new O-RAN-SC Lab): draft answer to 4 questions here:  OWL- Open Wireless Lab#O-RAN-SC-Access-and-Use-Policy

         1. @Tracy Van Brakle: Keysight and Viavi wants to have a special ID to track the usage of their tools. @Martin Skorupski:How should be the access approved? By OSC TOC.

      2. 03-13: access list here: OWL- Open Wireless Lab - Requirements and Software Architecture Committee - Confluence/Wiki, not yet fully implemented.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. 04-24:  @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.

   2. 04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.

   3. 04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.

   4. 03-27: @David Kinsey [AT&T] no update about tooling, will provide next week.

   5. 03-27: @Sridhar Rao logo now fixed.

   6. 03-20: @Sridhar Rao there is an O-RAN logo at docs.o-ran-sc.org. @David Kinsey [AT&T] It is there since beginning. If O-RAN does not approve it, we can change it. @James Li to reach out to PTL for DOC project, Wichen Ni

   7. 03-06: @Tracy Van Brakle OSC development efforts in Rutgers will be supported by new tools (O-RU, RICtest). Finalizing the procurement with O-RAN office now.

   8. OSFG updates:

      1. Workshop:

         1. 04-24: registration was requested if attend to OAI workshop either in person of remotely.

         2. 04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.

         3. 04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.

         4. 04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista; 

         5. 03-27: workshop will be in Kista, Irfan and John will be present, not David. Local contact known to align details. David will share the agenda with Sridhar. John will manage the booking of a room.

         6. 03-20: @Sridhar Rao will reach to other LNF projects if they are interested if the date is decided. @David Kinsey [AT&T] if its in Kista, then the date is set. It is not sure if its full day/half day. @Sridhar Rao will make a poll to see who from OSC can join on 23rd of May. @James Li will add a topic on Monday's OSFG call to prepare a paragraph about it which Sridhar can share with other projects.

         7. 03-20: @David Kinsey [AT&T]can send a mail to reflector about the possible topics. Will push at OSFG. No other update.

         8. 03-13: currently three options, see below. 

         9. OAI workshop

            1. 04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.

            2. 03-13: @David Kinsey [AT&T] May 21-22 (Wed-Thu) in Kista, Sweeden. If we would be present, we need to start preparing the line-up. So far we do not have the confirmation from various communities if they can attend - deadline is in two weeks, it will be difficult to manage. https://openairinterface.org/summer-2025-workshop-the-openairinterface-path-to-ai-driven-6g/ 

            3. 03-13: @John Keeney (Ericsson EST) might be able to secure an Ericsson location in Kista.

         10. Open Source workshop:

             1. 03-13: Other option is to join the LNF at end of June in Denver. We would still need to work on it soon. https://events.linuxfoundation.org/open-source-summit-north-america/

             2. 03-06: @Tracy Van Brakle we should discuss demos with OAI and Nephio - better to wait for David and Irfan to be back

         11. Workshop at O-RAN F2F

             1. 03-13: Possible, It will be difficult to collocate due to large overlap with other O-RAN meetings. OSC co-chairs are also active in the WGs as well as many of the TOC members.

      2. O-RAN SCCL enforcement:

         1. 04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed. 

         2. 04-17: @Jakub Novy [DTAG] in progress, trying to get closed.

         3. 03-20: @Jakub Novy [DTAG]: still waiting for O-RAN legeal, OCOP clarifications.

         4. 03-13: @Jakub Novy [DTAG]: in progress, pending confirmation from O-RAN legal.

         5. 03-06: @Jakub Novy [DTAG]: in progress, received feedback during F2F, demo repo prepared, OSARP document is under development.

      3. Collaboration with OAI (lab interconnection) and Nephio

         1. 03-20: @Martin Skorupski OAI and Nephio artifacts are already in one lab in France, so it works.

         2. 03-06: no update

      4. OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.

         1. 03-06: no update

      5.  Face-to-Face Meeting

         1. 03-06: Jinri: good event. We discussed the collaboration with standardization part, workshop, there were on-site and on-line demos. Next F2F planned for June.

   9. 3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination

      1. 04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system. 

   10. IEEE GLOBECOM 2025 O-RAN workshop

       1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

      1. 05-08: Panels reservation required. Need to check further.

7. Old Business

   1. ASN.1 compiler

      1. 05-08: This is completed

      2. 04-24: we will check the progress next week.

      3. 04-17: @Sridhar Rao still working for delete the ASN.1 compiler.

      4. 04-10: the archive ASN.1 compiler will be deleted by @Sridhar Rao Apr 10, 2025 .

      5. 04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.

      6. 03-27: @Martin Skorupski: wiki page created based on discussion last week: ASN.1 Compiler. There is a pointer at gerrit to very old and unused compiler. Some people were using the Nokia one which is not too active either. Suggestion is to use another ASN.1 compiler, which is up-to-date. The code needs to be changed to reflect the change. This wiki can be a guidance for the future.

      7. 03-20: ASN.1 compiler issues - can we switch to the OAI one? There is also almost empty repo which needs to be updated/deleted. @bimo fransiscus asisi we need some official step to inform projects to use a different compiler. @Martin Skorupski will prepare a material for next meeting and vote.

   2. RSAC co-chair

      1. 04-17: no update; still looking for. 

      2. 04-10: no update. still looking for a new RSAC co-chair.

   3. 03-20: still looking for a new RSAC co-chair.

   4. 02-13: RSAC: We'll begin that solicitation today for another RSAC co-chair, as Ritwick confirmed this week he doesn't have the capacity to continue. Anybody who wants to self nominate or knows somebody that would be interested can propose

   5. Project Updates
      
      

      1. RSAC - @Rittwik Jana or @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.

         2. 04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.

         3. 04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)

         4. 03-27: @bimo fransiscus asisi: There is a Discussion End-to-End Integration page to have end-to-end call in INT project. Call for anyone who wants to participate. There is one energy use case from TIFG. It was discussed at the RSAP. Feedback welcomed.

         5. 01-09: @Ray-Guang Cheng: Problem with integrated O-DU not communicating with TM-500. @David Kinsey [AT&T]:Need project help to debug. RSAC to help do incremental builds to identify when disconnect occurs: 1) ODULOW → TM500 2) xFAPI->ODULOW→TM500 5) ODUHIGH->xFAPI->ODULOW→TM500. Need to isolate since all three components indicate they don't have a defect but integrated build doesn't work.

         6. ASN.1 Fix

            1. 01-16: Still open - Status remains the same due to absence.

            2. 01-09: @bimo fransiscus asisi: Need ASN1 fix. @abdulwahid.w: Nokia has a resource but haven't reached out since new year. Wahid will get a status.

         7. SMO blueprint

            1. 04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   6. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
      
      

      1. 03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu

      2. 03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.

      3. 03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.

      4. 03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.

      5. 03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.

   7. Internship update

       8. Meeting Summary and Closure

•  

  • 03-27: @David Kinsey [AT&T] out on  May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.

  • 03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks. 

  • Next Meeting May 8, 2025 

2025 04 24

Recording 

Meeting Recording:

Agenda

• Scribe: @Yasufumi Morioka (NTT Docomo)

• Previous scribe: 

  • 2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: Nokia

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes Apr 17, 2025 

   3. Next Meeting May 1, 2025 

   4. Release Update

      1. New repo requests

   5. New business

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. Tooling budget update 

      2. SCCL enforcement

   7. Old Business

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision:  @Ankit Barve Motion to Approve; Seconded by @Sandeep Sarma (Ericsson); No Objections. Apr 17, 2025  Minutes approved. 

3. Release
   
   

   1. 04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf

   2. 04-03: @Sally Cooper : PR has been approved. PR will post  Apr 3, 2025

   3. 03-27: @Sally Cooper: waiting for the last approval from Intel, but it should come in. Logo solved.

   4. 03-20: not all input from PTLs received. Discussion about objective continues. Most of the project participating in RSAC knows what to do, but it needs to be documented.

   5. 03-13: Schedule under L-Release Timeline - Releases - Confluence/Wiki. We are finishing sprint 1. PLT asked to update the objectives.

   6. 03-06: No news. Next release planned for June, following 3 releases per year.

   7. Release Votes (checklist) and Approval

   8. New repo request

      1. 04-24: oam/oam-controller repo request; @David Kinsey [AT&T] motion to approve; seconded by  @James Li; No objections. Motion was carried.

      2. 04-24: it/tifg repo request; it would be beneficial for the integration project side to test those pieces as prior to their assembly in a more end-to-end manner; @David Kinsey [AT&T] motion to approve; seconded by @James Li; No objections; Motion was carried.

   9. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.

      2. 03-27: @Martin Skorupski page Common Vulnerabilities and Exposures (CVE) updated with status column. @Sridhar Rao will also improve the LNF scans as we go from Jenkins to Gitlab actions. The scan will work only on build. Infrastructure is there (https://github.com/lfit/releng-reusable-workflows) and open to anyone who wants to try it.

      3. 03-20: @Martin Skorupski there is a table at RSAC wiki with status. In discussion with PTLs. Will add columns for release when CVE was discovered and resolved. 

      4. 03-12: @Martin Skorupski: feedback period running. @David Kinsey [AT&T]: maybe it is too general, some CVEs were already closed. Someone should look at the new CVEs. If something is corrected, it should be mentioned in our release notes. The CVD process of O-RAN covers the update of CVE status in the database. We need just to report the updates to O-RAN.

      5. 03-12: @Jakub Novy [DTAG]: do we have a statement in OSC's code that we provide it "as is"? @David Kinsey [AT&T] / @Martin Skorupski: it is in both licenses we are using.

      6. 03-06: From WG11 towards OSC. There is a new CVE discovered (CVE-2024-34035, CVE-2024-34036). WG11 asks position of OSC regarding CVEs. @Martin Skorupski: we are contribution driven, so we cannot guarantee that it will be fixed. Draft of the statement is here: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333381634/Common+Vulnerabilities+and+Exposures+CVE. @Martin Skorupski to share via mail and TOC to approve next week(s).

   2. Rutgers Access Policies

      1. 03-06: @Martin Skorupski: Request for AccessPolicies by Rutgers (new O-RAN-SC Lab): draft answer to 4 questions here:  OWL- Open Wireless Lab#O-RAN-SC-Access-and-Use-Policy

         1. @Tracy Van Brakle: Keysight and Viavi wants to have a special ID to track the usage of their tools. @Martin Skorupski:How should be the access approved? By OSC TOC.

      2. 03-13: access list here: OWL- Open Wireless Lab - Requirements and Software Architecture Committee - Confluence/Wiki, not yet fully implemented.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. 04-24:  @David Kinsey [AT&T] the budget will cover all three tools; AT&T and O-RAN EC need to collaborate to approve the budget.

   2. 04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.

   3. 04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.

   4. 03-27: @David Kinsey [AT&T] no update about tooling, will provide next week.

   5. 03-27: @Sridhar Rao logo now fixed.

   6. 03-20: @Sridhar Rao there is an O-RAN logo at docs.o-ran-sc.org. @David Kinsey [AT&T] It is there since beginning. If O-RAN does not approve it, we can change it. @James Li to reach out to PTL for DOC project, Wichen Ni

   7. 03-06: @Tracy Van Brakle OSC development efforts in Rutgers will be supported by new tools (O-RU, RICtest). Finalizing the procurement with O-RAN office now.

   8. OSFG updates:

      1. Workshop:

         1. 04-24: registration was requested if attend to OAI workshop either in person of remotely.

         2. 04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.

         3. 04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.

         4. 04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista; 

         5. 03-27: workshop will be in Kista, Irfan and John will be present, not David. Local contact known to align details. David will share the agenda with Sridhar. John will manage the booking of a room.

         6. 03-20: @Sridhar Rao will reach to other LNF projects if they are interested if the date is decided. @David Kinsey [AT&T] if its in Kista, then the date is set. It is not sure if its full day/half day. @Sridhar Rao will make a poll to see who from OSC can join on 23rd of May. @James Li will add a topic on Monday's OSFG call to prepare a paragraph about it which Sridhar can share with other projects.

         7. 03-20: @David Kinsey [AT&T]can send a mail to reflector about the possible topics. Will push at OSFG. No other update.

         8. 03-13: currently three options, see below. 

         9. OAI workshop

            1. 04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.

            2. 03-13: @David Kinsey [AT&T] May 21-22 (Wed-Thu) in Kista, Sweeden. If we would be present, we need to start preparing the line-up. So far we do not have the confirmation from various communities if they can attend - deadline is in two weeks, it will be difficult to manage. https://openairinterface.org/summer-2025-workshop-the-openairinterface-path-to-ai-driven-6g/ 

            3. 03-13: @John Keeney (Ericsson EST) might be able to secure an Ericsson location in Kista.

         10. Open Source workshop:

             1. 03-13: Other option is to join the LNF at end of June in Denver. We would still need to work on it soon. https://events.linuxfoundation.org/open-source-summit-north-america/

             2. 03-06: @Tracy Van Brakle we should discuss demos with OAI and Nephio - better to wait for David and Irfan to be back

         11. Workshop at O-RAN F2F

             1. 03-13: Possible, It will be difficult to collocate due to large overlap with other O-RAN meetings. OSC co-chairs are also active in the WGs as well as many of the TOC members.

      2. O-RAN SCCL enforcement:

         1. 04-24: SCCL has not been fully adopted yet; we were not sure whether both process and legal aspect was closed. 

         2. 04-17: @Jakub Novy [DTAG] in progress, trying to get closed.

         3. 03-20: @Jakub Novy [DTAG]: still waiting for O-RAN legeal, OCOP clarifications.

         4. 03-13: @Jakub Novy [DTAG]: in progress, pending confirmation from O-RAN legal.

         5. 03-06: @Jakub Novy [DTAG]: in progress, received feedback during F2F, demo repo prepared, OSARP document is under development.

      3. Collaboration with OAI (lab interconnection) and Nephio

         1. 03-20: @Martin Skorupski OAI and Nephio artifacts are already in one lab in France, so it works.

         2. 03-06: no update

      4. OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.

         1. 03-06: no update

      5.  Face-to-Face Meeting

         1. 03-06: Jinri: good event. We discussed the collaboration with standardization part, workshop, there were on-site and on-line demos. Next F2F planned for June.

   9. 3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination

      1. 04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system. 

   10. IEEE GLOBECOM 2025 O-RAN workshop

       1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

7. Old Business

   1. ASN.1 compiler

      1. 04-24: we will check the progress next week.

      2. 04-17: @Sridhar Rao still working for delete the ASN.1 compiler.

      3. 04-10: the archive ASN.1 compiler will be deleted by @Sridhar Rao Apr 10, 2025 .

      4. 04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.

      5. 03-27: @Martin Skorupski: wiki page created based on discussion last week: ASN.1 Compiler. There is a pointer at gerrit to very old and unused compiler. Some people were using the Nokia one which is not too active either. Suggestion is to use another ASN.1 compiler, which is up-to-date. The code needs to be changed to reflect the change. This wiki can be a guidance for the future.

      6. 03-20: ASN.1 compiler issues - can we switch to the OAI one? There is also almost empty repo which needs to be updated/deleted. @bimo fransiscus asisi we need some official step to inform projects to use a different compiler. @Martin Skorupski will prepare a material for next meeting and vote.

   2. RSAC co-chair

      1. 04-17: no update; still looking for. 

      2. 04-10: no update. still looking for a new RSAC co-chair.

   3. 03-20: still looking for a new RSAC co-chair.

   4. 02-13: RSAC: We'll begin that solicitation today for another RSAC co-chair, as Ritwick confirmed this week he doesn't have the capacity to continue. Anybody who wants to self nominate or knows somebody that would be interested can propose

   5. Project Updates
      
      

      1. RSAC - @Rittwik Jana or @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.

         2. 04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.

         3. 04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)

         4. 03-27: @bimo fransiscus asisi: There is a Discussion End-to-End Integration page to have end-to-end call in INT project. Call for anyone who wants to participate. There is one energy use case from TIFG. It was discussed at the RSAP. Feedback welcomed.

         5. 01-09: @Ray-Guang Cheng: Problem with integrated O-DU not communicating with TM-500. @David Kinsey [AT&T]:Need project help to debug. RSAC to help do incremental builds to identify when disconnect occurs: 1) ODULOW → TM500 2) xFAPI->ODULOW→TM500 5) ODUHIGH->xFAPI->ODULOW→TM500. Need to isolate since all three components indicate they don't have a defect but integrated build doesn't work.

         6. ASN.1 Fix

            1. 01-16: Still open - Status remains the same due to absence.

            2. 01-09: @bimo fransiscus asisi: Need ASN1 fix. @abdulwahid.w: Nokia has a resource but haven't reached out since new year. Wahid will get a status.

         7. SMO blueprint

            1. 04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   6. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
      
      

      1. 03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu

      2. 03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.

      3. 03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.

      4. 03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.

      5. 03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.

   7. Internship update

       8. Meeting Summary and Closure

•  

  • 03-27: @David Kinsey [AT&T] out on  May 8, 2025 - May 15, 2025 . We will need to decide if we keep them.

  • 03-06: @Alex Stancu: US time change will happen this Sunday. For other regions, TOC will start one hour earlier next 3 weeks. 

  • Next Meeting May 1, 2025 @David Kinsey [AT&T]to host; it might be a holiday in Europe. Nokia will be scribe in May. 

2025 04 17

Recording 

Meeting Recording: Link

Agenda

• Scribe: @Yasufumi Morioka (NTT Docomo)

• Previous scribe: 

  • 2025 => January: Viavi; February: China Mobile; March: DTAG, April: NTT Docomo, May: 

  • 2024 => December: Orange; October: Ericsson, September: Samsung, August: WindRiver; July: Radisys; June: AT&T; May: Nokia; April: TIM; March: Docomo; February: DT; January: Orange

  • 2023 => December: CMCC + others (TBD); November: Ericsson; October: Viavi; September: Samsung; August: Wind River; July: AT&T; June: Radisys, May: TIM, April: CMCC, March: Nokia, Feb: NTT, January: Ericsson

  • 2022 => December: Viavi, November: DT, October: Orange, September: Wind River, August: China Mobile, July: Samsung, June: AT&T

• Roll Call & Quorum Check

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.  

1. Review of Today's Agenda

   1. Roll Call

   2. Review previous meeting minutes Apr 10, 2025 

   3. Next Meeting Apr 24, 2025 

   4. Release Update

   5. New business

      1. CVE handling update

   6. O-RAN Business - OSFG Update & F2F Meeting 

      1. O-RAN Open-Source Workshop

      2. O-RAN SCCL enforcement status

   7. Old Business

      1. ASN.1 compiler

      2. Project updates

   8. AoB Future New Agenda Items and Announcements 

2. Review and Agree to Minutes of Previous Meeting

   1. Decision:  @Avinash Bhat Motion to Approve; Seconded by Julien Boudani; No Objections. Apr 10, 2025  Minutes approved. 

3. Release

   1. 04-10: @Sally Cooper PR has gone out; https://mediastorage.o-ran.org/press-release/OSC+O-RAN.EC.2025-03-04-Joint%20PR-%20OSC%20releases%20J%20and%20K%20-%20industry%20value.pdf

   2. 04-03: @Sally Cooper : PR has been approved. PR will post  Apr 3, 2025

   3. 03-27: @Sally Cooper: waiting for the last approval from Intel, but it should come in. Logo solved.

   4. 03-20: not all input from PTLs received. Discussion about objective continues. Most of the project participating in RSAC knows what to do, but it needs to be documented.

   5. 03-13: Schedule under L-Release Timeline - Releases - Confluence/Wiki. We are finishing sprint 1. PLT asked to update the objectives.

   6. 03-06: No news. Next release planned for June, following 3 releases per year.

   7. Release Votes (checklist) and Approval

   8. Other

4. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

   1. CVE Handling: Common Vulnerabilities and Exposures (CVE)

      1. 04-17: CVE issue hasn't been fully resolved; The action item remains open until a response is officially provided to the originators.

      2. 03-27: @Martin Skorupski page Common Vulnerabilities and Exposures (CVE) updated with status column. @Sridhar Rao will also improve the LNF scans as we go from Jenkins to Gitlab actions. The scan will work only on build. Infrastructure is there (https://github.com/lfit/releng-reusable-workflows) and open to anyone who wants to try it.

      3. 03-20: @Martin Skorupski there is a table at RSAC wiki with status. In discussion with PTLs. Will add columns for release when CVE was discovered and resolved. 

      4. 03-12: @Martin Skorupski: feedback period running. @David Kinsey [AT&T]: maybe it is too general, some CVEs were already closed. Someone should look at the new CVEs. If something is corrected, it should be mentioned in our release notes. The CVD process of O-RAN covers the update of CVE status in the database. We need just to report the updates to O-RAN.

      5. 03-12: @Jakub Novy [DTAG]: do we have a statement in OSC's code that we provide it "as is"? @David Kinsey [AT&T] / @Martin Skorupski: it is in both licenses we are using.

      6. 03-06: From WG11 towards OSC. There is a new CVE discovered (CVE-2024-34035, CVE-2024-34036). WG11 asks position of OSC regarding CVEs. @Martin Skorupski: we are contribution driven, so we cannot guarantee that it will be fixed. Draft of the statement is here: https://lf-o-ran-sc.atlassian.net/wiki/spaces/RSAC/pages/333381634/Common+Vulnerabilities+and+Exposures+CVE. @Martin Skorupski to share via mail and TOC to approve next week(s).

   2. Rutgers Access Policies

      1. 03-06: @Martin Skorupski: Request for AccessPolicies by Rutgers (new O-RAN-SC Lab): draft answer to 4 questions here:  OWL- Open Wireless Lab#O-RAN-SC-Access-and-Use-Policy

         1. @Tracy Van Brakle: Keysight and Viavi wants to have a special ID to track the usage of their tools. @Martin Skorupski:How should be the access approved? By OSC TOC.

      2. 03-13: access list here: OWL- Open Wireless Lab - Requirements and Software Architecture Committee - Confluence/Wiki, not yet fully implemented.

5. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.) 

   1. 04-10: @David Kinsey [AT&T] no update about tooling, continue to discuss internally and will provide update next week.

   2. 04-03: @David Kinsey [AT&T] tool introduction seems to face to difficulties, continue to discuss internally.

   3. 03-27: @David Kinsey [AT&T] no update about tooling, will provide next week.

   4. 03-27: @Sridhar Rao logo now fixed.

   5. 03-20: @Sridhar Rao there is an O-RAN logo at docs.o-ran-sc.org. @David Kinsey [AT&T] It is there since beginning. If O-RAN does not approve it, we can change it. @James Li to reach out to PTL for DOC project, Wichen Ni

   6. 03-06: @Tracy Van Brakle OSC development efforts in Rutgers will be supported by new tools (O-RU, RICtest). Finalizing the procurement with O-RAN office now.

   7. OSFG updates:

      1. Workshop:

         1. 04-17: a registration page is available (including visa letters), but only five people have registered so far; @David Kinsey [AT&T] encouraged to register both OAI and OSFG; we will be able to join the workshop either remotely or in person; @Sriharsha Rao needs to contact to OSFG if non-member would like to join the workshop.

         2. 04-10: registration announcement has gone out on https://groups.o-ran.org/g/OSFG/message/231; we can use this registration if VISA is needed for workshop attendance.

         3. 04-03: @David Kinsey [AT&T] will send e-mail to @Irfan Ghauri (EURECOM/OpenAirInterface) and @James Li to discuss whether the registration is needed for outside O-RAN members; @David Kinsey [AT&T] in terms of workshop later in this year, detailed location and dates will be discussed after Kista; 

         4. 03-27: workshop will be in Kista, Irfan and John will be present, not David. Local contact known to align details. David will share the agenda with Sridhar. John will manage the booking of a room.

         5. 03-20: @Sridhar Rao will reach to other LNF projects if they are interested if the date is decided. @David Kinsey [AT&T] if its in Kista, then the date is set. It is not sure if its full day/half day. @Sridhar Rao will make a poll to see who from OSC can join on 23rd of May. @James Li will add a topic on Monday's OSFG call to prepare a paragraph about it which Sridhar can share with other projects.

         6. 03-20: @David Kinsey [AT&T]can send a mail to reflector about the possible topics. Will push at OSFG. No other update.

         7. 03-13: currently three options, see below. 

         8. OAI workshop:
            
            

            1. 04-03: @John Keeney (Ericsson EST) the facilities are secured in Kista, it would be good to have hands-on workshop as well.

            2. 03-13: @David Kinsey [AT&T] May 21-22 (Wed-Thu) in Kista, Sweeden. If we would be present, we need to start preparing the line-up. So far we do not have the confirmation from various communities if they can attend - deadline is in two weeks, it will be difficult to manage. https://openairinterface.org/summer-2025-workshop-the-openairinterface-path-to-ai-driven-6g/ 

            3. 03-13: @John Keeney (Ericsson EST) might be able to secure an Ericsson location in Kista.

         9. Open Source workshop:

            1. 03-13: Other option is to join the LNF at end of June in Denver. We would still need to work on it soon. https://events.linuxfoundation.org/open-source-summit-north-america/

            2. 03-06: @Tracy Van Brakle we should discuss demos with OAI and Nephio - better to wait for David and Irfan to be back

         10. Workshop at O-RAN F2F

             1. 03-13: Possible, It will be difficult to collocate due to large overlap with other O-RAN meetings. OSC co-chairs are also active in the WGs as well as many of the TOC members.

      2. O-RAN SCCL enforcement:

         1. 04-17: @Jakub Novy [DTAG] in progress, trying to get closed.

         2. 03-20: @Jakub Novy [DTAG]: still waiting for O-RAN legeal, OCOP clarifications.

         3. 03-13: @Jakub Novy [DTAG]: in progress, pending confirmation from O-RAN legal.

         4. 03-06: @Jakub Novy [DTAG]: in progress, received feedback during F2F, demo repo prepared, OSARP document is under development.

      3. Collaboration with OAI (lab interconnection) and Nephio

         1. 03-20: @Martin Skorupski OAI and Nephio artifacts are already in one lab in France, so it works.

         2. 03-06: no update

      4. OSFG - OSC/OAI integration in furtherance of Super Wireless RAN blueprint @Tracy Van Brakle.

         1. 03-06: no update

      5.  Face-to-Face Meeting

         1. 03-06: Jinri: good event. We discussed the collaboration with standardization part, workshop, there were on-site and on-line demos. Next F2F planned for June.

   8. 3GPP & O-RAN ALLIANCE Joint Workshop on 6G Coordination

      1. 04-10: joint work shop will be held on Apr. 24 and 25; the purpose is sharing perspectives and aligning expectations between 3GPP and ORAN regarding 6G development to keep compatibility for management system. 

   9. IEEE GLOBECOM 2025 O-RAN workshop

      1. 04-10: @bimo fransiscus asisi O-RAN workshop sessions will be planned on Dec. 9 to 11 on Taipei; keep seeing whether we can get a representation of O-RAN SC.

6. Other

   1. @Ray-Guang Cheng invites to CFP of Industry Panel of IEEE GLOBECOM 2025, 8-12 Dec. 2025, Taipei, Taiwan (https://globecom2025.ieee-globecom.org/authors/call-industry-panel-proposals) @James Li to followup in China Mobile.

7. Old Business

   1. ASN.1 compiler

      1. 04-17: @Sridhar Rao still working for delete the ASN.1 compiler.

      2. 04-10: the archive ASN.1 compiler will be deleted by @Sridhar Rao Apr 10, 2025 .

      3. 04-03: @Sridhar Rao @Martin Skorupski @David Kinsey [AT&T] Motion to approve; Seconded by @Sridhar Rao; No Objections, the motion for "deleting the archive for the ASN1 compiler that is in error" is approved; @Sridhar Rao will delete the archive with error.

      4. 03-27: @Martin Skorupski: wiki page created based on discussion last week: ASN.1 Compiler. There is a pointer at gerrit to very old and unused compiler. Some people were using the Nokia one which is not too active either. Suggestion is to use another ASN.1 compiler, which is up-to-date. The code needs to be changed to reflect the change. This wiki can be a guidance for the future.

      5. 03-20: ASN.1 compiler issues - can we switch to the OAI one? There is also almost empty repo which needs to be updated/deleted. @bimo fransiscus asisi we need some official step to inform projects to use a different compiler. @Martin Skorupski will prepare a material for next meeting and vote.

   2. RSAC co-chair

      1. 04-17: no update; still looking for. 

      2. 04-10: no update. still looking for a new RSAC co-chair.

   3. 03-20: still looking for a new RSAC co-chair.

   4. 02-13: RSAC: We'll begin that solicitation today for another RSAC co-chair, as Ritwick confirmed this week he doesn't have the capacity to continue. Anybody who wants to self nominate or knows somebody that would be interested can propose

   5. Project Updates
      
      

      1. RSAC - @Rittwik Jana or @Martin Skorupski 

      2. INT - @bimo fransiscus asisi 

         1. 04-17: @Peng Lu (Deactivated) preparing to share a configuration to connect ODU low to TM500; after that we try to integrate xFAPI and then ODU high; The goal is to ensure all parts work correctly.

         2. 04-10: working for reconfiguration of their lab to reproduce TM500 related issues; @Peng Lu (Deactivated) will share the configuration to @Ray-Guang Cheng to duplicate Intel's test results; some NDA issues seem to need to be solved, @Peng Lu (Deactivated) will follow-up the issues.

         3. 04-03: @Peng Lu (Deactivated): will find more efficient way with @Ray-Guang Cheng to debug TM500 related issues. @Ray-Guang Cheng will support joining face-to-face meeting in Japan. SMO blueprint Nephio, @John Keeney (Ericsson EST)

         4. 03-27: @bimo fransiscus asisi: There is a Discussion End-to-End Integration page to have end-to-end call in INT project. Call for anyone who wants to participate. There is one energy use case from TIFG. It was discussed at the RSAP. Feedback welcomed.

         5. 01-09: @Ray-Guang Cheng: Problem with integrated O-DU not communicating with TM-500. @David Kinsey [AT&T]:Need project help to debug. RSAC to help do incremental builds to identify when disconnect occurs: 1) ODULOW → TM500 2) xFAPI->ODULOW→TM500 5) ODUHIGH->xFAPI->ODULOW→TM500. Need to isolate since all three components indicate they don't have a defect but integrated build doesn't work.

         6. ASN.1 Fix

            1. 01-16: Still open - Status remains the same due to absence.

            2. 01-09: @bimo fransiscus asisi: Need ASN1 fix. @abdulwahid.w: Nokia has a resource but haven't reached out since new year. Wahid will get a status.

         7. SMO blueprint

            1. 04-03: @David Kinsey [AT&T] and @John Keeney (Ericsson EST) proposed to make a base blueprint for use-case independent platform to reduce the burden of integration.

      3. INF - @Jackie Huang 

      4. RIC - @abdulwahid.w 

      5. RICAPP - @Sunil Singh 

      6. SIM - @Alex Stancu 

      7. OAM - @Martin Skorupski 

      8. SMO - @Seshu Kumar Mudiganti 

      9. Non-RT RIC - @John Keeney (Ericsson EST) 

      10. AIML - @subhash

      11. ODUHIGH - @Ankit Barve 

      12. ODULOW - @Peng Lu (Deactivated)

      13. DOC - @Weichen Ni 

   6. Marketing Plan: Working with LNF and ORAN Alliance teams to increase Awareness and Visibility of OSC Work
      
      

      1. 03-20: @Sally Cooper K release approved by O-RAN board. Still need approval from Intel - contact is PTL for ODU low Peng Lu

      2. 03-20: @Sally Cooper there is still old O-RAN logo on wiki. @Sridhar Rao will update it.

      3. 03-13: @Sally Cooper working on F2F blog, youtube channel prepared. LNF newsletter updates planned for today.

      4. 03-13: no feedback from O-RAN received. @Sally Cooper to reach to Jindrich about it.

      5. 03-06 @Sally Cooper: PR now with O-RAN legal, on LNF side is all good. It will be shared on O-RAN OSC channel and LNF channel after approval.

   7. Internship update