Page History

...

Recording

• Recording (MP4)

Notes:

• Happy New Year!
  

• Meeting 16 December cancelled due to holidays
• Meeting 23 December cancelled due to holidays
• Meeting 30 December cancelled due to holidays
• This meeting: 06 January 2021
• Next meeting: 13 January 2021

...

• No major update
  • All OSC projects need to look at CII badging questions - ref toc 06/01/2020  https://wiki.o-ran-sc.org/display/TOC -
    • See Core Infrastructure Initiative (CII) Badging in OSC.

OAM (Martin Skorupski)

• Continuing to work on IPV6 support (Ref SDNC-895) - mainly problem connecting from ODL to other ONAP components.
  
• Continuing to study ODL Aluminium version usage ONAP (SR1 vs SR2). E.g. see https://jira.opendaylight.org/browse/NETCONF-744 Will discuss with Dan Timnony.

ONAP - OSC

• Andy Mayer ONAP modelling for O-RAN ... Will follow up in coming weeks.

• Swaminathan Seetharaman will report to ONAP TSC ... any additional input reqd.?

  • John Keeney Perhaps request TSC to reach out to OSC TOC & RSAC committees to help drive the alignment forward.
    
    • Swaminathan Seetharaman John Keeney Which concrete touch points would be good to drive this leadership-level discussion:
      • existing ONAP usecases (see Potential ONAP <-> O-RAN collaboration use cases)
      • OSC-SMO/NONRTRIC/OAM overlap,
      • ONAP Slicing (especially wrt ORAN-Alliance use case overlap)
      • New usecases?
  • Martin Skorupski It would be good to understand timelines/dates/cadences between ONAP & OSC to help clarify when/how requirements/releases in both projects depend on each other.
  • Martin Skorupski Yang copyright alignment & spec re-use remains a challenge ....
• Andy Mayer ONAP modelling for O-RAN ... Will follow up in coming weeks (next week?).

Other