Meeting Recording: 

Meeting Chat File: 

Attendees & Representation. Please add your name to the attendance table below.


Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Attendees

Name

Company
SHANKAR MALIK University of Delhi
Daniel Havey Microsoft
Santhosh Fernandes Walmart
Microsoft
Walmart
Charles Liu Walmart
Dhivya R Walmart
Karan Dalal Walmart
Jay Sheth Walmart
Netaji Subhas University of Technology












LF Staff: LJ Illuzzi 

Agenda

Minutes/Updates

  • Weekly TSC Meeting Day and Time Change
    • Proposed new day and time: Tuesdays at 9am to 10am PST or Tuesdays at 9:30am to 10:30am PST, starting Tuesday May 2.
    • Chat vote
      • Discussed, still working on resolving conflicts.


  • R2 Release Management (Dhivya)
    • Chaining - on track for May
    • Package - still have to build on 5.16 kernel
      • Need traffic mirroring
      • Multi-nic support
      • Might take a couple of more weeks
    • Break down issues into sub-issues so that progress is shown on dashboard


  • Issue discussion/Dev updates
    • L3AF R2
      • Lightweight RBAC: https://github.com/l3af-project/l3af-arch/discussions/57 
        • Dave- Here's a possible set of ranked evaluation criteria. Feel free to add to, reword, or argue for reordering:

          1. Allows use of existing tools for managing RBAC for other services.
          2. Uses existing mature implementation that is widely understood, used, and actively maintained.
          3. Ability to support multi-level hierarchy of complex scopes and user groups.
          4. Minimize protocol overhead between the client and the L3AFD service.
          5. Standards compliant.
          6. Minimize overhead (CPU, disk, memory) on the L3AFD host.
        • Revised: (See issue on Github)
          1. Allows use of existing tools for managing RBAC for other services.
          2. Uses existing mature implementation that is widely understood, used, and actively maintained.
          3. Extensible (e.g., to support multi-level hierarchy of complex scopes and user groups).
          4. Minimize protocol overhead between the client and the L3AFD service.
          5. Standards compliant.
          6. Minimize overhead (CPU, disk, memory) on the L3AFD host
      • PRs
    • L3AFD v2.1
    • L3AF on Windows
      • LFN Mentorship Program for L3AF on Windows
        • Updates from :
          • 7 applicants (2 complete applications)
          • No interviews yet
          • Next Steps:
            • encourage Mentees to complete applications
            • then, review applications for interviews


  • Signing of eBPF Programs (Karan)




  • Any Other Business


Action Items

  • Dhivya R Release Management Plan- add milestoners for testing, documentation, package. What else is needed from a delivery standpoint?
  • Daniel Havey coordinate Traffic Monitoring Blog with LFN Marketing


Future Agenda Items