Technical Charter for O-RAN Software Community

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 09 18

Audio recording: 

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x
   China Mobile	Jinri Huang Co-Chair	x
   Deutsche Telekom	David Streibl	x
   NTT DOCOMO	Masafumi Masuda	x
   O-RANge	William Diego	x	Vincent Danno
   Verizon	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.  

3. Review and Agree to Minutes of Previous Meeting
   1. Moved by user-2057e , seconded by Jinri Huang
      
      1. VOTE: 5-0.  approved.
4. Review of Today's Agenda
   1. New agenda items requested (DOC project committer approval request, INF project committer approval request, discussing license header) added to PTL reporting section.
5. Status of Open Action Items (Old Business)
   1. Action/ John Murray will try to get a representative from each PTL to provide someone to participate in the integration and test team activities.
      1. Service providers should be involved because they will understand what is expected of them.  It will understand what is working and what will work.  We need help in this community.  There is a high and low level activities.  Please reach out to Lusheng and get involved.  I expect all the PTLs to find a representative to participate.
         1. user-d3360: Nokia participation, further discussion with Highstreet and Rutgers.  Asking each project with software deliverables to send rep participating in integration and testing activities.
         2. Gil Hellmann: (windriver) will participate from INF.
   2. Action/ Tracy Van Brakle   continue discussion about Plugfest.  See where we can do plug and play activities at the MWC North Americas event.
      1. On track for December 2 and a white paper on December 5.  We should figure out something synergistic with China mobile. 
      2. Plugfest in Beijing and POC 
         1. Plugfest in Beijing, with real equipment
         2. PoC with OWL (Rutgers Winlab): Amber release
         3. How to promote.
            1. Jinri Huang encourage taking this opportunity.
            2. Tracy Van Brakle to provide writeup next week as base for blog, etc.   
            3. John Murray add to the wiki events page.  ToC member 
            4. Jinri Huang to talk to CMCC how to promote at Beijing slugfest
   3. Action/ Andrew Grimberg will check with the engineer of whether or not there is an automated process to auto-add the reviewers.
      1. Action/ Andrew Grimberg provide documentation and proposal.  
      2. Action/ Andrew Grimberg vet the TOC process with the TOC members.
      3. Action/ Andrew Grimberg provide clear instructions to TOC mail list on how TOC members can get a gerrit account and the process.
      4. user-d3360 no update from LF.  We should not be blocked by INFO.yaml.  If any blocker for new repo, we will raise to LF. 
   4. Action/ John Murray discuss the B release name.
      1. Action/ user-2057e start a poll for B release.
         1. user-2057e will work on this
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. user-59b16 got all the reports.  Will invite O-RAN WG cochairs to RSAC meeting, group by group so people going into F2F knowing the progress. Reports available from the RSAC link in the original Farheen email.
   2. Release planning link.
      1. John Murray We are at week 36.  Risk for near Realtime RIC Platform and xApp.  Start talking about B release schedule.  Plan to be approved: B release Dec 2nd.to June.  At the beginning there is a window for Amber maintenance release, --opportunity to close Release A tech debts.  
   3. Copyright
7. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non real time RIC (RAN Intelligent Controller) - John Keeney
   2. RIC Applications - Matti Hiltunen
   3. RIC Platform - Thoralf Czichy
      1. John Murray any update on the contribution blocked
         1. Thoralf Czichy escalated high up in Nokia.  we have verbal okay.  there are couple of conditions, none problematic.  One thing we must have clear scope.  Publishing E2 spec and ASN.1, legal discussion still on going.
         2. John Murray Filled copyright permission form for OAM project, currently under LF review, will submit to 3GPP as the first example.  Since the code hosted on LF repo, we work through LF.  We will see how this first one goes then others to follow.  O-RAN Alliance is also working with 3GPP.  This also include ASN.1 specifications.  
            1. Action/ Thoralf Czichyto send details of which spec, section, version, to John Murray
            2. John Murray Move this item to Standing Agenda Items from now on.
         3. Jinri Huang TSC requested AT&T and Nokia to report on misalignments between Near Realtime RIC OSC implementation and WG3.  user-59b16 we will need Paul Stevens from WG3 and Matti and other from OSC to start.  John Murray Start to work on this before the F2F.  Also how to manage the time line e.g. when Near Realtime RIC started there was no E2 yet.  Jinri Huangencourage other PTLs to think how to work with WGs, suggesting good documentation for communication.
            1. Action/ user-59b16 To organize meeting
   4. O-RAN Centralized Unit user-a934b
   5. O-RAN Distributed Unit High Sachin Srivastava
   6. O-RAN Distributed Unity Low Zhimin Yuan
   7. O-RAN Radio Unit (TBD)
   8. Operations and Maintenance - Martin Skorupski
   9. Simulations - Alex Stancu
   10. Infrastructure - Xiaohua Zhang
       1. Committer approval request for Jack Wang (Windriver) for PT Realtime platform repos and Jianqiang Wu (Lenovo) for AAL repos.
          1. Motion seconded by Jinri Huang,  5 - 0, vote passes.
          2. Discussion John Murray PTL should maintain a contact list for committers in each project.
             1. Action/ user-d3360to work with LF to get the current listing.
   11. DOC - weichen ni
       1. Committer approval request for Farheen from AT&T, Eric from LF.  
          1. Discussion: John Murray future plan for community approval process.  currently we ask this activity to come to ToC.
          2. Motion seconded by Jinri Huang, 4 - 0, vote passes.
   12. O-CU user-a934b 

