Time & Location:

New Meeting Slot

We have now moved to new meeting slot Wednesdays at 16:00 UTC in Summer (DST), 17:00 UTC in Winter !


Please note our new Zoom Bridge

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

Meeting ID: 890 6970 8424



NOTE: During the "Daylight Savings Time" changeover periods (US vs Europe vs Asia) the time of the meetings may fluctuate. See the Calendar: (https://lists.o-ran-sc.org/g/main/calendar

Summer Daylight Savings time eventually stabilizes to: 9am PDT | 12pm EDT | 16:00 UTC | 17:00 BST | 18:00 CEST | 19:00 EEST | 21:30 IST | 00:00 CST (Thurs) | 01:00 JST (Thurs)

Winter (non-DST) time eventually stabilizes to: 9am PST | 12pm EST | 17:00 UTC | 17:00 GMT | 18:00 CET | 19:00 EET | 22:30 IST | 01:00 CST (Thurs) | 02:00 JST (Thurs)

  • Meeting ID: 890 6970 8424
  • 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

Date

Attendees

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

Contents:


Recording

Notes:

Housekeeping


OSC Project roundup

NONRTRIC (John Keeney)

SMO (Mahesh Jethanandani)

SIM (Alex Stancu)

  • Figuring out Netconf call home over TLS - needed for proposed O-RU usecase.
    • John Keeney Cert exchange is very tricky - similar issue with REST Callbacks over A1 (HTTPS)
    • Martin Skorupski Alex Stancuuser-4594e No clear answer - Need cert management function. Perhaps should check how this is done in "PNF registration using VES" - had a similar issue .... to check
  • John Keeney New Simulator Alex Stancu no update ... session at O-RAN F2F was re-scheduled

OAM (Martin Skorupski)

  • Requested to remove links to O-RAN specs - difficult where these links appear in already published docs/pages - should O-RAN Alliance enforce any license check before being able to access protected docs?

ONAP - OSC

Proposed O-RU usecase

  • Martin Skorupski Re OAM ...
    • need to be careful that call home messages do not use a new controller port each time - need to align IDs to prevent this.
    • need clarity on Yang models ... cannot re-publish 3GPP-based models, and use-case specific models should be discouraged ... for further study
  • John Keeney Re NONRTRIC/rApp
    • It is clear that this is not a real-world use case & not standards compliant in many ways, so it is not clear if there will be benefit in building more that a placeholder/minimum rApp ... e.g. a simple script.
      • (Will drive another NONRTRIC hello-world rApp use case to help drive requirements & nonrtric/smo platform services)
    • Need to check with Mahesh Jethanandani about plans for message router etc for this use case.

ONAP functions in Honolulu Martin Skorupski John Keeney user-4594e

  • AAF will not be included ...
  • Clamp merged with Policy

CII talk at O-RAN vF2F event

  • Need to figure out how to access NexusIQ scans for OSC code

ONAP Topology Service/Model (ref last week)Andy Mayer

ONAP CSIT Functions (ref last week)

O-Cloud question from Lasse Kaihlavirta

LFN vDTF Event - Session on ONAP/OSC/ORAN Alignment John Keeney Swaminathan Seetharaman Martin Skorupski Mahesh Jethanandani

Other