Time & Location:

Daylight savings time - Changing for some people from next week

Daylight savings time starts next week in US.
During Winter→Summer DST changeover we follow US time
In 3 weeks Daylight Savings time changeover happens in Europe.

Meeting times may fluctuate in coming weeks. Please follow the calendars!
https://lists.o-ran-sc.org/g/main/calendar

  • 2023-03-05: 7am PST | 10am EST | 15:00 UTC | 15:00 GMT | 16:00 CET | 17:00 EET | 20:30 IST | 23:00 CST | 00:00 JST (Thurs)
    • Today
  • 2023-03-12: 7am PDT | 10am EDT | 14:00 UTC | 14:00 GMT | 15:00 CET | 17:00 EET | 21:30 IST | 22:00 CST | 23:00 JST
    • Meeting will be an hour earlier for some Asian attendees - and stay like this for ~6 months
    • Meeting time will be an hour earlier for European attendees - but will change back to 'normal' time soon
    • Daylight savings change in US - Meeting time will not change for US attendees
  • 2023-03-19: 7am PDT | 10am EDT | 14:00 UTC | 14:00 GMT | 15:00 CET | 17:00 EET | 21:30 IST | 22:00 CST | 23:00 JST
    • Meeting time remains an hour earlier for European attendees - but will change back to 'normal' time soon
  • 2023-03-267am PDT | 10am EDT | 14:00 UTC | 14:00 GMT | 15:00 CET | 17:00 EET | 21:30 IST | 22:00 CST | 23:00 JST
    • Meeting time remains an hour earlier for European attendees - but will change back to 'normal' time soon
  • 2023-04-027am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST
    • Daylight savings change in Europe - Meeting time returns to normal for European attendees
    • Back to the normal time for everyone now - 14:00 UTC
  • 2023-04-09: 7am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST

Meeting Detail: Times & Joining Info

Tuesdays at 15:00 UTC     (14:00 UTC in Summer DST Northern Hemisphere)

https://us02web.zoom.us/j/89069708424?pwd=aGJOZm54eTUxd0FXR0VCU1N0ejBrUT09

  • Ensure you are signed into your Zoom account to join.
  • Meeting ID: 890 6970 8424. By Phone: Dial in (Local numbers): You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
  • Calendar: https://lists.o-ran-sc.org/g/main/calendar
  • NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. 
    • Winter (non-DST) time (Q4, Q1) eventually stabilizes to:
      7am PST | 10am EST | 15:00 UTC | 15:00 GMT | 16:00 CET | 17:00 EET | 20:30 IST | 23:00 CST | 00:00 JST (Thurs)
    • Summer Daylight Savings time (Q2, Q3) eventually stabilizes to:
      7am PDT | 10pm EDT | 14:00 UTC | 15:00 BST | 16:00 CEST | 17:00 EEST | 19:30 IST | 22:00 CST | 23:00 JST
    • (During Winter→Summer DST changeover follow US time. Summer→Winter DST changeover follow Europe time)

  • Meeting ID: 890 6970 8424
  • You will need a Participant ID so you will need to join the meeting from a Zoom client first to get this.
  • Dial in: (Local numbers)
    • +1 646 558 8656 US (New York)
    • +49 30 5679 5800 Germany
    • +49 69 3807 9883 Germany
    • +353 1 240 8941 Ireland
    • +46 8 4468 2488 Sweden
    • +46 8 5016 3827 Sweden
    • +358 3 4109 2129 Finland
    • +358 9 7252 2471 Finland

Please checkout the calendars:

Anti-Trust Notice

Date

Attendees

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

Contents

Recording

Notes:

Housekeeping:

OSC Project roundup:

News from OSC TOC call last week

NONRTRIC (John Keeney)

  • 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
    • 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 Shekhar Pandey)

  • No update this week

SMO (Seshu Kumar Mudiganti)

RSAC (David Kinsey Rittwik Jana)

AI/ML platform project (Joseph Thaliath)

Short discussion on CVE reports for OSC functions (Martin SkorupskiJohn Keeney& 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: 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 (smile)


Meeting ends 22 min