8. Test & Integration Planning - Lusheng

   1. user-d3360 Need standard text for O-RAN Software License.  
      1. John Murray Forwarded to O-RAN Alliance, no response yet.  Jinri Huang Next week EC call I will remind them.
   2. user-d3360 SPDX identifier for Apache 2.
      1. John Murray email Trishan de Lanerolle to confirm there is no issue from LF, if no objection I am okay with it.  Bring this back next week.
      2. Action/ user-d3360contact Trishan de Lanerolle
9. Requirements Software Architecture Committee - Rittwik
   1. user-59b16 B release requirements to share on this meeting next week.
   2. John Murray clear demonstrable use cases as high priority.

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

11. Any Other Business (AOB)
    1. Thoralf Czichy just got email we got green light.  we can move back to open source now.
12. Meeting Summary (resolutions, new action items, etc.)

2019 09 11

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x
   China Mobile	Jinri Huang Co-Chair	x
   Deutsche Telekom	David Streibl	x
   NTT DOCOMO	Masafumi Masuda
   O-RANge	William Diego		Vincent Danno
   Verizon	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.  

3. Review and Agree to Minutes of Previous Meeting
   1. The minutes of the prior meeting were reviewed, and there were corrections. On motion made by Jinri Huang and seconded by user-2057e   the minutes of the September 4, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
   1. Action/ Jun Hyuk Song start the dialogue on the email list regarding the KPI monitoring xApp concern.  
      1. Jun has spoken to Matti.  Samsung has volunteered to work on the KPI monitor xApp.  Had discussion with Jun about what it means to be an xApp.  Ac xApp and simulator code.  Discussions are moving along.  Concern is that there is fairly little documentation in the LF and the ASA1 spec is not publicly available.  It makes it difficult for EU members to contribute.
   2. Action/ Claudio Coletti raise the issue of the E2 interface and WG3 schedule with the O-RAN Alliance.  
      1. David discussed w/ Claudio.  Presenting how to align spec for E2 will be ready to present to the TSC.
      2. There have been a range of discussions about how do we release the E2 and manage it.  Who owns the E2 spec and how do we document it.  3GPP and O-RAN are specifications.  We have communicated with 3GPP and there is a process of making a request from 3GPP.  Anyone making open source software for 3GPP should look at the wiki under Best Practices.  ASA1 - Jack will work on establishing a process for copyrites for 3GPP and O-RAN.
         1. Will there be a practice description of how to deal with 3GPP copyright information?
            1. Yes
               1. The O-RAN will be for material created under O-RAN Alliance?
                  1. Yes, I hope that will be broader so we do't have to do much work. 
                     1. Is O-RAN for finalized specs or work in progress?
                        1. It should cover both work in progress and final.  Normally we wouldn't know about wip and progress but since we have inside knowledge before the spec is published.  Jack will work through that.
         2. There was an email from standard development group who are coordinating the process of 3GPP.  Jinri shared with the community.  Call to community to identify the 3GPP issues and bring it back to Jack and Jinri.  
            1. For O-RAN that is correct.  For O-SC it is LF who owns the code and they need to sign off.  LF must be involved.  LF is the first gate.  That is where the information is downloaded from.  Should the PTL get started with the form?
               1. Yes, it's the ETC form.
               2. Do we have an estimate for the timeline?
                  1. Hard to say because it is our first time through it.  ETC has not addressed open source.  We're not asking for document or republish whole chapters but we are asking for tables and subsections.  
            2. Yingying - Implementation of the 3GPP stack.  If we don't have agreement from 3GPP then we can upload anything?
               1. We should not be copying in 3GPP specs.  
                  1. Is that the table or figures?
               2. Ganesh - for O-CU there is no challenge.  There is no issue.
                  1. If you're implementing software that follows the software instructions of how to send the message there is no issue.  Implementing the functionality is not a concern.  If you're reproducing the exact messages then it needs to be covered by copyright.
   3. Action/ John Murray will try to get a representative from each PTL to provide someone to participate in the integration and test team activities.
      1. Service providers should be involved because they will understand what is expected of them.  It will understand what is working and what will work.  We need help in this community.  There is a high and low level activities.  Please reach out to Lusheng and get involved.  I expect all the PTLs to find a representative to participate.
   4. Action/ Tracy Van Brakle   continue discussion about Plugfest.  See where we can do plug and play activities at the MWC North Americas event.
      1. On track for December 2 and a white paper on December 5.  We should figure out something synergistic with China mobile. 
      2. Plugfest in Beijing and POC 
   5. Action/ John Murray talk to user-d3360 about the issues with signing of names on the CLA.
   6. Action/ Andrew Grimberg will check with the engineer of whether or not there is an automated process to auto-add the reviewers.
      1. These are all related to the same item.  For the new repo we are learning as we go.
      2. Action/ Farheen Cefalu combine t
   7. Action/ Andrew Grimberg provide documentation and proposal.  
   8. Action/ Andrew Grimberg vet the TOC process with the TOC members.
   9. Action/ Andrew Grimberg provide clear instructions to TOC mail list on how TOC members can get a gerrit account and the process.
   10. Action/ Farheen Cefalu send a message to the PTLs to provide a one page summary of their progress in the last four weeks to the TOC mailing lists.
       1. Rittwik - we have 5 and 6 more to go.  Rittwik will be setting up a call to be prepared to have a discussion.  Please get your open summary by Friday.  A lot of people have updated it in their wiki status pages.  Action/ user-59b16 create a space where we can do a review and set up a meeting to review the summary docs.
       2. Sachin - I have updated O-DU but it got lost in the email.
   11. Action/ John Murray discuss the B release name.
       1. Action/ user-2057e start a poll for B release.
   12. Action/ John Murray 3GPP copyright discussion
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. Release planning link.
      1. Work with the documentation team to keep documentation up to date.
      2. Jinri - For the Friday O-RAN bring to the attention of the co-chairs.
         1. We are taking the wright ups from each PTLs.  Keeping it simple is fine.  Rittwik is collecting them and make sure they are accessible.  
7. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non real time RIC (RAN Intelligent Controller) - John Keeney
   2. RIC Applications - Matti Hiltunen
      1. I submitted a repo request and Jinri has approved.  
      2. On motion made by Matti Hiltunen to create a repo that KPI monitor xApp that calculates KPIs and exposes the xApps in the RIC and seconded by Jinri Huang
         1. VOTE: Vote taken, item passed.
   3. RIC Platform - Thoralf Czichy
   4. O-RAN Centralized Unit user-a934b
      1. On motion made by user-a934b to create a repo for O-CU seconded by Jinri Huang 
         1. VOTE: Vote taken, item passed.
   5. O-RAN Distributed Unit High Sachin Srivastava
   6. O-RAN Distributed Unity Low Zhimin Yuan
   7. O-RAN Radio Unit (TBD)
   8. Operations and Maintenance - Martin Skorupski
   9. Simulations - Alex Stancu
   10. Infrastructure - Xiaohua Zhang
   11. DOC - weichen ni
   12. O-CU user-a934b made a motion to create a repo for 

8. Test & Integration Planning - Lusheng

   1. Please reach out to Lusheng to see how O-RAN works.  Lusheng will be scheduling meetings around test and integration for the Amber release.
   2. O-RAN software license for Apache 2 we have standard text to make the claim that we have a style of license for apache2.  We do not have O-RAN license yet.  We can ask our internal company review?  
      1. yes, we will then forward it on to Stefan (legal).  He can then talk to individual company.  Include a copy of what we do for Apache 2 for Sefan.
   3. We do have projects who want MIT open source licenses.  How can we include upstream projects.  How should we proceed?  One way is we do not host their code we download build and us when those upstream projects.  Not ideal but it is a clean way to practice.  Another way is if we do need to make modifications to upstream project first.  In practice it is difficult to do it first.  Do the upstream project first and then do our change in your local repo.  Create an external dedicated directory where you maintain the MIT license.  This way there is a clear differentiation between licenses.  
      1. Trishan - check the compatibility and MIT is compatible.
      2. GPL is complicated you have to build it.  We will put it in the best practices.  Interproject relationships like ONAP, ETSY, LF, to build stronger relationships.  Akraino and Acumos are active projects where we can expand.
