2026-07-15 TSC Minutes
Representatives & Attendees
Quick Links: TSC Mailing List | Meeting Recordings
TSC Members | Company |
|---|---|
TSC Members may indicate their attendance by changing the cell background for their name to green. | |
@Sana Tariq | TELUS, Canada |
@Ciaran Johnston (Ericsson) | Ericsson |
@balaji varadaraju | Red Hat |
@Timo Perala (Nokia) | Nokia |
@Hsiu-Chi “蔡秀吉” | National Yang Ming Chiao Tung University (NYCU) |
@Raj Panchapakesan | AccuKnox Inc |
@Girish Kumar | Infosys |
Community members may @ tag themselves below to show their attendance.
@Liam Fallon
You can add action items anywhere in the minutes by typing “/action” and pressing enter
Action Items:
LF Staff:
Agenda
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. |
Key Updates
Potential LFN developer event during the LFN Japan ONE Summit - need to determine if there is interest from the Nephio community to participate
@Ciaran Johnston (Ericsson) to discuss options with @Casey Cain
Discuss on “coding agent contribution readiness”
@Liam Fallon has agreed to look at this from SIG Auto perspective
2026-06-17: no update yet, this was discussed with @Liam Fallon recently – would be good to get concluded before end of June
2026-07-15: we will adapt the kpt variant in porch, and propose an approach for the rest of the Nephio repos after that
Need to document a vulnerability reporting process. It then needs to be documented.
2026-06-17: no progress
@Hsiu-Chi “蔡秀吉” About the TSC meeting at 2026-06-03 TSC Minutes . As a volunteer on the vulnerability-reporting item, I've drafted a lightweight Nephio Security Response process — GitHub Private Vulnerability Reporting alongside sig-security@, a small rotating Security Response Committee with a 3-working-day triage SLA, an embargo/coordinated-disclosure policy with a zero-day fast-path, and CVEs issued via GitHub Security Advisories — and I've already privately identified and runtime-validated several security issues in main that we can run as the first real cases through it; I'll share the draft with Casey and Ciaran for their recommendation.
@Liam Fallon to add @Hsiu-Chi “蔡秀吉” as a reviewer if necessary to make the upstream commits to fix the vulnerabilities
SIG Status
Network Architecture
Nothing developing due to holidays. Needs to move to fortnightly
Automation
No attendance to SIG Automation as of late
Release
.
Security
.
Other Updates
.
Action Items Review
Minutes