/
2025 Q3 + Q4

2025 Q3 + Q4

2025 12 18

Recording 

Meeting Recording: 12-18-2025 Meeting Recording

 

Agenda

  • Host: @David Kinsey [AT&T] Scribe: Ultan Kelly (Viavi)

  • Previous scribe: 

    • 2025 => December: Ericsson; November: Samsung; October: China Mobile; September: TIM; Aug: Orange; 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

Company

Contact Name

Attendance

Alternate Contact

Attendance

Company

Contact Name

Attendance

Alternate Contact

Attendance

AT&T

David Kinsey Co-Chair

X

 

 

China Mobile

Jinri Huang Co -Chair

X

James Li

 

Deutsche Telekom 

Jakub Nový

X

 

 

Ericsson

Sandeep Sarma

 

John Keeney

X

NTT DOCOMO

Yasufumi Morioka

 

Minami Ishii

 

Nokia

Arunkumar Halebid

 

Abdul Wahid

X

Orange

Julien Boudani

X

 

 

Radisys

Ganesh Shenbagaraman

 

 Ankit Barve

 

TIM

Andrea Buldorini

X

Sergio Benco

 

Wind River

Jackie Huang

X

Jon Zhang

 

Viavi Solutions

Ultan Kelly

X

Baruch Friedman

 

Samsung

Avinash Bhat

 