9. Requirements Software Architecture Committee - Rittwik
   1. We started the B release epics we want to share with the team.  Requesting all PTLs to improve and provide input.
      1. B release should include use cases that drive what we can test, demo, and deliver.  Specific work in each subsystem.  test team is driven by use cases, requirements, and team.  

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

    1. Start a discussion with alignment with community project ONAP, Akraino, Acumos
    2. Secondary project with code contributions.  If someone is interested in participating we can work on 
11. Any Other Business (AOB)
    1. Jinri - request for PTL when you hold a teleconference is it OK for PTL can record the meeting.  Issues with China meetings.  
12. Meeting Summary (resolutions, new action items, etc.)

2019 09 04

Zoom meeting: 2019-09-04_tsc.mp4

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x
   China Mobile	Jinri Huang Co-Chair	x
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Masafumi Masuda
   O-RANge	William Diego	x	Vincent Danno
   Verizon	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.  

3. Review and Agree to Minutes of Previous Meeting
   1. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by Jinri Huang and seconded by William DIEGO  the minutes of the August 28, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
4. Review of Today's Agenda
   1. Jinri - Claudia, new agenda item.  WG3 raised an issue and would like to add it to todays agenda.
5. Status of Open Action Items (Old Business)
   1. Action/ Thoralf Czichy read out the status of the issue with signing of the CLA and the open ticket. 2019-09-04: This is now resolved. Not sure where the problem was, but it's likely around companies where there are multiple CLA managers where multiple projects are managed. The whitelisting seems to work. I updated the instructions to properly also describe the case where there's only a CCLA and individual developers do not actually need to sign an additional ICLA. Also added some clarification in some of the steps: delta in "Signing Contributor License Agreement"
      
      1. Naming is still a little confusing.
      2. China Mobile has some questions on CLA.  We have two license.  For CLA does the CLA manager have to sign both?
         1. Yes. Both should be signed.
         2. It is OK to have two people sign two licenses.  
         3. The platform is still young and there were challenges signing the CLA.
            1. Action/ John Murray talk to user-d3360 about the issues with signing of names on the CLA.
   2. Action/ Farheen Cefalu  add link to other upstream projects such as ONAP on the Release Planning page.
      1. Action/ John Murray will be working with Farheen Cefalu for the next weeks to coordinate the release schedule.
   3. Action/ Brian Freeman will send Architecture link to Jack Murray.
      1. Action/ John Murray will work with Farheen Cefalu
   4. Action/ Andrew Grimberg will check with the engineer of whether or not there is an automated process to auto-add the reviewers.
   5. Action/ Andrew Grimberg provide documentation and proposal.  
   6. Action/ Andrew Grimberg vet the TOC process with the TOC members.
   7. Action/ Andrew Grimberg provide clear instructions to TOC mail list on how TOC members can get a gerrit account and the process.
   8. Action/ Tracy Van Brakle  OSC Amber PoC ("Plug-fest").  We need the TOC to decide how (or if) the Linux Foundation should (or should not) promote this particular LFN event.
      1. Slides are on the wiki
      2. China Mobile is sponsoring O-RAN "Plug-fest" in parallel with a O-RAN-SC Amber PoC "Plug-fest".  Do you want to promote the PoC Plug-fest?  It will be December 2nd.  The readout would be December 4th.  It will take place as a parallel track with some overlap. 
         1. China Mobile is planning to host the Plug-fest in December.  Is the PoC Plug-fest the same thing?
            1. This is a proof of concept vs. a Plug-fest.  The O-RAN Alliance Plug-fest is featuring open front-haul.  We want to compliment that with mPlane.
   9. O-RAN Alliance has a particular structure with LF.  There is no marketing activity from LF.  It is all budgeted to the O-RAN Alliance.  They have done some activities in the past.  It is conservative because of how it is funded.  It is not a simple activity to get the LF to promote or do work around LF activities.  Unlike ONAP that has a marketing activity funded around it.  We should look at how we can some activity as a promotion of a plugfest.  But give more attention to the Amber activities.  We should pick this discussion up and we should see where we can do plug and play activities.  Most on the A1O1 side and the xApp near Real time RIC.  Perhaps the simulator?  Does anyone know of an area that will have software at the end of release A? 
      1. We're trying to do a demo for NWC America around the December time frame. 
      2. Non real-time RIC?
         1. Demo ORAN 5G use cases with PNF Plug in Play.  Another demo, bulk management data that are 36PP aligned.  Show the hybrid architecture vs. hierarchical architecture using ONAP components.  One of the first things we did was to use the PoC Plugfest to promote the B release.
            1. LF and O-RAN Alliance will 
            2. Action/ Farheen Cefalu continue to keep the discussion open next week regarding Plugfest.
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. Release planning link.
      1. PTLs update the email list of where they are at and what progress they have made.  Create a brief summary and then we will review the mail with the working groups.
   3. There is a WG review item.  What is your expectation?  How should we facilitate that?  I was going to request the WG co chair to cross check.  Can you give us some guidance? Guidance on the review.
   4. 1. We will have time between development sprints 1 and 2 to review what sections of software.
         1. We should put together a clear list of what has been done.  Any demos of what is working and a quick discussion on what is planned for the next few releases.  Then hand off to O-RAN.
         2. Written document from each PTL to show the progress that has been made as a review checkpoint.  In future releases the demos will be a natural part of the process.
         3. Next Friday will be our bi-weekly TSC call where each WG and software community TOC should present their progress.  It's good to provide a summary of the overall progress.  Every two months is when we can report out on significant progress.  The milestones of reporting to O-RAN are tied to milestones in the software efforts.  Action/ Farheen Cefalu send a message to the PTLs to provide a one page summary of their progress.
         4. Action/ Farheen Cefalu add B release naming to the Agenda.
7. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non real time RIC (RAN Intelligent Controller) - John Keeney
      1. Ericsson has ramped up their commitments to 10 developers.  
      2. Difficult to see a clear line of working with ONAP working with O-SC.  Concerned about coordination of the 10 developers between ONAP and O-SC.  TOC set up a process for upstreaming and project alignment.  Becoming difficult to provide a clear description of work items to the developers as the PTL.
         1. 5G is popular and ONAP wants to contribute.  It drives people to participate but it does create confusion and overlap.  We need to continue to get clarification.  ONAP is not the only non-real time RIC platform that is supported.  There are options for others.  
         2. The general discussions have been around the fact that it's an upstream project that will be used in our releases.  Clarify what is the platform and what are the services that run on the platform.  Some platform evolution has to be related to 5G.  This should be a discussion on our October agenda on how we deal with our relationship on our upstream projects. 
            1. Using released versions where possible. We are going to acquire and contribute back to projects such as ONAP.  We are looking at a G release when we will be using it.  We don't want to sit idly by.  We should set up a formal way to approach.
               1. We need to keep discussing and evolving our relationship.
   2. RIC Applications - Matti Hiltunen
   3. RIC Platform - Thoralf Czichy
      1. 2019-09-04: Some legal issues currently prevent us from contributing further to some of the RIC Platform repos. Legal discussion takes time. Solution should come in anything between 1 to 4 weeks delays. This also effects some of the RIC xApps (MC and UE Manager).  Consequences are there will be delays in the original plans to the RIC platform.
         1. All contributions or certain elements of RIC Platform?
            1. Certain elements.
   4. O-RAN Centralized Unit user-a934b
   5. O-RAN Distributed Unit High Sachin Srivastava
   6. O-RAN Distributed Unity Low Zhimin Yuan
   7. O-RAN Radio Unit (TBD)
   8. Operations and Maintenance - Martin Skorupski
   9. Simulations - Alex Stancu
   10. Infrastructure - Xiaohua Zhang
       1. Talked to INSPUR according to Orange due to resource issues can not contribute to Release A.
          1. When Jack was at the LF OSS Linux Edge meetings discussed with Akraino project.  For the infrastructure project we need to put Akraino on the list of the upstream project that we want to have our relationship with.
   11. DOC - weichen ni
       1. I don't know how to test the docs structure.  I don't know how to set up the templates or the documentation structure.  How can I see if my docs works?

8. Test & Integration Planning - Lusheng

   1. Every company should have one person who participates in the test and integration planning.  Companies should designate one person / representative as a part of that team.  Action/ John Murray will try to get a representative from each PTL to provide someone to participate in the integration and test team.
