Attendees & Representation

TAC Members and Project representatives should mark their attendance below 

Agenda

• Check Action Items & Topic Requests (Backlog)

• OpenAN Candidate Review @Chuanyu Chen

• Stratoweave Candidate Review

• Presentation on Network Energy Savings @Tracy Van Brakle

• Follow up with @Fatih Nar on breakdowns and roadmaps

• Reminder: May 20, 2026Project Updates to the Board

• Zulip Engagement

• Any Other Topics

OpenAN @Chuanyu Chen

• Project Overview:

  • Open source initiative for autonomous network tools (L4/L5 evolution)

  • License: Apache 2.0

  • Founders: China Mobile and Huawei (seed code contributors)

  Membership:

  • Current: ZTE, China Mobile, Huawei

  • Pending: Several CSPs and OSS vendors (internal approvals in progress)

  Timeline:

  • June 2026: Seed code release at DTW Copenhagen

  • December 2026: Additional version release

  Technical Scope:

  • Evolution from API-based to language-based to agentic AI interfaces

  • Built on LFN's A2A protocol with telecom extensions (A2A-T)

  • Focus: Multi-vendor, cross-layer, cross-domain integration

  Key Components:

  • A2A-T SDK for agent communication

  • Agent Registry Center (discovery, health, skill queries)

  • Agent Orchestration Center (workflow management)

  • Future: Execution engines, audit systems, asset management

  Governance:

  • LFN standard governance with TSC

  • Infrastructure setup with Linux Foundation

Stratoweave @Ian Farrer @Joachim Westphal

• Project Overview:

  • Open source network automation platform for IP, transport, and optical domains (MPLS, segment routing, CPE)

  • Addresses vendor lock-in issues experienced with closed-source platforms

  • License and governance to be established under LFN

• Key Capabilities:

  • Beyond configuration management: includes telemetry ingestion for conditional provisioning and health monitoring

  • Closed-loop architecture with real-time service health visibility (jitter, latency, packet loss)

  • Pre-built service automation library with common L2, L3 VPN, SD-WAN implementations for common vendor hardware

  • Single standalone binary deployment via container

• Architecture:

  • Northbound: NetConf, RestConf, TMF interfaces using IETF Yang models

  • Southbound: CLI and NetConf to devices

  • Bi-directional flow: South-to-north state data subscription via GNMI for health monitoring

  • Includes "Cerespo" - realistic service provider automation code example

• Questions & Discussion:

  • Q (Frank): How does StratoWeave relate to OpenDaylight given the similarities in service-facing and resource-facing functions?

    • A (Ian): StratoWeave is a single standalone binary with all functionality, not designed to plug into OpenDaylight

Network Energy Savings @Tracy Van Brakle

• Differred to next meeting

IMS DC SDK @Casey Cain

Casey introduced the IMS DC SDK as a new project that China Telecom is interested in donating to LFN. He noted this was an early preview requested by Arpit Joshipura to collect TAC feedback before any formal candidate announcement or technical onboarding. Casey clarified these were not his slides, and that he had only received the materials the previous day. A formal presentation by China Telecom is planned for a future TAC meeting.

TAC Feedback

Olaf Renner (Nokia) raised several points:

• No links to existing code repositories were provided in the deck, despite mentions of GSMA trial repos. He requested that these be shared.

• He was unable to find "OpenIDS" via web search, confirming the branding is not yet established.

• The slides did not mention cross-project collaboration opportunities. He noted that China Telecom mentioned being active contributors to ONAP but did not describe how the SDK might integrate with ONAP or other LFN projects. He asked whether the SDK would be useful for ONAP and whether there might be integration points with ONAP or O-RAN SC.

N.K. Shankaranarayanan (ONAP) responded that this had not previously come up and that he would take the question back to the ONAP TSC for discussion.

Girish Kumar (Infosys) asked for clarification on whether the SDK targets the client/handset side or the server/network side for supporting 5G calling, noting that the distinction was not clear from the slides and that the two are quite different.

Ranny Haiby (The Linux Foundation) agreed and suggested that the architecture diagram appeared to show a handset-side implementation. He recommended asking the proposers to clarify what is required on the handset versus what is required in the network.

Action Items

• Casey to meet with China Telecom (target: same day or next day) to gather additional detail and relay TAC feedback, including requests for code repository links, client vs. network clarification, cross-project integration opportunities (ONAP, O-RAN SC), and branding/trademark status.

• China Telecom to deliver a formal presentation at a future TAC meeting.

• N.K. Shankaranarayanan to raise the IMS DC SDK topic at the ONAP TSC for feedback on potential relevance.