Peter Moonki Hong

 

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

    3. Next Meeting Jan 8, 2026. No meeting 12-25-25, 01-01-26

    4. January 2026 Scribe

    5. Release Update

    6. New business

      1. Letter of Recognition for Bimo: Bimo Letter of Recognition.pdf

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

      1. SCCL enforcement

      2. CVE Changes in O-RAN Policy

      3. OSFG Adhoc (UNH)

      4. Incoming LSR from WG11

    8. Old Business

    9. AoB Future New Agenda Items and Announcements 

  2. Review and Agree to Minutes of Previous Meeting

    1. Decision:   Motion to Approve @Jakub Novy [DTAG] seconded by  @Julien Boudani . Minutes form 12-11 are approved

  3. Scribe for January 2026 is AT&T (With assistance from China Mobile)

  4. Release

    1. 12-18:

      1. Motion to allow the Superusers to branch, tag and commit the various contribution of the Integration Project to the M-Release. (It was noted that Int project was branched for the first time for the L-Release) that it was the. Motion to branch Integration project proposed by @David Kinsey [AT&T] and seconded by @John Keeney (Ericsson EST) and motion was passed. @John Keeney (Ericsson EST) and @Martin Skorupski to branch.

      2. The O-DU projects are not updated in this release. RICAPP was updated.

      3. @David Kinsey [AT&T] made the motion for the Release. Motion carried to make the M-Release. @Sridhar Rao to close out.

      4. @Sally Cooper to see if we can push the release notification through social channels

    2. 12-11:

      1. Vote on the M-release decision to take place on 12-18-2025 Meeting

      2. RIC App: Still no update.@David Kinsey [AT&T] to follow up.

      3. Scans are complete and @Sridhar Rao noted that there are no blockers.

      4. Tagging will be complete next week. RIC-APP and DU projects may not contribute to release. Opportunity to add in May Maintenance release

      5. O-DU Low and High ‘M-Release page’ need to be updated to reflect current PTLs and status

    3. 12-04:

      1. RIC App: No update this week so check again next week

      2. @David Kinsey [AT&T] noted O-DU High, O-DU Lo and RIC App are outliers for the release. xFAPI is expected so need to confirm with Intel. Worst case scenario is that a motion is called for the release without these three components

      3. Scans started and any issues to be to be addressed by end of next week.

    4. 11-27:

      1. Release Schedule: The target release date is set for the end of the last week of the month, likely between Christmas and New Year.

      2. RIC App: Sunil will update the release page next week.

      3. Code Scans will begin scans next Monday (post-Thanksgiving).

      4. ODU High Project: There has been no response from @Ganesh Shenbagaramanat Radisys regarding ODU High.@Sridhar Rao and @David Kinsey [AT&T] will attempt to find alternative contacts to clarify the company's direction.

      5. Integration Project (INT): PTL is stepping down as he has completed his studies and accepted a new job. Prof Ray is looking for a student to take over the role.

    5. 11-20:

      1. Timeline: The final release vote is being targeted for the week of December 18th (specifically the 18th) to avoid the TSE meeting falling on Christmas Day.

      2. PTLs were asked to update their release notes and highlights for the M release.

        • Highlights have been updated for SIM, OAM, and Integration & Test, but are still missing for non-RT RIC, RT RIC, RIC Apps, and AIML. [Action Item: PTLs]

        • There is still no clear status on the ODU High project due to the unresponsiveness of the PTL. @Sridhar Rao to follow up.

        • @Sridhar Rao will collect and present project commitment statistics during the next meeting.

        • The scanning process is scheduled for the first week of December. This timing is to allow sufficient time to address any cleanup, changes, and commits necessary to correct scanning errors, including License validation.

    6. 11-13: There is currently no Project Team Lead (PTL) for ODU High due to layoffs (Ankit and one other developer from Radisys), leaving the project without anyone to fill in release notes or push code.

      • Action Item: @Sridhar Rao will contact @Ganesh Shenbagaraman at Radisys to determine the company's commitment to the project, including whether they will provide a replacement PTL or give up the project. Sridhar plans to share an update by the following Monday.

      • Release Timeline

        • Aim is to have the PTLs' release notes wrapped up by the first week of December.

        • The final vote for the release is planned for the week of the Dec 18th.

    7. 11-06: @David Kinsey [AT&T] proposed the below next steps for the release

      • Current Status: The group is in Week 19 of the release, and Dev Sprints are expected to wrap up this week.

      • Timeline Proposal:

      • Final Release Vote: Proposed for the week of December 18th (Week 25).

      • The goal is to wrap up the release starting at the beginning of December to avoid working through the last week of the year and the holiday period.

      • Action Item for PTLs: PTLs need to start filling in the checklist with their goals and accomplishments/highlights to prepare for the review starting next week. This includes getting all project documentation in order.

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

    1. 12-18: David Kinsey acknowledged contributions made by @fransiscus bimo and reviewed and issued a formal letter of recognition for his achievements with the OSC, including ES Savings App development, lab setup and event participation. Bimo’s pursuit of excellence and consistently positive demeanor was noteworthy especially significant given there was no renumeration for the role. @David Kinsey [AT&T] makes a motion that the letter is endorsed by the TOC and @Julien Boudani to second. Motion carried and David to update the letter and send to the TOC, Professor Ray and Bimo.

    2. 12-11: No updates

    3. 11-20: The proposal for a semi-standalone service model for SMO projects has been passed to the RSAC. The RSAC will discuss the impact and viability of this feature for the N-release with the SMO-related projects.

    4. 11-13: Proposal Update: SMO Projects to Build as if they are a Semi-Standalone Service, Leveraging ONAP

      1. Discussion continued on the proposal to integrate SMO projects (specifically SMO OAM, AIML, and non-RT RIC) with ONAP/OOM. There are changes required on OOM side to integrate these projects.

      2. The integration is a technical change, not an organizational one. There are no technical blockers for the integration.

      3. The proposal will require resources to contribute to the OOM and INT projects. @Sandeep Sharma agreed to follow up with @John Keeney (Ericsson EST) and others (Ericsson/ONAP) regarding any potential gaps and will revisit the topic next week.

    5. 11-06: Proposal: SMO Projects to Build as if they are a Semi-Standalone Service, Leveraging ONAP

      1. ONAP Model: ONAP has separated common services (OOM) from individual projects, allowing each project to define its own release schedule rather than being tied to the half-year ONAP cadence.

        • OSC Proposal: The proposal is to align the four core SMO projects (SMO, non-RT RIC, OAM, and AIML) to follow a similar semi-standalone service model, building off of OOM to create their own build.

        • Deviation: Unlike ONAP, these projects would still use the OSC documents project for documentation, and governance would remain with the RSAC and the TOC. Overall objective is to downstream these projects.

        • Next Release Feature: The first feature requested for the next release is for these four projects to implement building off of OOM.

        • Build Scripts Discussion: It was discussed that placing the build scripts in the Integration project might be better to simplify the process of building OSC components.

    6. ATT-2025.11.06-OSC-D-SMO Components as SEMI-Standalone ONAP Service-v01.pptx

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

    1. 12-11: TSC Meeting is next week to potentially make decision on LFN direction. @David Kinsey [AT&T] to put topic on Agenda for next TSC meeting, as the next step to give visibility to the board, via the EC. TSC Charter likely to change after any move.

      1. @Sridhar Rao to publish list of CVEs, possibly after the M-Release.

    2. 12-04: TSC Charter Discussion @David Kinsey [AT&T] presented the three options for the future of OSC and noted ORAN Board are discussing options and the path forward is pending board approval. @David Kinsey [AT&T] to upload the presentation to WiKi.

      1. Today, OSC are acting as an SOW for LF where TSC/TOC is appointed and controlled by O-RAN. There is an option not to change this direction.

      2. Technically Option 2, the LFN Forklift, is a good solution, as OSC projects need to integrate with RAN LFN projects. Migration would take about 2 weeks and offer significant budget relief for ORAN.TOC is currently appointed by ORAN but that would change.

      3. Initially it would be seeded with existing members but when the initial term expires a new vote would occur.

      4. LFN would like to announce at MWC 2026 but the ORAN Board are concerned that a move to a meritocratic model means loss of control and have open questions about budget and governance. LFN Forklift would require a new Charter under LFN.

      5. In the future, option 3 may occur as a natural evolution, where select OSC projects merge into LFN.

      6. OSC releases may be re-labelled as research grade

      7. OSC projects are not getting the care and attention they require and reflects the slow nature of ORAN.

      8. In particular, the lack of business case for near-realtime RIC is blocking progress despite the scale and value the OSC near-realtime RIC has demonstrated.

    3. 11-27: TSC Charter Discussion: @David Kinsey [AT&T] outlined three options currently under discussion regarding the future governance structure of the OSC. He will present a detailed document next week.

      1. Option 1 (Status Quo): Continue as is, with the TSC organized/approved by the O-RAN Alliance and hosted by the Linux Foundation (LF).

      2. Option 2 (LF Project Model): Move fully to an LF project structure. This would shift leadership to a meritocratic model (voted positions based on contribution) rather than appointed positions. This could impact the influence of companies that advise but do not contribute code directly.

      3. Option 3 (Hybrid/Move Projects): Move specific projects (e.g., Non-RT RIC, SMO, OAM, AIML) under other LFN projects where content overlaps. Projects like RIC apps, simulations, and O-Cloud would potentially remain or follow a meritocratic model under a new TSC structure.

    4. 11-20: TSC Charter Discussion: @David Kinsey [AT&T] shared an update on a proposal for an evolutionary change to the OSC TSC charter.

      • Current Model: Voting members are appointed by O-RAN.

      • Proposed Model: A shift to a meritocratic setup where TSC positions are elected.

      • Expected Impact: This shift would likely move influence toward vendors, who account for the majority of the code contributions.

      • Action Item: Voting members were asked to provide feedback on concerns regarding this potential change via email to @David Kinsey [AT&T] and @huangjinri@chinamobile.com

    5. OSFG updates:

      1. O-RAN SCCL enforcement:

        1. 12-11: The current O2 information model but does not match the API so we need a new API. Limited value for March train so unlikely to be useful until the July train.

        2. 11-20: The adoption of Spectral, an open-source tool, was discussed for validating API schemas (e.g., O2 IMS interface) and applying Linting rules. A custom rule will be needed to enforce the use of the correct SCCL license text.

        3. 11-06: @David Kinsey [AT&T] The SCCL was last checked and was expected to close. However, enforcement of the security requirements will not be done in the November release due to time constraints.

    6. IEEE GLOBECOM 2025 O-RAN workshop

      1. https://globecom2025.ieee-globecom.org/open-ran-summit-2025

    7. OSC/OSFG Update for TSC

      1. 11-06: OSC Charter: @David Kinsey [AT&T] highlighted that the proposed new charter mentions "open source communities" instead of specifically OSC, as the ecosystem now includes projects like Nephio and ONAP.

      2. 11-27: Globecom2025 hosting of the Open RAN Summit is on Dec 9th and 10th. https://globecom2025.ieee-globecom.org/open-ran-summit-2025

    8. O-RAN F2F meeting Dallas

      1. 11-06: @Martin Skorupski reported on the 2 OSC Demo sessions at the recently concluded F2F Workshop

        1. Key demonstrations included the oCloud deployment (INFRA project), AIML pipelines, and the Machine-readable format from TIFG.

          • The workshop featured fewer demos than previous sessions but allowed for more active Q&A and discussions.

          • Future Face-to-Face (Rome - February): @David Kinsey [AT&T] mentioned that the short timeline means this meeting will likely focus on planning the next release. A demo for the June timeframe was suggested to showcase the component builds of the SMO.

  7. Other

    1. 12-11:

      1. ORAN Summit, hosted by Globecom, noted to be in progress.

      2. Blueprints desired but limited progress, needs PTL

      3. Helm Chart Publishing has a process that is nearly in place. @Matt Watkins to complete this week.

    2. 12-04: @David Kinsey [AT&T] acknowledged @fransiscus bimo work as a PTL and would like input from the team to how Bimo assisted OSC and draft a letter of appreciation for him. @Ray-Guang Cheng to provide specific input.

    3. 11-27: Tooling & Infrastructure by @Matt Watkins

      1. Meeting Management (LFX vs. Zoom):

        1. @Matt Watkins demonstrated the LFX meeting platform, highlighting benefits like a "single pane of glass" for schedules, self-service invites, and automated transcripts.

        2. @Sridhar Rao noted previous hesitation because LFX accounts cannot be mandated for all attendees.

        3. It was agreed to reconsider migrating to LFX in the new year to reduce administrative overhead

      2. Helm Chart Publishing:

        1. @John Keeney (Ericsson EST) requires a process to release a full set of Helm charts/scripts for the upcoming release.

        2. @Matt Watkins reported that integration for credentials has been flaky, blocking the automated publishing process.

        3. Action: @Matt Watkins will implement a static credential fix to unblock the immediate release and work with John/Aravind to finalize the workflow.

      3. Release Job Verification:

        1. There is concern about existing Jenkins jobs due to lack of recent use.

        2. Action: @Sridhar Rao is to email PTLs requesting they pre-test staging and release preparation jobs immediately to ensure they work before the release deadline.

    4. 11-20: Infrastructure Maintenance by @Matt Watkins

      • A motion was made to approve a maintenance activity to update Gerrit next Tuesday, which is expected to cause minimal disruption (10-15 minutes of downtime during a half-hour window).

      • Motion to Approve Maintenance proposed by @David Kinsey [AT&T] seconded by @Jakub Novy [DTAG] The motion to approve the maintenance activity on the following Tuesday was passed.

    5. 11-13:

      1. ODU Project Future: There was an open discussion about the long-term strategy for ODU, especially since ODU High is stranded, and other potential code bases (SRS-RAN, OAI) are also in transition under OCUDU. The possibility of migrating the salient features of ODU into a new project like Duranta and then archiving the original ODU project was discussed.

      2. RIC Support: The need for the Near Real-Time RIC was brough up to support a new service model involving low-level physical layer signal functions. @Abdul Wahid will look into the roadmap to ensure the Near Real-Time RIC can support the required service

    6. 11-06: @David Kinsey [AT&T] reminded attendees that there is still an open position for a second co-chair to assist @Martin Skorupski with the RSAC meeting schedule. 

  8. Old Business

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

      1. 11-13: @Sridhar Rao updated that the intern activity. All the identified CVE gaps can be handled and the discussion on these topics progressing well.

    2. RSAC co-chair

      1. 09-18: @huangjinri@chinamobile.com still open. Call again for candidates

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

    3. Project Updates

      1. General

        1. RSAC -  @Martin Skorupski  

      2. INT - @bimo fransiscus asisi

      3. INF - @Jackie Huang 

      4. RIC - @Abdulwahid W (Nokia) 

      5. RICAPP - @Sunil Kumar 

      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

      13. DOC - @Weichen Ni 

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

    5. Next Meeting: Jan 8, 2026

2025 12 11

Recording 

Meeting Recording: Meeting recording for Dec 11th 2025

 

Agenda

  • Host: @David Kinsey [AT&T] Scribe: Ultan Kelly (Viavi)

  • Previous scribe: 

    • 2025 => December: Ericsson; November: Samsung; October: China Mobile; September: TIM; Aug: Orange; 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

Company

Contact Name

Attendance

Alternate Contact

Attendance

Company

Contact Name

Attendance

Alternate Contact

Attendance

AT&T

David Kinsey Co-Chair

X

 

 

China Mobile

Jinri Huang Co -Chair

 

James Li