9. Requirements Software Architecture Committee - Rittwik
   1. We have started the B release epics.  Encourage people to leave comments.  Reminder October meeting with the working groups.

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

    1. Action/Claudio Coletti WG3 raising a concern of prospect of  E2 release by OSC.
       1. In WG3, due to slow progress, we decided to postpone our first release of the E2 specs of the E2 interface.  Information elements being captured and information model.  Release A targets November as release date which is not aligned with O-RAN perspective in WG3. Concerned about misalignment. As a WG co-chair it is important to guarantee WG3 is captured in the E2 implementation open release.  
          1. Challenges with moving the software forward and standards because we are early in the process.  Most of what we are doing in Release A is pre-specification.  We need to find the challenges in building something new.  
             1. Perception of something that looks like E2 prior to ORAN release. 
             2. There will be something that looks like E2 before O-RAN Alliance publishes.
                1. Agree that we (TOC) should come up with terminology and activity but we should not slow down the progress.
                2. We will not slow down in activities.  Concerned about the public perception of the disconnect.
          2. We're thinking of having an O-RAN Alliance demo and not sure how to take care of this issue.  It is coming from O-RAN Alliance.
             1. I am not concerned about the demo.  I am concerned about the November release and what it will look like compared to what the E2 specs.  Will we have public MACD and pre-spec.
                1. The documentation project can make E2 pre-spec.
                2. Jack - We need clarification on terminology from O-RAN Alliance.  There will always be something that may not be conforming to spec.  We have to figure out terminology O-RAN Alliance wants us to use.  The TOC needs to take up with O-RAN Alliance leadership and come up with an agreement.
             2. Action/ Claudio Coletti raise the issue with O-RAN Alliance.  What is O-RAN supposed to do.  How it should be published.  
             3. Jun Hyuk Song we don't know about message types and what kind of information elements it carries.  It is a serious concern.  I hope WG3 can look at the pre E2 spec to give us blessing or feedback.
                
                1. Each project has its own documentation.  
                   1. They don't have documentation and that is why I am raising a concern.
                      1. RIC Platform PTL: This is effected by legal issues.  There is a document floating around with WG3 but it is not in public repos yet because of legal issues.
                      2. Communicate clearly that it is pre-specification and get it approved by legal. 
                      3. Eventually when the document is public will it contain elaborate details? Yes, we will elaborate the details
                2. We have to trust that WG3 is going to work through the issues.  For us how we set up compliance with implementation of E2 with a mappable plugin structure.
             4. KPI monitor xApp concern.  We need to know E2 subscription message.  We don't have any information on it.  We are making up our own.  We need to have a pre-spec which is the only way to minimize issues between O-SC and WG3. 
                1. Action/ Farheen Cefalu add this to our agenda but this is a part of the software architecture issue.  
                2. Action/ Jun Hyuk Song start the dialogue on the email list regarding the KPI monitoring xApp concern.  
    2. Action/ John Murray 3GPP discussion
11. Any Other Business (AOB)
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
       1. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by Jinri Huang and seconded by William DIEGO  the minutes of the August 28, 2019 meeting were the approved by the TOC members. 
          1. VOTE: Vote taken, item passed.
    2. Actions
       1. Action/ Jun Hyuk Song start the dialogue on the email list regarding the KPI monitoring xApp concern.  
       2. Action/ Claudio Coletti raise the issue of the E2 interface and WG3 schedule with the O-RAN Alliance.
       3. Action/ John Murray  continue discussion about Plugfest.
       4. Action/ John Murray talk to user-d3360 about the issues with signing of names on the CLA.
       5. Action/ John Murray will be working with Farheen Cefalu for the next weeks to coordinate the release schedule with upstream projects.
       6. Action/ Andrew Grimberg will check with the engineer of whether or not there is an automated process to auto-add the reviewers.
       7. Action/ Andrew Grimberg provide documentation and proposal.  
       8. Action/ Andrew Grimberg vet the TOC process with the TOC members.
       9. Action/ Andrew Grimberg provide clear instructions to TOC mail list on how TOC members can get a gerrit account and the process.
       10. Action/ Farheen Cefalu send a message to the PTLs to provide a one page summary of their progress in the last four weeks to the TOC mailing lists.
       11. Action/ John Murray discuss B release naming convention.
       12. Action/ John Murray 3GPP discussion