Attendees & Representation (default sort: member first name)

TAC Members and Project representatives should mark their attendance below 

Member Representatives

RepresentingMember
AT&T
China Mobile

vacant

China Telecomvacant
Cisco
Deutsche Telekom
Ericsson
Google

vacant

Huawei
Infosys
Nokia

Red Hat

Tech Mahindra

vacant

TELUS
Verizon

vacant

Wallmart
ZTE

Community Representatives

CommunityRepresentativeLifecycle
ONAPGraduated
OpenDaylightGraduated
AnuketGraduated
FD.ioGraduated
Nephio
Graduated
ODIMSandbox
EMCOSandbox
L3AFSandbox
XGVelaSandbox

Elected Representatives

Chairperson
Vice-Chair
Security
5G-SBP

Agenda

  • We will start by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
  • Roll Call
  • Check Action Items & Topic Requests
  • General Topics
    • Netmaker project introduction - Netmaker team (30m)
    • Refreshed documentation approval
    • Security initiative -
      • status update.
      • Verifying we have the right points of contact.
      • Where are the projects on the security roadmap? What are they struggling with?
      • What is the TAC expected to do? Recommend? Enforce?
    • Proposal for TAC topics backlog - Muddasar Ahmed 
    • Edge Use Cases Lisa Caywood Olaf Renner  - What is the TAC role here?
      • How is it related to the other "threads" the TAC is dealing with (AI, Security, Edge)
  • Any Other Topics

Action items

Minutes

Netmaker Project Introduction

  • Alex Feiszli introduced the Netmaker project to the LFN.
    • He announce that they are considering joining the LFN.
  • Muddasar Ahmed do you have functional parity with any commercial solutions?
    • Alex Feiszli We tend to avoid hardware dependencies. 
      • If you are looking to do something simple like connecting sites, then maybe this isn't the solution for you.
      • We are also a mono-core repository currently.
      • The org name is the same as our project name and will need to be updated
    • We do not yet have a Technical Charter or a TSC
    • Kenny Paul suggested that we get Alex Feiszli in touch with the Linux Foundations project formation team.
      • A project charter is a great place to start
      • The Project formation team can help with suggestions for project names and 

Security

  • Comments