zoom meeting recording: 2019-07-24-toc.mp4
Agenda
Roll Call & Quorum Check
Company | Contact Name | Attendance | Alternate Contact | Attendance |
---|---|---|---|---|
Jack Murray Co-Chair | x | |||
Jinri Huang Co-Chair | x | |||
David Streibl | x | |||
Masafumi Masuda | x | |||
Orange | Vincent Danno | x | ||
Viswa Kumar | x |
*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.
Here is my proposal.
1, for most occasions such as in the meeting minute, in the Release A epic document where there is no constraint on the naming, the name defined in O-RAN Alliance White Paper shall be used, which are:
non-realtime RIC, abbreviated as, Non-RT RIC, or NRT RIC;
near-realtime RIC, abbreviated as, near-RT RIC, or nRT RIC; // note, it it is about the platform, then the word “platform” should be explicitly spelled out.
2, For project name and the corresponding project key, as shown here at https://wiki.o-ran-sc.org/display/ORAN/Projects, proposal is:
"Non-realtime RIC (or Non-RT RIC, or NRT RIC) as the project name, with project key as “NRTRIC"
"Near-reamtime RIC platform (or near-RT RIC platform, or nRT RIC platform) as the project name, with project key as “RICPLF"
3, For repo name which requires lower case, digits, slash and dash, suggest to use “non-rt-ric” and “nrt-ric-plf” for Non-RT RIC and near-RT RIC platform, respectively.
Non-realtime RIC focus on feature functionality of A1-interface (consumer and provider), and closed-loop use cases.
OAM focus on align of O1 interfaces on ME and verification of related interface specifications.
Both projects will align activities on a case-by-case based for O1 interfaces (NetConf client ODL, and http-Server – ves-receiver from DCAE).
Current ONAP baseline should be Dublin for Release A
Standing Agenda Items (Brief Status of Ongoing Activities)
Test & Integration Planning - Lusheng
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items