Technical Charter for O-RAN Software Community

TOC Mail Lists

TOC Meeting Info

Technical Oversight Committee meetings are open to the public and held on Wednesdays at 8 AM Eastern Time USA.  World Time Zone Map

Zoom 2 Info:

• Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/6540568082
• Or Telephone: Dial (for higher quality, dial a number based on your current location)
  • 855 880 1246 (Toll Free), 877 369 0926 (Toll Free)
  • Meeting ID: 654 056 8082
  • International numbers available: https://zoom.us/u/acyy3hylQi

2019 05 01

Zoom Meeting Recording

Agenda

1. Call for Scribe (minutes owner) 
2. Roll Call & Quorum Check 
3. Review and Agree to Minutes of Previous Meetings
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
6. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

7. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

8. Planning for Next Meeting
9. Open Discussion
10. Any Other Business (AOB)
11. Meeting Summary (resolutions, new action items, etc.)

Minutes:

• Call for Scribe (minutes owner)
• Roll Call & Quorum Check

• Review and Agree to Minutes of Previous Meetings 
  • Vincent
  • Jinri
  • Jack
• Review of Today's Agenda
• Status of Open Action Items (Old Business)
  • Action Phil will go ahead and make the change to o-ran-sc.org and move away from oran-osc.org and provide feedback from IT team in two days.
    • Phil does not have a timeline and date from them and will continue to push.
  • Action Vincent will lead TOC based effort to identify and recommend what sub committees we want for the A release cycle.
    • Cautioning not to launch too many sub-committees. 
    • TOC must approve subcommittees.
    • All new sub-committees must adhere to ORAN Alliance.
    • Recommends launching one TOC subcommittee for use cases and requirements for releases.
    • Setup 1 subcommittee to make a proposal to TOC for use cases and requirements of the O-RAN Software Community releases.  
      • There is a use case task group that deals with ORAN use cases.
      • What will be the difference between the two use case groups?
      • In our software community we are working with releases such as "A".  We have our own schedule and ORAN Alliance has their own.  There must be strong links between ORAN Alliance and TOC.  The Software community must inherit what is there.  We need to define which use cases we will embark in release A.  
      • To make the software work there are use cases that are more functionally addressed here.  Whereas ORAN Alliance is looking at overall functionality.  There may be implementational use cases and not functional use cases.
      • There are use cases that WG1 has that stradles the stack.  There are use cases are santions.  You will need to exercise the use cases that are sanctioned by Alliance and determine if they can be developed.  
      • We have to define the end to end use cases by release.
      • This will be focusing on developing different working groups.  The use case in our subcommittee in our software community is not the use cases of the working groups.  Alliance is from a software perspective.  The working group use cases are functional.
      • Software group will be checked by the software interfaces group.  The end to end use case will be done by the WGs. 
      • We are far from full stack End to End.  But for people outside ORAN there are ETE use cases.  Such as deploy the software, deploy the RIC, a simple example of an xapp (MACD).  This will bring people together to show broader interested parties.
    • Rittwik is a part of the committee.  Lusheng has proposals of project structure.  Lusheng.  Action: Lusheng will post that to the list after the meeting.  Dave is somebody who can participate and start working on this first sub committee that is being proposed.  He is a software brand architect.  This meeting will grow as participants.  We have two zoom bridges to coordinate meetings between subcommittees. 
    • Proposal: Start this new subcommittee called Requirements and software architecture.  Remove use cases.
      • David agrees to remove use cases from the name of the subcommittee.
      • Is there a reason why security is a part of software architecture?
        • It was a topic of discussion.
        • At the point of releasing code we want to respond to vulnerabilities.
      • Jinri: I  can post but can not receive messages from the list.  There are many teams from China mobile using lists.  Contact Phil after speaking to colleagues.
        • Action: Vincent send Jack the proposal slides.
        • Action: Jack get the proposal on the website.
      • Vincent makes a motion for the creation of a subcommittee that is called requirements and architecture.
        • Jack
        • Jinri
        • David
      • Action: Farheen: set up the new committee in the wiki and new committee list.
      • David will be the lead in preparing the guidelines for our first release.  We can talk more about that.
  • Action: Projects: Jinri is leading.  Action: Lusheng will post the proposal for the projects.  
    • Lusheng will set up the structure to attract people to projects.  We know that RU and DU are minimal but it's good to set up the structure.  This will be worked on this week.  The meeting is used to summarize the weekly forum.  
      • Action: We will have a discussion 
  • Action: Need a volunteer to work with O-RAN WG.  The O-RAN Alliance TSC handles filling in the position O-RAN OFG. 
  • Action: Charter and License for Spec Code Project: To close with legal and Stefan.
    • Nothing for charter.  There are minor gaps to fill.
    • Jinri asked Hank steve and umesh are talking to Ericsson and Samsung.  Expecting to get the finalized job by the end of this week and sending to others.  The progress is huge because it is almost done.  Wait until the end of this week for the feedback.
    • Setting goals.  May 17th for the license.
    • Much of this is tied to ORAN business as an enabler for projects.
    • We had a goal to finalize the charter this week.  
      • Concerned that we have not seen emails or feedback from Stefan.
      • Action: Jinri will push Stefan and Hank
      • Action: Jack will push on the license.
  • Action: ToC membership slot filling.
    • Concerned that Viswa has not been able to attend because it's an early time slot
    • Last week on the EC call I brought this TOC membership issue to EC.  
      • EC does not recommend telecom italia mobile.
      • EC is concerned about Nokia.  They put 22 employees on software dev.  ORAN WG3 where Nokia is co-chairing and are not actively participating.  Concerned that the software collaboaration is not in line with software community.  Later on we need to talk to Nokia.  
      • AT&T has a conflict of interest.  AT&T has contributed seed code for non-real time RIC along with Nokia.  We are satisfied with their work.  The challenge is in the E2 interface.  The relationship has been good.  There are challenges.  But that is how it will be with the larger vendors.  They are bringing a significant team to work on this.  It is better to get them into the open source community than not.  We plan to drive the near real time RIC in this release.  We have comparable number of resources working in this space.  
      • Concern is WG3.  One is Nokia group in the Software community and the Nokia team in WG3.
      • We have to get beyond the politics and get moving on developing.
      • David Streibl: ORAN is the intitiator.  No spec work to back the work then potentially we will have a discrepency between the two projects.  If we don't solve this problem here and it will be harder to solve in later releases.  If you can warn the Nokia team that there is misalignment.
      • There will be a multi group talk between the two parties.  It will happen very soon.  Hank is on the EC.  
        • Hank left early last Friday
        • Open source is open.  We keep politics out of if.  It's about who participates and what they bring.  The challenge is how much do we drag one community into another community.  It should be driven by the open source community.
        • Align the work between groups but keep it open to all communities.  We don't want to focus on who is doing the work.  We want to take all contributions.

