Roll Call & Quorum Check 

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.  

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
2. Vote to approve minutes for 30 Oct 2019 
3. On motion made by MASAFUMI MASUDA
4. Seconded by user-bc668
5. VOTE: Vote taken, item passed

1. Action/Jinri Huang  will create a framework for the marketing plan.
   
   1. A message from the call this Monday is this will be a joined release with the Linux Foundation.  We can have one quote from O-RAN leadership.
   2. user-59b16  send Jinri information about the overall targeted use case and functionality as targeted working material.  Announce the first release about the features we are delivering.  What is the main functionality and how we pull this together as a community as a milestone.
   3. The tone is important in the first press release.  We don't want to oversell.  We want to depict it as a milestone.  
   4. The LF leans towards talking about the current release and not the next release.  Hopefully we can pull together the voting for the B release and the time frame.  Trishan de Lanerolle volunteered to help.

1. Action/ Community Vote for a "B" Release Name deadline. 
   1. Vote to approve closing the B release name end date 08 Nov 2019 noon UTC
   2. On motion made by Thoralf Czichy
   3. Seconded by user-bc668
   4. VOTE: Vote taken, item passed
2. Action / Farheen Cefalu send out a note today of when we have to have our votes in by 08 Nov 2019 .  Update the site
3. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
   1. No updates .  We are in the process of setting up the VPN to the process.  Up and running.
   2. Tracy - Thinks the time is right to include the names of the participating written vendors.  Does anyone have an opinion or should I include their names in our documentation.
      1. How many participants?
         1. For the OSC POC there are additional vendors (open front haul) 5 committed members.  I have confirmation from Conscope Ericsson NEC and Nokia, and Samsung.  OSC O1 related use cases from slides on wiki.  Others are captured from Beijing captured on their slides.   
            1. From OSC perspective I think it is OK to put their names.  
               1. They confirmed in writing.  I will put their names.
                  1. We have to avoid words like compliance because they're participating.  
                     1. Agree this is a demo proof of concept un-certified non-compliant.
4. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
5. Action/ John Murray to work with OAI interface.
   1. EC discussed this.  Orange proposed dividing this corporation into two stages.  Short and long term targets.  First term have a joint proof of concept.  Bad news is they don't have details of code distribution tools, integration.  One of the requests from Hank is to require Orange to come up with detailed mechanics of POC.  Long term is to have a third license from OAI.  Desire is to put this under O-RAN SC so that it will encourage O-AI community to contribute to O-RAN SC.  For this long term cooperation is not very clear.  Uncertainty whether O-AI give up their work in their own community and assign their resources to O-RAN SC.  My understanding is if we want to cooperate we should concentrate on the short term solution.
      1. The question on the short term.  Were they targeting that cooperation with O-RAN Alliance test group? O-SC test?
         1. OSC.  The software development work is mainly under our community.  Their corporation will cover our software community.
            1. We need to gather people of interest to work on this.  user-59b16 set up an architecture team.  We need to sit down and see how to use it as a target to see how to make it work.  We should create a plan.  Action/ user-59b16 Alignment and adjust their code to be compliant with O-RAN Alliance.  The time frame is as part of B release what can we achieve as interoperability.  Can we id a task with some level of interoperability with OAI.  
               1. Rittwik - My expectation is E2 adaptors.  
                  1. Jack - These need to be listed out and agreed upon so everyone is on the same page.  We need a some statement out so we can 
                     1. Jinri - Maybe we should wait for Orange.  
                        1. Jack - They will need some support from us.
                           1. Jinri - OK 
      2. Details 
         1. There is a spreadsheet that ids the B Epics.  Action/user-59b16 send the epics to user-bc668 .  December 4 or 6 the TOC will take a vote to approve the spreadsheet.  We have this month to clean up all the epics and end to end use cases.
            1. Viswa - Will there be a vote for seed code in the repo?
               1. We got original seed code.  We formed the individual projects with the PTLs.  The community decided what they will pull in.  We deleted some seed code.  We left that to each of the working teams.  The epics are pre- O-RAN Allliance specification.  We are working towards.  As we bring in code compliance with spec, some code may be depricated or changed to meet the specifications.
                  1. What is there is questionable code?  Are we going to getting all the code or lifecycle only?
                     1. All the integration and test drives the package.
                        1. Lusheng's team is packaging up different projects that will be included in the release.  Though some projects have not contributed enough code for detailed functionality.
                           1. Lusheng - we are asking each repo for a binary image or LF package for this release.  For next release we will run those binary artifacts and end to end stories.
                              1. Viswa - If someone wants to check out the Amber release do they have to download from each repo?
                                 1. Yes they will have to download from each repo and we can offer the Amber branch.
                                    1. Now that we have pieces we will start to build the "B" release.  The E2E use cases will drive the build.
                                       
                                       1. If needed we can create automated script to grab the Amber release branch and put it into a big tar ball.  However for A release not everything is integrated.
                              2. Earlier we had a word document that detailed the scope of A release.  Now that we heard there is a project will there be one for B release.
                                 1. The release architecture team should pull together and close software development and write detailed release notes.  These are a part of the documenation for the release.
6. Action/ John Murray closing the remaining the TOC slots. 
   1. Jack sharing tes.lfanalytics.io/projects/o-ran.
      1. We are not releasing it yet because the data that is presented is not accurate. This is progress.  When clicked on we get metrics.  The site is not fully released yet.  We are continuing to work it.  Trishan de Lanerolle  there needs to be an overview.  I wanted to show the progress.  Lusheng is working with them on the first level.  Getting the public release of metrics is important to show because we want to fill in the TOC slots.
7. Action/ user-d3360 add the link of the Jenkins instructions from the the Jenkins status page to the top of the Project Readiness for Amber Release wiki page.
   1. Chris Lott has written a very good page and I still have to create a link to it.  
