2024-03-05 Meeting notes - Joint OAM / NONRTRIC / SIM Community meeting

Time & Location:

Anti-Trust Notice

• Antitrust Policy Notice

• Antitrust Policy

Date

Mar 5, 2024

Attendees

• @John Keeney (Ericsson EST)(Ericsson EST & OSC NONRTRIC)

• @Martin Skorupski (Highstreet & OSC OAM)

• @Alex Stancu (Highstreet & OSC SIM)

• @James Li (CMRI & OSC INT)

• @Aravindhan Ayyanathan (Ericsson EST)

• @Rohith Rajneesh (Ericsson EST)

• @Varadarajan (Samsung)

• @RAVITEJA KARUMURI (EST) (Ericsson EST)

• May not have captured a full correct attendee list for this meeting  ... please add/remove yourself

See also / co-located (ONAP/O-RAN-SC/SMO - Meeting)

• Co-located with ONAP 2024-03-05 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting)

Contents

Recording

Notes:

Housekeeping:

• Calendar:

  • https://lists.o-ran-sc.org/g/main/calendar

  • https://lists.onap.org/g/onap-meetings/calendar

  • See section at top about Daylight Saving Time updates!

• OSC SMO project calls now move to its own time slot - alternate Thursdays

  • See OSC RSAC Calendar: https://lf-o-ran-sc.atlassian.net/wiki/display/RSAC/calendars

  • See also OSC Meetings calendar: https://lists.o-ran-sc.org/g/main/calendar

  • (Note this meeting to open to anyone, including non-ORAN members)

  • We will maintain this slot for ONAP Alignment, and try flag issues/question to/from SMO meetings.

  • See OSC SMO Project meeting notes

• See also OSC AIML Project meeting notes

OSC Project roundup:

News from OSC TOC call last week

• https://lf-o-ran-sc.atlassian.net/wiki/display/TOC/#ORANSCTechnicalOversightCommittee(TOC)

  • Last week's TOC (Thursday):

    • No Update this week. See minutes.

  • This week's TOC (in 2 days):

    • Hope to mention CVE topic - see below

    • Update from POWDER lab team.

NONRTRIC (@John Keeney (Ericsson EST))

• Short update this week:
  Continuing tasks as mentioned last week.
  Making Good Progress

• Last Week

  • Maintenance I-Release

    • No deliveries.

  • Continue work on rApp Manager - as a focal point for tying together alot of other existing activities

    • Working on some sample rApps. e.g. See Release J: Simple rApp using Hello World Microservice

    • Aim to have an updated version in coming weeks

  • Continue work on Service Manager - again pulling together alot of work on Service Exposure in previous releases

    • Aim to have a first functional release in coming weeks

  • Continue maturing the A1-Policy Controller function (ref ONAP) - including a potential new NBI (v3) to achieve R1 alignment

    • Current API will be maintained but deprecated for several releases to come.

    • New API development ongoing

  • Will need to de-prioritise many of the older less-used NONRTRIC functions - we welcome others in the community to help take these on if interested.

    • Need to study how/if we can achieve R1-DME alignment. Specs continue to diverge from our implementation - with alot of effort need to align.  We welcome contributors to help here.

  • Working through reviews for changes to it/dep charts. Main focus on A1-PMS configuration functionality & state.

    • Latest updates merged (Release I). Still verifying. Good progress

SIM (@Alex Stancu)

• No major change since last week.

• Work in progress continues.

OAM (@Martin Skorupski)

• In a rush today ... so short update:

• Working through some confustion in OAM architecture. Seeking feedback from Wg10 team

OSC Integration / INT (@James Li)

• Discussions with POWDER team.

  • potential for closer engagment with OSC, and would like to get feedback/updates/news of OSC using POWDER.

  • Note POWDER has a good OAI setup & would welcome even better engagement

  • Will briefly discuss at TOC this week.

O-DU (@Vidhu (Deactivated))

• No update this week

SMO (@Seshu Kumar Mudiganti)

• No update this week.

• Meeting notes Meeting notes

RSAC (@David Kinsey [AT&T] @Rittwik Jana)

• No update this week

• Minutes: 2024 RSAC Meetings 

AI/ML platform project (@Joseph Thaliath)

• Minutes & Meeting: Meeting notes

• Calendar: https://lists.o-ran-sc.org/g/main/calendar

• No update this week

Short discussion on CVE reports for OSC functions (@Martin Skorupski & @John Keeney (Ericsson EST)& @Alex Stancu )

• @Martin Skorupski mentioned some vulnerabilities identified in OSC (near-RT-RIC PLT) project, with associated CVE vulnerability reports

• Discussed at OSFG 

• https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=O-RAN

• Good to see issues being identified by the community, and feedback via JIRA tickets. However concern about CVE reports resulting.

• But how should we handle such CVE reports? Do we need to handle them at all?

• LF tools should be used to identify some identifiable vulnerabilities.

• @Alex Stancu SOme of the CVEs refer to DoS attack, which would require load testing & stress testing. LF tools/scans would not identify these perhaps anyway?

• @John Keeney (Ericsson EST): In NONRTRIC we do not claim nor attempt to produce commercial-grade/product-grade code or functions. So do not feel that CVE reports would be appropriate.
  If a vendor wishes to use OSC NONRTRIC code/functions in products or commercial networks then it is their responsibility to identify/correct/mitigate vulnerabilities. (And hopefully contribute back)
  We do not have the scope, resources or ambition to produce CVE-free functions except as best effort.
  If CVE reports are raised against NONRTRIC functions then we would need to consider archiving/removing functions that are not actively developed/maintained.
  We would also need to consider how to mitigate perception/reputation issues where CVE reports are created or where functions are misused in a commercial setting without additional hardening/verification.
  Other projects/PTLs might not have any issue with this.

• Hope to discuss in TOC for guidance.

ONAP Update (@N.K. Shankaranarayanan)

• No update this week

ONAP/OSC Usecases (@N.K. Shankaranarayanan)

• No update this week.

Disaggregated SMO Flows (@N.K. Shankaranarayanan)

• No update this week

Questions / Comments / AOB:

• None this week.

• Quick meeting this week

Meeting ends 22 min