2025 06 26

Recording 

Meeting Recording: Link

Agenda

• Scribe: David Kinsey (AT&T)

• Previous scribe: 

  • 2025 => July: Radisys; 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: Notes not yet transcribed.

   3. Next Meeting Jul 3, 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:  Minutes have not been transcribed; 2 weeks pending.

3. Release

   1. 06-26: Release Tagging Non-RT RIC and SMO not tagged

      1. Non-RT RIC is on vacation, team needs John to confirm, he will be back next week

      2. SMO can be done today or tomorrow.

      3. Documentation can’t be completed until the other projects have finished tagging.

      4. L Release Q Wiki page needs update for Near-RT RIC as release contents is not clear

      5. TOC can approve today, question is the date

      6. Motion by @David Kinsey [AT&T] to set release date to Jul 2, 2025, second by @Ankit Barve , No objections motion carries, release date set for Jul 2, 2025

      7. Vote for release to be approved No objections, Release approved.

      8. @Sally Cooper will create the release communications, which will be done as a blog post. Announcement blog, will also go out on other channels.

   2. 06-19: None of the projects are tagged yet

      1. Some projects are still missing highlights

      2. Scan issue was corrected,, and scan was successful, still waiting for final confirmation

      3. After highlights, tagging, and documentation we can execute the release

      4. RSAC indicates several projects would like more time for project documentation before tagging.

      5. PTLs expected to attend 6/26 meeting and if not tagged be able to indicate the date that it will be complete.

   3. 06-12: Release Checklist started scans are completed, 1 item requiring a correction @Alex Stancu @Martin Skorupski will work the issue.

   4. 06-12: review L Release PTL contributions

   5. 06-12: Release verification difficult due to lack of evidence.

   6. 06-12: Leverage Release testing to show highlights. Requires identification and demonstration of highlights before INT does E2E release testing.06-05: Release Vote 06-26 TOC Meeting

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

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

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

   10. 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. 06-19: No feedback on CVE handling from other Open-Source communities.

      2. 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.

      3. 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.

      4. 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-12: UNH will host, 3rd week of November, 2 day event, day 1 discovery, 5 tracks, day 2 morning track workshops, how will they self-organize, Day 2 Afternoon, track readouts.

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

         3. 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.

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

      2. O-RAN SCCL enforcement:

         1. 06-19: Hopefully final version submitted to OCOP, won’t be in effect for July Train.

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

         3. 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.

         4. 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.

         5. 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. 06-19: Will not be Keynote by Chi Lin and O-RAN Chair, no panel

      2. 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-19: Need Business value of Open RAN software for O-RAN CFO to have for tooling funding. Reach out to Tracy Van Brakle for collateral.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. 06-19: Need build blueprints for features, by projects, might be request for 'M' release.

            1. Right now its very manual to get right file version set to demonstrate a feature, would like more automation

         2. 06-19: Students cannot be the ones doing debug and version control. They don’t have the time, especially right now as the term end is pending.

         3. 06-19: Current problem is not related to xFAPI but due to the new ASN.1 compiler.

         4. 06-19: Bimo cannot access Nexus, ticket open. Matt will work directly with Bimo and work through the problem,

         5. 06-12: ODUHIGH doesn’t need access to xFAPI code

            1. Testing will be integrated ODUHIGH-xFAPI-ODULOW → TM500

            2. Trying to get back to where SIB1 is working

         6. 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.

         7. 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

   1. @Matt Watkins is moving to finishing new flows which will replace Jenkins Jobs.

      1. Outputs Helm charts to Artifactory, JFrog, and DockerHub.

      2. Problem with user account. DockerHub might have a pre-existing account.

         1. recommend opening a ticket and find details on why ORANSC is not being allowed.

         2. If existing user, recover the account as others shouldn't be using that Id.

      3. Matt will present the new flows on Jul 10, 2025

• Next Meeting Jul 3, 2025

2025 06 19

Recording 

Meeting Recording: Link

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: Notes not yet transcribed.

   3. Next Meeting Jun 26, 2025 

   4. Release Update