8. Action/ weichen ni  will provide PTLs with the steps that they need to view their converted docs on the documentation wiki.  He will add the link to the top of the Project Readiness for Amber Release .
9. Action/ Each PTL write up a small clear statement about their license attribution that they can post to the email list. 
   1. This is from the license scan that the LF provided.  There is code with DSD or MIT licenses.  
   2. These licenses can be used in upstream projects. 
   3. BSD-3-Clause need to be clearly marked of which directory from the external source.  This was the assignment for PTLs to provide so TOC can approve.  

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Lusheng demonstrated the spreadsheet with the copyright and copyleft items.
   2. Project Readiness for Amber Release
   3. Do we allow an extension to the code freeze?
      1. At this point they should put the code in and it will be a part of the maintenance release if we choose to have one.  At this point freeze the code and document.  That repo won't be a part of this release.  It will be a part of maintenance release if they are green.
   4. Action/ PTLs update Project Readiness for Amber Release red rows as soon as possible.  We want to move ahead.
   5. Regarding support contact user-d3360 or Chris Lott for CICD.
   6. Action/ PTLs must update their release notes in their documentation by 13 Nov 2019 .  We will review the red rows on Project Readiness for Amber Release.  If you haven't completed give us a percentage complete.  We need a good faith demonstration.
   7. As we are preparing for releasing docker images to docker hub prefix the organization with the docker name.  TOC Co chairs have been asked for how to name this.  ORAN is NYSE for Orange.  Use o-ran.  Jack - We should use o-ran-sc or scp.  This makes it clear which license gets what.  They both begin with O-RAN.
      1. Concern about confusion around sc and scp.  I would call it o-ran-sc. Once in binary the licensing is not important.
      2. Action / TOC We need to confirm this by 13 Nov 2019 .  
2. user-d3360 Test & Integration Planning (INT)
3. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Matti Hiltunen RIC Applications (RICAPP) 
   2. Thoralf Czichy RIC Platform (RIC)
      
      1. request to approve one new repo and committer changes for two existing repos as per this e-mail
   3. user-a934b O-RAN Centralized Unit (OCU)
   4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
   5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
   6. Martin Skorupski Operations and Maintenance (OAM)
   7. Alex Stancu Simulations (SIM)
   8. Xiaohua Zhang Infrastructure (INF)
   9. weichen niDocumentation (DOC)
   10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
   11. (TBD) O-RAN Radio Unit (ORU)
4. user-59b16 Requirements Software Architecture Committee

1. Lusheng - email request for release status review.

1. Sonia Sangari  needs access to build Jenkins jobs.   Sonia Sangari  send user-d3360  a request for Jenkins jobs access.

1. Votes
   1. Vote to approve minutes for 30 Oct 2019 
      1. On motion made by MASAFUMI MASUDA
      2. Seconded by user-bc668
      3. VOTE: Vote taken, item passed
   2. Vote to approve closing the B release name end date 08 Nov 2019 noon UTC
      1. On motion made by Thoralf Czichy
      2. Seconded by user-bc668
      3. VOTE: Vote taken, item passed
2. Actions
   1. Action/Jinri Huang  will create a framework for the O-RAN SC marketing plan.
   2. Action / Farheen Cefalu send out a note today of when we have to have our votes in by 08 Nov 2019 .  Update the site
   3. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
   4. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
   5. Action/ John Murray to work with OAI interface.
   6. Action/ user-59b16 Alignment and adjust their code to be compliant with O-RAN Alliance.
   7. Action/user-59b16 send the B release epics to user-bc668
   8. Action/ John Murray closing the remaining the TOC slots.
   9. Action/ user-d3360 add the link of the Jenkins instructions from the the Jenkins status page to the top of the Project Readiness for Amber Release wiki page. 
   10. Action/ PTLs must update their release notes in their documentation by 13 Nov 2019 .
   11. Action/ TOC Docker hub prefix naming vote due 13 Nov 2019 .  Suggestion was made to call the prefix o-ran-sc

Roll Call & Quorum Check 

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.  

• The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
• Vote to approve minutes for 16 Oct 2019 
• On motion made by user-2057e
• Seconded by MASAFUMI MASUDA
• VOTE: Vote taken, item passed

1. Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
   1. Tracy reviewed with several working groups last week.  I am uploading the current slides and a welcome package.  Demo video will record the live demo and read out in zoom and post that in the O-RAN Alliance wiki and the O-RAN-SC wiki.  Unless there are other suggestions for the video?
      1. Good idea we need to figure out how we'll organize our information about our releases from that demo and marketing stand point.
      2. Action Farheen Cefalu Add to the marketing of the Amber release to TOC agenda.  We need to work on a package with WG and LF on what PR we are going to put out.
      3. Call to action for TOC members to lead the Amber release marketing and PR strategy for the Amber release.
      4. Tracy - Talk to Jack offline for the expectations on the vendors.  They are asking questions about PR.  
      5. Action/ Tracy Van Brakle will send out an email to TOC mail list.  We are not going to keep score or pass fail.
      6. Trishan de Lanerolle  support Tracy Van Brakle with PR.
2. Jinri Huang will upload presentations and minutes under Events page on the wiki of the face to face meeting. 
   1. user-59b16  reach out to Jinri Huang for slides.
      1. Make sure there is nothing in the documents that O-RAN is not ready to release publicly.
      2. Executive Committee slides can go up?
         1. Let's get a list of what we can put up.  There is a difference between the TOC meetings and the O-RAN Alliance meetings.  We can point to the O-RAN Alliance wiki or else we need permission to share their slides on O-RAN-SC.
         2. Action/ Farheen Cefalu remind Jack about how we want to arrange the events page with O-RAN Alliance slides.
3. user-d3360 send Jinri Huang the count of committers in gerret.
   1. Amber metrics need to be gathered.  How many committers?
      1. Action/ Trishan de Lanerolle provide a report to John Murray of the analytics around contributions of the Amber release.
   2. LF has a new analytics platform based on code contributions in a project.  
      1. When will the reports be available?
      2. Action/ Farheen Cefalu  add an agenda item for project metrics.

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. We have 2 weeks and then we will have our updated code freeze.
   2. We will freeze code November 2 and then a few weeks of defect fixing, then freeze and branch the code.  We will document the code during the code freeze and then have our release.  Once we branch the code we will return to a maintenance cycle in January.  The maintenance release will run through Feb 1.  This is projected for B.  We have not finalized the B plan.  Dec. 2 we will start Epic identification.  RSAC will come with their use cases and details.  We take off from December 21st to January 6th.  If changes need to be made make them now.  They need to be finalized in the next few weeks.
2. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Action/ Jack will move the order of the agenda by moving Test to the top during the release process. 
   2. Matti Hiltunen RIC Applications (RICAPP) 
   3. Thoralf Czichy RIC Platform (RIC)

      1. Below a list of changes to repos (new ones, as well as deletions) under the RICP (near-RT RIC Platform) that we would like the TOC to approve. Parts marked with RICP/RICAPP are proposed by Matti and I (PTLs for RICAPP and RICP) and parts marked with RICP only  me as PTL.

         (WE1) Project RICP
           ric-plt/resource-status-manager
               - Summary: Implements the management of Resource Status messages over E2
               - Description: The Resource Status Manager is responsible to control the generation of
                   Resource Status messages sent by the RAN to the RIC by issuing Resource Status Requests.
                   The RSM provides an API that allows to start and stop the generation of these messages as
                   well as to issue specific request commands. The RSM provides also default values which are used
                   whenever a new RAN (eNB) is added to the RIC.
               - License: Apache 2
               - Initial committers: (all AT&T) Shuky Har-Noy  ( shuky.har-noy@intl.att.com),  Hila Anina ( hanina@intl.att.com), Yaki Ratz ( yaki.ratz@intl.att.com )

         (WE2) Project RICP/RICAPP
           We (RICP and RICAPP PTL) would like to remove the following repositories:
              ric-app/demo    (empty)
              ric-app/reporter (not maintained anymore for 6 months (and actually confusing community if someone uses this as reference) and e.g. the measurement campaign xApp can replace it)
              com/asn1         (an ASN.1 compiler for which we found that it causes to much issues that we had to troubleshoot. We already switched to using com/asn1c (which is derived from https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_vlm_asn1c&d=DwIFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Tnwenk7t78Qk7cMlMZ90EGmbng6eVuV4yQNhqbtpKkk&m=xoq2zMpPhab9uHOEBVXWXAFXjPsyFpAgdbNtyADOnwY&s=Rkl10dXpdSlyLJTKlTd3zwy98meppgWMQ_0PNWZ8QjQ&e=)

         (WE3) Project RICP
            new repo: ric-plt/ric-test
               - Summary: RIC platform-specific testing that are not specific to a single RIC component
               - Description: This repo includes test cases that span the full RIC platform, i.e., that cannot run against a single RIC component. This may also include
                   simulators related to the E2 base protocol, or related abstract test xApps (that do not actually implement 3GPP specifications). Note that the test
                   cases must still be limited to RIC platform only. If you want to write/check test cases that integrate also other O-RAN SC components, check
                   the it/test repository.
               - License: Apache 2
               - Initial committers: (first one AT&T, the other two from Nokia): Xuan Tuyen Tran (Harry) (tuyen@research.att.com ), Amit Uttam  ( amit.uttam@nokia.com )  and Shashikumar HN ( shashikumar.hn@nokia.com )

         (WE4) Project RICP
            new repo: ric-plt/ric-dep
               - Summary: Code and configuration files that are needed for deploying a near-RT RIC platform instance
               - Description: This includes, for example, helm charts for RIC platform components. In this we can make assumptions about the underlying k8s already existing or
                              we can also spin up blueprints for such a deployment. Note that this component is intentionally limiting itself to the RIC platform and does
                              not include other O-RAN SC components. For such you might want to look at the it/dep repo managed by another O-RAN SC project.
               - License: Apache 2
               - Initial committers: (first one AT&T, the other two from Nokia): Lusheng Ji (lji@research.att.com) , Prabhu K ( prabhu.k@nokia.com )  Ranjit  Angajala   ( ranjit.angajala@nokia.com )

           Note that this needed for legal reasons to clearly define the scope of the near-RT RIC project. It is aligned with a "scope" wiki text that we wrote for the same reason.
           Also note that we continue with the it/dep repo as a general integration repo where any O-RAN SC components can be integrated together. In scope of their work on
           integrating all O-RAN SC components, engineers working on the it/dep repo might re-use some of the functionality that was original committed to ric-plt/ric-dep .

         (WE5) Project RICP/RICAPP
           We would like to remove the empty ric-app/uemgr and instead create a new repo under ric-plt/. This is in order to clearly link
           the demo xApp to the RIC platform project. At the same time also note that the license of this is changed to a documentation
           license. So that its legal scope reflects its actual role in the RIC platform. Naturally there will continue to be actual xApps under the
           RICAPP project. Placing it under the RICP project (and not RICAPP) allows Nokia to contribute to it. The name is intentionally kept
           generic. As part of this change we also move this page https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.o-2Dran-2Dsc.org_display_RICA_UE-2BManager-2BxApp&d=DwIFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=Tnwenk7t78Qk7cMlMZ90EGmbng6eVuV4yQNhqbtpKkk&m=xoq2zMpPhab9uHOEBVXWXAFXjPsyFpAgdbNtyADOnwY&s=gaI_Yvwbqi4X3KKgd2KlO1cau-oPGsKTpA0lo3SzHeo&e= to the RICP project (a reference
           in RICA continues to refer to it.
           deleted repo: ric-app/uemgr
           new repo: ric-plt/demo1
               - Summary: A simple demo xApp running on the RIC platform.
               - Description: Contains a simple demo xApp running on the RIC platform.
               - License: Creative Commons Attribution 4.0 International License
               - Initial committers: (all Nokia) Timo Tietavainen ( timo.tietavainen@nokia.com ), Jussi Maki Aijala (jussi.maki-aijala@nokia.com), Juha Hyttinen (juha.hyttinen@nokia.com) , Anssi Mannila  ( anssi.mannila@nokia.com)

         (WE6) ) Project RICP
           We delete the following repo: ric-plt/ue-nib . The scope of the RIC platform does not include this functionality. If, then
           such functionality should be developed outside of the RIC platform, e.g., under the RICAPP project. Some of the earlier functionality (read and write
           of the demo data that is actually needed in the "demo1" demo xapp (under documentation license) is moved into the demo1 repo as it is
           closely related and does not make too much sense as standalone documentation repo. Note that this implies that the functionality is now under
           document license in ric-plt/demo1

         1. Empty repos are allowed to be deleted.  Repos with content are open source and remain for historical reasons.
            1. Needs to be marked as depricated.  When we complete the Amber release there should not be code dependencies.  Therefore we can remove the repos because this is the first A release.  
         2. The RIC platform as an entity must be open source contained platform.  When you cross over to system integration is work in a different project that will rely on the RIC project but other people on different licenses won't be able to participate.  
            1. E2 was removed due to legal issues.
            2. RIC PLT E2 had files ASN1 files that were not supposed to be there.  That compiler was used in early development but won't be used again.
         3. Concern about putting this in documentation license downstream and someone contributes back to a test repo then it becomes a part of the test by the integration team.
            1. That is acceptable.  
      2. Proposal to make changes to the RIC Platform repos above
      3. On motion made by Thoralf Czichy
      4. Seconded by MASAFUMI MASUDA
      5. VOTE: Vote taken, item passed
   4. user-a934b O-RAN Centralized Unit (OCU)
   5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
   6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
   7. Martin Skorupski Operations and Maintenance (OAM)
   8. Alex Stancu Simulations (SIM)

   9. Xiaohua Zhang Infrastructure (INF)

      1. During f2f repos were summarized.  3 repos were supposed to be contributed by inspur.  I double checked and they are not using those repos anymore.  They will not be making future contributions.
         1. These are seed code repos that were not a part of the Amber release.  We need to go ahead and clean up and remove those seed repos.  No vote needed.  This is normal clean up.  
         2. Action/ Xiaohua Zhang raise a ticket with LF to remove the seed code projects.
   10. weichen ni Documentation (DOC)
   11. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
   12. (TBD) O-RAN Radio Unit (ORU)

3. user-d3360 Test & Integration Planning (INT)

   1. Call to all PTLs to give a status report for release preparation.  Action/ user-d3360 post the request through mail list.
   2. Next TOC will occur after daylight savings time.  Not all communities will recognize that shift and that will move this meeting minus 1 hour.
4. user-59b16 Requirements Software Architecture Committee
   1. Discussed traffic churn use case with different values.  We should prepare for that.  We are going to look at our spreadsheet of epics consolidate and move on to call flows.  It's in a word document with some call flows.  I am hoping that Thoralf Czichy and Matti Hiltunen will discover algos that will work with xApps.  Talked to Samsung about CU DU binary code for an example.  Jin Sun said their management will look into it.  Radisys agreed to provide a CU DU binary.
      1. As part of the release planning when we get into the B release we identify the epics.  Yes there is an approval.  This is the version of our requirements and use cases as part of the B release.  That package should be brought to the TOC for a vote to freeze the target environments.  
         1. When does that happen?
            1. December 7th once the epics are identified we should freeze it so the projects can commit to B release.  This gives the development team to groom their user stories.
      2. How many end to end use cases?
         1. One
      3. Jack would like to see a simpler e2e  base line "hello world" use case that demonstrates that the platform is working.  It is a simple metrics use case that can exercise the components and return metrics on the different components running in place.  We need a use case that we maintain for the basic level of operation before talking about complex.  We want a base line use case that exercises the system and gathers metrics.  A heartbeat check.  This way everyone is at a base point before advancing their use case.  There should be a self diagnostic test so the platform is base lined.
      4. user-59b16 post the presentation.

1. Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
2. Thoralf Czichy  Near-RealTime RIC platform repos that are required.

1. Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
2. Jack will be adding more items to next weeks agenda.

1. Votes
   • The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
     • Vote to approve minutes for 16 Oct 2019 
     • On motion made by user-2057e
     • Seconded by MASAFUMI MASUDA
     • VOTE: Vote taken, item passed
   • Proposal to make changes to the RIC Platform repos above or Thoralf's request through lists.o-ran-sc.org
     • On motion made by Thoralf Czichy
     • Seconded by MASAFUMI MASUDA
     • VOTE: Vote taken, item passed
2. Actions 
   • Farheen Cefalu Add to the marketing of the Amber release to TOC agenda.
   • Call to action for TOC members to lead the Amber release marketing and PR strategy for the Amber release.
   • Trishan de Lanerolle  support Tracy Van Brakle with PR.
   • user-59b16  will reach out to Jinri Huang for F2F slides to put in the Events wiki.
   • Action/ Farheen Cefalu remind Jack about how we want to arrange the events page with O-RAN Alliance slides.
   • Action/ Trishan de Lanerolle provide a report to John Murray of the analytics around contributions to the Amber release. How many committers?
   • Action/ Farheen Cefalu  add an agenda item for project metrics.
   • Call to all PTLs to give a status report for release preparation.  Action/ user-d3360 post the request through mail list.
   • user-59b16 post the churn use case presentation on RSAC.
   • Action/ Farheen Cefalu  add Summarize F2F meeting at O-RAN Alliance event to next weeks agenda.
   • Action/ Farheen Cefalu move the order of the agenda by moving Test to the top during the release process. 

Roll Call & Quorum Check 

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.  

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 25 Sep 2019 
   2. On motion made by William Diego
   3. Seconded by Masafumi Masuda
      VOTE: Vote taken, item passed

1. Items added to section 10 New Agenda new Business below.

1. Actions: Plugfest 
   1. Tracy Van Brakle to provide writeup next week as base for blog, etc.
   2. Farheen Cefalu add to the wiki events page. 
      1. Jinri received a call for participation.  Farheen Cefalu follow up with Tracy and Jinri.
   3. Jinri Huang to talk to CMCC how to promote at Beijing plugfest.
      1. Jinri will report back 09 Oct 2019 .
         1. Two parallel sessions in Beijeng and USA.  Jinri wants to promote TOC in both events.
2. Action/ user-2057e start a poll for B release.
3. Action/ user-59b16 publish the meeting details on the RSAC page regarding WG3 and E2.
   1. Last week Rittwik organized the meeting to align the O-RAN working groups.  Jinri attended.  There was another alignment meeting with software working group and O-RAN Alliance.
4. 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
      1. Conclusion is we are not using SPDX.
5. Action/ user-d3360 talk to Jack about which use cases are being covered by the test and integration team, for release B.
6. Action / Tracy Van Brakle TOC will look to Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. RSAC meeting Rittwik mentioned most development work in RSAC is ongoing.  Our target is to have our release at the end of November.  Initial idea to reconsider the timeline.  Rittwik and Jack are not here.  Call for opinions.
      1. Matti - Code freeze is Monday this week.  We are not supposed to add anything.  Proposal by Rittwik to extend the release by three weeks (1 full sprint).  Code freeze was September 30 extend it for three weeks.  Team needs more development time.
         1. Who should we request an extension from?
            1. Release Manager
            2. Voting approval by TOC and TSC.
            3. Action/ user-59b16 place a formal approval request for code freeze extension.
         2. LF projects release has a special meaning.
            1. Code hosted by LF gerrit, nexus, etc.
            2. To release code must be published to other global repos.  Gerrit goes to github.  Docker images go to Dockerhub.  To publish means to publish to these global repositories.  Meaning we should have some standards.
               1. Do we have any standards for release?  
                  1. LF has different criteria for different releases.
                  2. Licenses have to have standards.
                  3. As far as software quality is the TOC/TSC decision.
   2. Jun Song - wants to raise an issue.  RSAC meeting I raised two issues for KPI XApp.  We don't know how to verify and test the xApp once we complete the coding.  
      1. Matti - from integration point of view what are the requirements his KPI xApp has to meet?  It will talk to simulator via E2 termination.  Other xApps are tested with a simple simulator without E2.  Action/ Matti Hiltunen document the simulator test on the RSAC space in the wiki.  We don't have anything else for the Amber release besides the simulator to test xApps.
      2. Lusheng - I would like to see one xApp for a complete integration.  I would like to see it following the overall flow and architecture.  We can enhance a component for the Amber release.  It can be deployed so the APIs provided by the near real time platform would be a big achievement.
         1. As long as you can deploy the xApp would be a minimum viable product.
            1. Martin agrees.  We need to have the basic building blocks complete.
   3. Jinri - We need Rittwik to vote on extending the timeline.
2. Release planning link.
3. Copyright
   1. Which projects have the copyright issue?
      1. CU, DU, RIC Applications.
   2. There was a form from O-RAN Alliance regarding the copyright issue.  
      1. We should let Jack address.  He wants to test one or two components.  Jinri will review with Jack.

1. Non real time RIC (RAN Intelligent Controller) - John Keeney
2. RIC Applications - Matti Hiltunen
3. RIC Platform - Thoralf Czichy

   1. Outstanding Resource Requests for Linux Foundation

      1. https://lists.o-ran-sc.org/g/toc/topic/new_repo_requests_ricp/34367904?p=,,,100,0,0,0::recentpostdate%2Fsticky,,,100,2,0,34367904 

         1. hi,

            I hereby request two new repos managed by the RICP (near-RT RIC platform) project.

            ric-plt/asn1-documents

                  - Summary: ASN.1 definitions and related documents

                  - Description: ASN.1 definitions and related documents that are needed by other components in compilation. E.g., this includes E2 ASN.1 definitions.

                  - License: Creative Commons Attribution 4.0 International License (unless document comes from somewhere else)

                  - Initial committers: Thoralf Czichy (thoralf.czichy@...), Alistair Urie (alistair.urie@...), Paul Stephens (paul.stephens@...), Antti Puhakka ( antti.puhakka@... )

            ric-plt/streaming-protobufs

                  - Summary: protobuf definitions used when streaming messages to other xApps

                  - Description: contains protobuf definitions that xApps can use, for example, to derive statistics from streams of messages obtained from the RAN.  

                  - License: Creative Commons Attribution 4.0 International License

                  - Initial committers: Timo Tietavainen (timo.tietavainen@... ), Jussi Maki Aijala (jussi.maki-aijala@...), Rolf Badorek (rolf.badorek@...)

            All committers are already committers in other repos of the RIC platform. Additionally we have Alistair and Paul working in WG3 of

            the O-RAN alliance and myself as RIC PTL.

            Thoralf

   2. Vote to approve two new repos managed by the RICP (near-RT RIC platform) project 

      1. ric-plt/asn1-documents will be in word or pdf which are not reviewable by git gerrit.  License will be the common.

         1. Committers: Thoralf Czichy, Allistair Urie, Paul Stephens, Antti Puhakka.

      2. Protobuf definitions ric-plt/streaming-protobufs.  They are an interface.  No code link or creative logic.  3 Nokia Committers. See Thoralf Czichy  message on lists.o-ran-sc.org TOC.
         1. Committers: Thoralf Czichy, Jussi Maki Aijala, Rolf Badorek.

1. 1. 1. On motion made by William Diego
      2. Seconded by Masafumi Masuda
         VOTE: Vote taken, item passed
2. O-RAN Centralized Unit user-a934b
3. O-RAN Distributed Unit High Sachin Srivastava
4. O-RAN Distributed Unity Low Zhimin Yuan
5. O-RAN Radio Unit (TBD)
6. Operations and Maintenance - Martin Skorupski
7. Simulations - Alex Stancu
8. Infrastructure - Xiaohua Zhang
9. DOC - weichen ni
10. O-CU user-a934b 

Test & Integration Planning - Lusheng

New Agenda Items (New Business)

1. Approval from Thoralf Czichy for Near Real time RIC
2. Face to face meeting discussion regarding agenda Jinri Huang
   1. Who will be at F2F? Jinri Huang , MASAFUMI MASUDA, William DIEGO user-a934b.  Rittwik will be there.  Thoralf and Matti will work with Rittwik for the RIC presentation.
   2. October 14 - 16 we are in the afternoon session from 4:30 - 7:00PM.  There are four purposes for the meeting.
      1. consolidate our alignment with WG.
      2. Discuss release B planning
      3. Copyright issue discussion
      4. Discuss the respective projects but since low attendance of PTLs we may reconsider.
      5. To make the communication for WG better there is a slide.  Check with other working groups and prepare similar slides.  Let us call them Alignment Analysis.  I can see a list of items divided into three groups with three marks.  
         1. "Aligned" mark: items developed based on released spec. or what have been agreed in the WG.
         2. "pre-spec" mark: items being specified, or to be specified in the future in WG.
         3. "TBD" mark; 
            1. Do the items go beyond the interface protocols A1, O1?
               1. Definitely interface and maybe messages.  This is generic.
                  1. Should the PTLs or WGs come with the list of items?
      6. Last remarks: Go to WG3 wiki and check out their alignment document as an example.
      7. Reviewed draft agenda
         1. Day 1: Alignment - Needs TOC support to convince TSC about WGs alignment.
         2. Day 2: Allocate 2 hours for Release B.
         3. Day 3: Copyright issues.
3. There is a motion in working group 1 to rename the non real time RIC.  Mentioned to Jack.  We have until the Costa Rica F2F meeting to decide if the OSC has a meeting on this.  Action/ Farheen add to next weeks call.
4. Action/ Farheen add discuss the relationship with the upstream projects to next weeks agenda.  John Keeney is looking for guidance for upstream and downstream projects such as Acumos and Akraino.

1. Votes:
   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for 25 Sep 2019 
         1. On motion made by William Diego
         2. Seconded by Masafumi Masuda
            1. VOTE: Vote taken, item passed
   2. Vote to approve two new repos managed by the RICP (near-RT RIC platform) project
      1. ric-plt/asn1-documents will be in word or pdf which are not reviewable by git gerrit.  License will be the common.
         1. Committers: Thoralf Czichy, Allistair Urie, Paul Stephens, Antti Puhakka.
      2. Protobuf definitions ric-plt/streaming-protobufs.  They are an interface.  No code link or creative logic.  3 Nokia Committers. See Thoralf Czichy  message on lists.o-ran-sc.org TOC.
         1. Committers: Thoralf Czichy, Jussi Maki Aijala, Rolf Badorek.
            1. On motion made by William Diego
            2. Seconded by Masafumi Masuda
               VOTE: Vote taken, item passed
2. Actions
   1. Plugfest Actions
      1. Tracy Van Brakle to provide writeup next week as base for blog, etc.
      2. Farheen Cefalu add to the wiki events page. 
      3. Jinri received a call for participation.  Farheen Cefalu follow up with Tracy and Jinri.
      4. Jinri Huang to talk to CMCC how to promote at Beijing plugfest.  Jinri will report back 09 Oct 2019 .
         1. Two parallel sessions in Beijeng and USA.  Jinri wants to promote TOC in both events.
      5. Action/ user-2057e start a poll for B release.
      6. Action/ user-59b16 publish the meeting details on the RSAC page regarding WG3 and E2.
      7. Action/ John Keeney discuss renaming of near real time RIC.
      8. Action/ John Keeney discuss the relationship with the upstream projects such as Acumos and Akraino.
      9. Action/ Jinri Huang discuss PTLs slide preparation for the F2F meeting.

Roll Call & Quorum Check 

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.  

• The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
• Vote to approve minutes for 09 Oct 2019 
• On motion made by Jinri Huang
• Seconded by user-bc668
• VOTE: Vote taken, item passed

•  Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
  • Where are the presentations from the face to face meeting.
    • Create a file list under the Events page in the wiki.
  • Face to face meeting discussions and meetings notes or recordings.
    • Action/ Jinri Huang will upload presentation and minutes under Events page. 
•  Jinri Huang  expand on the events page with anything that is relevant to the Plugfest.
•  Matti Hiltunen document the simulator test on the RSAC space in the wiki. 
  • The need for the simulator and what function it has at this time.
  • The testing should be in the simulator or the xApp or the integration and test spaces.
  • The ask was to have the simulator for hand sets so the they could drive use cases.
  • The RSAC needs a proposal for a use case.
•  user-d3360 talk to Jack about which use cases are being covered by the test and integration team, for release B.
  • Open source community will focus on demonstrating the advancement of the contributions while the use cases can drive the future activities.
  • Chance to contribute an end to end use case.
  • Action/ TOC provide user-59b16 with end to end use cases in the RSAC Committee.
    • The work begins to have the system engineering done.
    • We will discuss and document a detailed use case in this mornings working group.
    • Radisys will hinge on the DU project.
      • If a black box version of their DU can be provided.
        • Ganesh - Rittwik's proposal is regarding black box/ binary contribution.
        • It is an open call.  If Samsung wants to provide the interface from CU DU it does not have to be open source until future releases.
•  John Keeney discuss renaming of non-RT RIC.
  • We concluded last week that we don't want to re-name the non-RT RIC
•  John Keeney  provide alignment slide for f2f meeting to Jinri Huang
•  Action/TOC continue review the Nokia proposal for the near-RT RIC and return with feedback.
•  Action/TOC approve committers for user-a934b
•  user-bc668 approve O-CU committers.

1. Release Manager/Release Planning: Weekly TOC Scheduling
2. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Matti Hiltunen RIC Applications (RICAPP) 
      1. Matti Hiltunen I request a repo that will be managed by the RICAPP project (for now):

      2. com/asn-to-json-converter

         • Summary: A streaming application that receives ASN.1 messages via Kafka and publishes them as JSON via Kafka
         • Description: The ASN1 to JSON converter is a Kafka Streamer application that received from the E2Terminator messages with ASN1 Binary payload    (PER) that is encoded in Base64 and convert it to textual JSON that can be consumed by other applications. The converter receives the packed messages on an input Kafka Topic and publishes the input on dedicated output topics. Aligned with O1 tracing. Can be used for traces from any component that uses ASN.1 message format.
         • License: Apache 2
         • Initial committers: Shuky Har-Noy  (shuky.har-noy@intl.att.com),  Hila Anina (hanina@intl.att.com), Yaki Ratz (yaki.ratz@intl.att.com) 
      3. Create com/asn-to-json-converter repo
         • On motion made by Matti Hiltunen
         • Seconded by Jinri Huang
         • VOTE: Vote taken, item passed
   2. Thoralf Czichy RIC Platform (RIC)
   3. user-a934b O-RAN Centralized Unit (OCU)
   4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
   5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
   6. Martin Skorupski Operations and Maintenance (OAM)
   7. Alex Stancu Simulations (SIM)

   8. Xiaohua Zhang Infrastructure (INF)

   9. weichen ni Documentation (DOC)
   10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
   11. (TBD) O-RAN Radio Unit (ORU)

3. user-d3360 Test & Integration Planning (INT)

   1. Request for adding committers for the integration and test open frame work.

   2. Dear O-RAN SC ToC,

      We would like to request the addition of two more committers to the it/otf Gerrit repository to help completing the Amber release target.:

      ORDWAY, ADAM G <ao8347@att.com>, LFID ao8347;

      MEILINGER, JUSTIN <jx088j@att.com>, LFID jx088j.

       
      • Request the addition of two more committers ORDWAY, ADAM G <ao8347@att.com>, LFID ao8347 and MEILINGER, JUSTIN <jx088j@att.com>, LFID jx088j to the it/otf Gerrit repository to help completing the Amber release target.
      • On motion made by user-d3360
      • Seconded by Jinri Huang
      • VOTE: Vote taken, item passed
        • Action/ user-d3360 send Jinri Huang the count of committers.
   3. In the building how much code is residing?
      1. Source code repo is a recipe.  The source code is not imported into the repo.  It is the recipe that puts it there.
      2. During build time the upstream.
         1. Is the resulting build unique to our project so O-RAN SC will use that work.
            1. Yes, it is optimized kernel and the packages.
               1. Be careful in impacting all of our other resources and projects.
               2. How often do you need to rebuild this?
                  1. No, we want to build once per release or patch releases.  Maybe one or two times per release should be good.
                  2. Concerns about managing the resource consuming job.  Work with Lusheng to schedule time early in the process so we can be efficient in the resources across projects and not block others.
   4. Lusheng - tonight will provide the full report at the f2f.
4. user-59b16 Requirements Software Architecture Committee

• Jun Hyuk Song binary seed code submission.
  • We thought seed code is possible through open source.  Binary is not an option on the table.  We are reluctant to open our code to binary code.  We learned binary code is being submitted by another vendor.
    • Jack - This is a rich topic for discussion.  In open source the code is open and people can look and contribute.  We've had discussions with companies about including the binary code as an option.  Binary code is not a contribution to the open source community.  However binary code can be used for integration and test.  For example Intel wanted to keep their layer 1 software.  They didn't have to contribute that software.  Instead they are contributing a loader module that will pull in their binary from their location.  The process to get their code is consistent.  The open source community doesn't treat it as open source but instead uses it for test and integration.  In this case the O-DU could choose to license from Intel and build it into their process.  Intel would contribute the loader.  The binary itself is not open source.  The company would have to deal with Intel directly for their binary.  They are not open source but are build, test, and integration options.  The build APIs are open source.
    • Jinri - Do we need to discuss this with the O-RAN legal team?
      • The broader issue for us is that it is hosted by the Linux Foundation.  These contributions aren't in source code.  Theoretically, if you could contribute binary it would have to under one of our two licenses meaning people could use it.  That is not their intent.  It is best for them to keep their code under their management.  If we use it for integration and test then O-RAN would have to set up how to make it available for us to use.
  • Jun Hyuk Song  TOC membership.  There are open vacancies for the TOC membership.  
    
    • Jack - We want to promote open source developers.  Interest in a viable candidate to contribute open source code.
  • Jun Hyuk Song What about xApps?  Are there requirements for that?
    • Jack- We didn't put a hard requirement on contributing magnitude of code.  Demonstrate your interest in the activity and the community.
• F2F Summary
• Samsung - contributions in the form of binary code.

1. Votes
   • The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
     • Vote to approve minutes for 09 Oct 2019 
     • On motion made by Jinri Huang
     • Seconded by user-bc668
     • VOTE: Vote taken, item passed
   • Create com/asn-to-json-converter repo
     • On motion made by Matti Hiltunen
     • Seconded by Jinri Huang
     • VOTE: Vote taken, item passed
   • Request the addition of two more committers ORDWAY, ADAM G <ao8347@att.com>, LFID ao8347 and MEILINGER, JUSTIN <jx088j@att.com>, LFID jx088j to the it/otf Gerrit repository to help completing the Amber release target.
     • On motion made by user-d3360
     • Seconded by Jinri Huang
     • VOTE: Vote taken, item passed
2. Actions
   • Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
   • Jinri Huang will upload presentations and minutes under Events page on the wiki of the face to face meeting. 
   • user-d3360 send Jinri Huang the count of committers in gerret.

Roll Call & Quorum Check 

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.  

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 02 Oct 2019 
   2. On motion made by Jinri Huang
   3. Seconded by user-2057e
      VOTE: Vote taken, item passed

•  Tracy Van Brakle to provide writeup next week as base for Plugfest blog, etc.
•  Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
  • There will be a demo next week.  Not tested yet.
  • Call to all O-RAN Alliance working group members to propose more demonstrations for the plugfest on this call.
•  Farheen Cefalu add to the wiki events page. Follow up with Tracy and Jinri. (Plugfest).
•  Jinri Huang  expand on the events page with anything that is relevant to the Plugfest.
•  Jinri Huang to talk to CMCC how to promote at Beijing plugfest.  Jinri will report back 09 Oct 2019 
  • 2 sessions.  1 in Beijing (China Mobile).  Jinri will use Martin and Tracy's demo video for the Beijing session.  
•  user-2057e start a poll for B release. 
•  Matti Hiltunen document the simulator test on the RSAC space in the wiki. 
•  user-59b16 place a formal approval request for code freeze extension.
  • Extend the code freeze to October 18 or October 25.  
•  user-59b16 publish the meeting details on the RSAC page regarding WG3 and E2.
  • We had two meetings today to align all the WGs and projects.  ODU and Infra still have to update but we are in good shape for the f2f.
•  user-d3360 talk to Jack about which use cases are being covered by the test and integration team, for release B.
  • Trying to get people from other projects and companies more involved because it requires a lot of activities that need to test their items. Code testing and end to end use cases drive the OSC solutions that we promote work.  The integration and test team will be driven by the end to end use cases that we pick as a community for our release.  This is important for the discussion next week.  RSAC have a clear managable set of use cases that demonstrate the value and capability of where we are in the O-RAN stack to the community and beyond.  You can only have a certain amount of end to end use cases.  The team has to focus on these use cases as a primary goal.  End to end use cases are the primary driver to demonstrate what the release can be used for.
    • Rittwik - If you want a full stack ete demo it will require CUs and DUs who won't be ready until the B release.
      • The goal is trying to demonstrate functionality towards the goal.  Simulators can be used.  We have to show the community is advancing in it's goals.  The spirit of end to end is talking about broader functionality and not just the individual.  Write an end to end use case around Martin's demo.  Integration and Test team should develop a plan to evaluate an end to end use case.
•  John Keeney discuss renaming of near non real time RIC.
  • People are complaining about which is the real name of RIC?  People don't like typing the extra words "near real time..." or "non real time ..."
    • Jinri spoke to O-RAN TSC.  There are difference of opinions in WG1.  Keep it open until later.
      • Martin - Do you have a proposal because it has implications to O-RAN Alliance.
        • John - I propose that we don't change it.
          • Jack - Better to change it now rather than later.  It will become harder to make the changes across documenation and it will have a ripple effect throughout the projects.
•  John Keeney discuss the relationship with the upstream projects such as Acumos and Akraino.
  • Asking for feedback on relationships with upstreams projects.  Do other people have other discussions?
    • Yes lots of discussions in the background.  See new Partnerships link in the top navigation bar.  We have slides we will share and put on the agenda in the coming weeks.  We will pick one of the projects and talk through it.  We are starting to document which ones we are interacting with and we have develop a breakdown of what our interactions is with.
    • Irfan Ghauri - Are there collaboration agreements?
      • In open source there are no formal collaborations except for O-RAN Alliance, 3GPP, and ETSI.  They require formal collaborations
      • Jinri raised a concern about the putting the O-RAN Alliance in the Partnership category.
        • It is not owned by O-RAN Alliance.
        • Peter Moonki Hong - How do the open source developers refer to the other collaborative projects such as Akraino?  For example I am a developer who would like to test O-RAN software stack and there are other components from Akraino.  Could you provide formal guidance of how we interact with the partnerships?
          • Jack - In the near term start by reaching out to Lusheng about integration.  Akraino is a part of the INF project it's early.  We have contacts from Akraino.  Acumos is being used by the Near real time RIC dashboard.  Reach out to the TSC in those projects.  We will expand the partnerships with a list of contacts.
•  Jinri Huang discuss PTLs slide preparation for the F2F meeting.
  • Top mission is the complete the alignment with the working group at the face to face meeting.
  • Rittwik - preparing one slide deck for discussing the near real time RIC.  We should sit in the WG3 meeting. 
    • From Non Real Time RIC we presented our alignment with WG2.  WG1 and WG6 I am quite confused about the scope and architecture when it comes to the Non real time RIC.
      • Can you share the slides with the community?
        • Yes, there is one slide.
          • Jinri needs to see whether these items are aligned.  
            •  John Keeney  provide alignment slide for f2f meeting to Jinri Huang
  • Jinri requesting all the working groups to present their slides by the end of this week.

1. Release Manager/Release Planning: Weekly TOC Scheduling
   • There is a formal request.  In the Amber release this schedule was ambitious process.  One of the goals is to get people to get familiar and start contributing.  Code freeze is supposed to occur at the end of this week.  The developers enter a maintenance cycle.  To get a release out we add a maintenance release.  So the developers can continue to fix defects while everyone plans on what the new features are in the B release.  This next window October 14 - November 2 is time to work on fixing bugs on the software only for this release.  We should allow this extension because there is not enough code to do end to end testing.
   • The proposal is to move the code freeze date to add a development sprint 5.  Focus on getting the code as mature as possible for Amber to make it useful.  This is a one time event.
     • Jinri agrees to delay. 
     • Extend the release schedule code freeze from October to November 2.  On motion made by Jinri Huang seconded by  user-2057e
       • VOTE: Vote taken, item passed
2. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Matti Hiltunen RIC Applications (RICAPP) 
   2. Thoralf Czichy RIC Platform (RIC)
      1. For legal reasons we need a controlled way to define the scope of the near-RT RIC platform. Concrete suggestion is here. The basic idea is a description of scope and RICP project meeting approval for changes to that scope plus TOC approval for new repos. Additionally we would like the following sentence in the beginning of each file (in addition to the copyright and license statement):  "This source code is part of the near-RT RIC (Radio Intelligent Controller) platform project (RICP)." (suggested by legal dept.). Jack's opinion on the extra sentence needed. The rest of the procedure was ok-ed by RICP project meeting.
         1. Jack will review the proposal.
         2. David - keep Paul in the loop to avoid surprises.
         3. John - The title should be updated.
         4. Action/TOC continue review the proposal and return with feedback
      2. E2AP documentation now available as document (PDF/DOCX) plus ASN.1 file: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/asn1-documents.git;a=tree
      3. RICP presentation at ONS, Antwerpen, 2019: Overall architecture (not component-specific)
   3. user-a934b O-RAN Centralized Unit (OCU)
      1. Request for approval of the committer.
   4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
   5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
   6. Martin Skorupski Operations and Maintenance (OAM)
   7. Alex Stancu Simulations (SIM)

   8. Xiaohua Zhang Infrastructure (INF)

   9. weichen ni Documentation (DOC)
   10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
   11. (TBD) O-RAN Radio Unit (ORU)

3. user-d3360 Test & Integration Planning (INT)

4. user-59b16 Requirements Software Architecture Committee

1. Discuss OSC Partners and Open Source alignment

1. PTLs attend user-d3360 meeting for Integration and Test.

1. Votes
   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for 02 Oct 2019 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
         VOTE: Vote taken, item passed
   2. Seeking approval from TOC for new code freeze date for Amber release to Oct 18 (or Oct 25). TOC to recommend a suitable date for code freeze.
      • Extend the release schedule code freeze date to November 2. 
        • On motion made by Jinri Huang 
        • Seconded by  user-2057e
        • VOTE: Vote taken, item passed
2. Actions
   1. Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
   2. Jinri Huang  expand on the events page with anything that is relevant to the Plugfest.
   3. Matti Hiltunen document the simulator test on the RSAC space in the wiki. 
   4. user-d3360 talk to Jack about which use cases are being covered by the test and integration team, for release B.
   5. John Keeney discuss renaming of near non real time RIC.
   6. John Keeney  provide alignment slide for f2f meeting to Jinri Huang