• Standing Agenda Items (Brief Status of Ongoing Activities)
  • Release Manager/Release Planning: Weekly TOC Scheduling
  • Report out from PTL: Stand-Up & Report Out on Blockers
  • Test & Integration Planning
  • Report Out of Sub-Committees
• New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
  • There is a ORAN Alliance meeting.  Action Jinri post it to committee mail list.
  • M0 starts in a few weeks and we have to recruit working.  We need people to pull together the requirements that will lead to epics, and user stories and start sprints.  You need to have the main goals and a list of requirements to be pulled into place.  In  a normal cycle in planning M1 they can work on preparing for the B release.
  • Naming convention for our releases.  Cities, rivers, etc...
• Planning for Next Meeting
• Open Discussion
• Any Other Business (AOB)
• Meeting Summary (resolutions, new action items, etc.)

2019 04 24 

Agenda

1. Call for Scribe (minutes owner) 
2. Roll Call & Quorum Check 
3. Review and Agree to Minutes of Previous Meetings
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
6. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

7. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 

8. Planning for Next Meeting
9. Open Discussion
10. Any Other Business (AOB)
11. Meeting Summary (resolutions, new action items, etc.)

Minutes:

• Introducing Phil Robb VP of Operations for Networking and Orchestrating at the Linux Foundation located in midwestern USA.  Will facilitate initial activities.
• Farheen and Lusheng are in Jack's organization to support the calls.
• Call for Scribe (minutes owner): Farheen Cefalu
• Roll Call & Quorum Check

• Review and Agree to Minutes of Previous Meetings: 
  • Activities tied directly to ORAN which is the specification charter, license, and filling out the TOC slots.
  • TOC Activities that have to be worked on by this team.
  • Motion to Accept the minutes: 
    • Jack Murray 
    • Vincent Danno
    • Toshiro Kawahara
• Review of Today's Agenda
• Status of Open Action Items (Old Business)

• Will update wiki page for detailed meeting info: when and Zoom info Farheen Cefalu 24 Apr 2019 
•  Avoid confusion about the two domain names:  oran-osc.org and o-ran-sc.org.  
• Action Phil will go ahead and make the change to o-ran-sc.org and move away from oran-osc.org and provide feedback from IT team in two days.   Waiting on reply from IT on a timeline within the next day or two.  Placed as an urgent request.  Phil Robb

