2025-04-17 TSC Minutes

DRAFT MINUTES

Attendees & Representation

LF Staff: @Casey Cain

Agenda

• Review and approval of previous meeting minutes

• Action Items Review

• General Topics

  • Governance & project management issues

  • Release Management

  • Commonalities

  • Identity & Consent Management

  • API Backlog

  • End User Council (EUC)

• Specific Topics

  • Board task to evaluate Model Context Protocol (MCP)

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/101253182

  • No Comments - Agreed

Action Item Review

• See home page Technical Steering Committee for current list of open action items

  • Ongoing: “@Herbert Damker to discuss announcement event of Fall25 meta-release with Marketing working group”

    • According to 2025 Event Tracker there is no event which fits perfectly and has the right audience. An own virtual event together with a press release is currently in discussion.

Governance & Project Management issues

• No major update from @Casey Cain

• The Board meeting on March 27th asked the “CAMARA TSC to come up with initial positioning to MCP and any suggested partner relationships”

  • Some Background:

    • Model Context Protocol (MCP) is a pragmatic way for large language models (LLMs) and AI Agents to interact with the outside world through clearly defined capabilities like file operations, web browsing, or tool usage. It was initially proposed by Anthrophic (Claude AI), and is in the meantime supported by several AI companies, including OpenAI and Microsoft.

    • Initial discussion in the CAMARA Board was that CAMARA APIs and MCP represent complementary approaches to API interoperability that could create powerful synergies. CAMARA standardizes telecom network capabilities through well-defined, intent-based APIs that work consistently across different operators, while MCP provides a structured framework for AI systems to interact with external tools and services.

  • It is important for CAMARA to have a clear strategic message about these synergies and to evaluate what is needed to be done technically within CAMARA to support this message.

  • Proposal by @Herbert Damker to run a TSC activity to create the requested outcome until the Board meeting in May

    • Volunteers: @Nick Venezia@Herbert Damker @Shilpa Padgaonkar @Jorge Garcia Hospital @Ludovic Robert @Tanja de Groot @diego.gonzalezmartinez(added after the TSC meeting as did not assist the meeting)

    • Initial meeting: Friday, 25th, 14:00 UTC (16:00 CEST) (@Herbert Damker to request the meeting via support@camaraproject.org)

    • Wiki and Slack as tools? yes

  • More discussion later in special topic if time is left.

Release Management (@Tanja de Groot)

• Fall25 meta-release

  • M0

    • Fall25 kickoff (M0) was announce by email after off-line support by Herbert to reach TSC quorum

    • The meta-release plan can be found here: https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/36241429

  • M1

    • Request to TSC to approve the proposal to shift date from April 15 to April 29th

      • Decision: No objection - OK to the shift

    • Commonalities and Identity & Consent Management

      • teams are preparing their alpha release, but need a bit more time after the heavy load of Spring25

      • the scope issues with the Fall25 content are available on the meta-release page

    • AIl Sub Projects are asked to create their Fall25 API release trackers and reading the scope issues in preparation.

      • If there are no impacts from Commonalities & ICM an API can be off a meta release but this will probably be not the case…

      • @Tanja de Groot will check the project governance and release guidelines for consistency

    • Release Management will provide a few updates to the process based on feedback which mainly concerns the following:

      • guidelines for versioning in event types (update to Commonalities API design guidelines)

      • continuous numbering of release-candidates across pre-releases in the same meta-release to avoid number clashes

      • add API description (for the marketing web site) in the API readiness checklist (request from API Backlog and Marketing Working Group team)

• Spring25 meta-release (closed)

  • For the stable APIs of the Spring25 meta-release, Sub Projects are asked to ensure to update their test statement issue once implementation tests have been achieved. Target is to close these issues by April 29^th.

Commonalities (@Rafal Artych )

• New guidelines documents:

  •  

  •  

  • Second iteration of documents editing is needed: issues #445, #446, #447, #448, … coming from the review (improvements and clarifications)

  • Request to all to review the documents and raise issues for further improvements and clarifications of the documents (separate from substantial changes)

• https://github.com/camaraproject/Commonalities/issues/444 - alpha release planned for Apr 29, 2025

Identity & Consent Management (@Axel Nennker )

• Overview https://github.com/camaraproject/IdentityAndConsentManagement/issues/275

• https://github.com/camaraproject/IdentityAndConsentManagement/issues/288

• https://github.com/camaraproject/IdentityAndConsentManagement/pull/290
  There is a new draft PR for a new flow “JWT Bearer Flow”
  Typical APIs that might use this flow are e.g. NumberVerification or Sim-Swap.
  This flow needs fewer network requests compared to CIBA and OIDC Authorization Code Flow.
  The User is authenticated e.g. by a TS.43 token

• Ongoing: https://github.com/camaraproject/IdentityAndConsentManagement/issues/258
  We are getting to the core of it.

API Backlog (@Jorge Garcia Hospital)

• (See message from @Jorge Garcia Hospital with proposals for 17/04)

Two APIs reviewed (previously presented during MWC TSC session. Proposal to create a joint Sandbox API repository Network Insights:

Note: Only China Unicom is commited to this API yet.

• Network Health Assessment

  • Provides the health score of a given network.

  • Proposed by China Unicom, original issue 127, Network Health Assessment template

  • Decision: OK

• Network Traffic Analysis

  • Provides statistical information of the traffic exchanged by the users of a given network.

  • Proposed by China Unicom, original issue 128, Network Traffic Analysis template

  • Decision: OK

One new API proposed: Voice Notification

• API to provide applications with the capability to send audio notifications to user’s devices based on standard network mechanisms.

• Supported by China Unicom, original issue 157, Voice Notification template

• Decision: No objection - ok

End User Council (EUC) (@Gary Clift)

• To be discussed during next TSC

Evaluation of Model Context Protocol (MCP) (@Herbert Damker)

• @Herbert Damker initialized a page here and went thru this page.

• Material from @Nick Venezia to be added.

Any Other Business

• The Sub Project Number Verification is searching for a better name to avoid confusion with the NumberVerification API and repository:
  https://github.com/camaraproject/NumberVerification/issues/185

Next Meeting

• The next TSC would be on May 1st, a public holiday in many countries - proposal is to skip this occurrence.

• Next TSC Meeting will be then on Thursday, May 15th, 15:00 UTC (Note: 17:00 CEST / 08:00 PST)

• Specific agenda topics backlog:

  • None

Action items