• Follow up: Jinri to note onto O-RAN Alliance wiki 
• Get ToC members onto the mailing list, get mailing list info to prospective members Farheen Cefalu24 Apr 2019 
• Review to-do list items (Jack's email on 04/15)
  • O-RAN Specification Code Project charter – Yes we need to align a few remaining comments. I hope we can finalize this this week. (Jinri)
  • O-RAN Specification code License – We need to set a goal, timeline, and communicate it. I am concerned we have communicated to a few companies but not had broader reviews.
  • Fill TOC membership slots 6-12 (O-RAN Alliance TSC)
• On the TOC side, here are the next items to get accomplished

  • Set time for the weekly TOC meeting (David working it)

  • LF has assigned Phil Robb probb@linuxfoundation.org as our program manager initially. He will eventually assign this to someone else once established. I will send an email shortly.
  • Clarify the email list and domain names (Phil Robb)
  • Organize the TOC and establish a community best practices documentation including use of both licenses (Jack Murray)
  • Recruit a release manager and Establish a timeline I will share a target
    • What are goals for M0?
      • We have to find a release manager, integration and test, documentation lead, create projects.
  • Establish sub-committees then recruit PTL and participants
    • For the A release I was looking for one of the TOC members to help and gather requirements and talk to W8 and others and come up with a proposed list of sub committees and recruit the people needed for Software Architecture, Product Committees, 
    • Do we need sub committee first or do we need a project first?
      • In this case you need both but because we have a template for the project I am going to propose we work on that template for now.  We try to recruit the sub-committees first.  Pulling together people is much more work than putting together the project plan.  There is a lot of work in the requirements.  There are several roles in sub committees.  Is a security sub committee needed? 
      • I am asking for someone to come up with a proposal of sub-committees and a PTL for each committee they propose.
      • Vincent Danno - We can have a bottom up approach as you are proposing however I'm afraid by following that approach we may end up with many sub-committees while resources are limited?  Don't we want to find a common committee and then break it down after that.  
        • Yes, I am asking somebody on the TOC to think about and come up with a recommendation for the TOC to vote and approve.
        • Action Vincent will lead TOC based effort to identify and recommend what sub committees we want for the A release cycle.
      • Could you clarify the timeline?
        • Right now we go back to release page and click on release this is the proposed timeline until we finalize.  We want them identified by M0. 
      • Sprints are 3 weeks long.  At the end of each sprint we will set up a demo for what that sprint accomplished and test.  Aiming to have 80% of user stories completed because it's an open community.
      • Who is the appropriate person to take care of Security?
        • First decide a sub-committee then find a principal technical lead (PTL).  There are committers and code contributors.
        • Second have a clear set of requirements for the release.    
  • Establish sub-Projects then recruit PTL, Committers, and contributors
    • We need a volunteer to put together a proposed list of project.  Work with subcommittees.  Focus on whether we are going to do on real time RIC non real time RIC.  You don't have to do that on you own.  Will someone take the lead to get that organized?
      • Action: Jinri will take it as an initiative.
  • Continue to work with LF on infrastructure needs (user-d3360  current contact)
    • If no one has concerns I propose that we continue to have Lusheng in that role. 
  • O-RAN WG coordination and communications must be an on-going activity
    • Action: Need a volunteer to work with O-RAN WG.  The O-RAN Alliance TSC handles filling in the position O-RAN OFG.  
  • Charter and License for Spec Code Project: To close with legal and Stefan.
  • ToC membership slot filling.
  • During O-RAN Alliance TSC meeting last Wed regarding approvals for Lenovo and Nokia, we were asked to provide clarification on criteria and guideline on ToC member recommendation on O-RAN Alliance wiki.  Jinri proposed text.
  • Whether to discuss Intel and Radisys and put in the same proposal with Lenovo and Nokia to TOC.
    • Next Tuesday is another meeting opportunity to talk about this before the Wed TOC meeting.

• Standing Agenda Items (Brief Status of Ongoing Activities)
  • Release Manager/Release Planning: Weekly TOC Scheduling
  • Report out from PTL: Stand-Up & Report Out on Blockers
  • Test & Integration Planning
  • Report Out of Sub-Committees
• New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items 
• Planning for Next Meeting
  • Next week is May 1 which is a day off in most countries. 
    • Vincent Danno can make it. 
    • Jinri can also make it.  
    • Jack planning to attend.  Quorum reached 50% therefore will hold meeting
• Open Discussion
• Any Other Business (AOB)
• Meeting Summary (resolutions, new action items, etc.)
  • Resolutions 
    • We have a timeline for A
    • Vincent volunteered to lead the effort to form subcommittees
    • Jinri volunteered to lead project 
    • Jack volunteered to recommend
      • best practices
      • licenses
      • software agreements
  • New Actions
  • We need a naming convention for major release instead of calling them "A", "B", "C", etc... release. 
  • Change of domain name. 
  • Complete goals for M0
  • We need a lead for communications to the working groups.
    • add ORAN working group liaison
  • This meeting is open to everyone.  Please invite people to the meeting and encourage them to get involved.
  • Finish the license, charter, and naming the TOC members. 
  • Target for June release. 
• Closed 9:04 AM EDT 2019/04/24

Return to Agenda