2026-10-01 TSC Minutes
Attendees & Representation
TSC Members may indicate their attendance with an X in the far column | |||
|---|---|---|---|
Representatives | Organization | Role |
|
Herbert Damker | Deutsche Telekom AG | Maintainer | x |
Ben Hepworth | CableLabs | Maintainer |
|
Shilpa Padgaonkar | T-Mobile US | Maintainer |
|
Jan Friman | Ericsson | Maintainer | x |
Toshi Wakayama | KDDI | Maintainer | x |
Ludovic Robert | Orange | Maintainer | x |
Tanja de Groot | Nokia | Maintainer, Release Manager | x |
diego.gonzalezmartinez | Telefonica | Maintainer | x |
Jose Luis Urien Pinedo | Telefónica | Maintainer | x |
Eric Murray | Vodafone | Maintainer | x |
Mahesh Chapalamadugu | Verizon | Maintainer |
|
Kevin Smith | Vodafone | Maintainer |
|
Doug Makishima | Summit | EUC Representative | x |
Nick Venezia | EUC Representative |
| |
massimiliano.troiani | Verizon | EUC Representative |
|
George Glass alt: Olta Vangjeli | TM Forum | TM Form Representative |
|
Henry Calvert alt: Mark Cornall | GSMA | GSMA Representative | x x |
Community members may use @name tag to mark their attendance
Community: Pierre Close Surajj Jaggernath Rafal Artych Alberto Ramos Monaga Thorsten Lohmar
Action Item Review
LF Staff:
Agenda
The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company's legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
Review and approval of previous meeting minutes
General Topics
Governance & project management issues
API Backlog
Commonalities
Identity & Consent Management
Release Management
Specific Topics
ICM Lifecycle Management and API Compatibility Governance
Marketing WG - Whitepaper WoW
Any Other Topics
Minutes
Review and approval of previous meeting minutes
Minutes of previous TSC meeting: 2026-09-17 TSC Minutes
Approved
Action Item Review
See home page Technical Steering Committee for current list of open action items
One open action item Herbert Damker
Governance & Project Management issues
none today.
API Backlog (Alberto Ramos Monaga)
No new topics for TSC approval.
FYI: New onboarding tracker created for SimSwapTimeFrame #335. See more context on the last TSC meeting: 2026-09-17 TSC Minutes
Waiting for confirmation of the codeowners
FYI: Connectivity Governance API proposal #298 has been moved to “frozen” status following a group decision made at the last meeting due to a lack of activity.
Commonalities (Rafal Artych )
MCP Enablement
MCP event notification - in the roadmap (April 2027?) - first draft:
GitHub - modelcontextprotocol/experimental-ext-triggers-events: Incubation space for the MCP Triggers & Events Working Group ) we should postpone the definition how to expose CAMARA Subscription APIs until the MCP specification is ready
might be a late extension or update for the Signal27 Commonalities release (pause until then how event notifications are exposed via MCP)
use of Standard Webhooks (standardwebhooks.com) - standardizes the delivery mechanism specifically for HTTP webhooks: how to sign the payload, which headers carry the signature/id/timestamp, how to verify it, retry schedules, and operational concerns like SSRF (Server-Side Request Forgery) protection and timeout handling.
Event notification security updates · Issue #712 · camaraproject/Commonalities - multiple sub-issues for hardening notificationsDefine a concrete signing profile for event notifications (integrity, origin and replay protection) - here following Standard Webhooks guidelines is an option
Wide-ranging (API Backlog, TSC) topics for Signal27:
Collections vs Resource Groups vs Batch semantics (consistency boundaries)
TSC Participants are invited to provide their views on the topics.
Mark Cornall Seeing different approaches across implementations, therefore the work on aligning subscription delivery mechanism further is important. Webhooks are definitely a good option.
Identity & Consent Management (Axel Nennker )
Tanja de Groot had done the minutes of last meeting (see xxx), was short
Discussed succession for group moderation and coordination - no solution yet.
Please consider to step up for the role
Next important milestone is M1 for Signal27 (end of October)
Release Management (Tanja de Groot )
Sync26 meta-release (Sync26 meta-release (ex-Fall26) )
M3 (sep 15 → oct 6)
Status today: Reminder: M3 is reached with the publication of the first release-candidate. Overall, most APIs have done this (using Commonalities r4.3). API that have not yet reached M3 are listed below.
Sync26 has 38 participating repositories with 59 API (of which 1 new API since Fall25 (dedicated-network-areas) in 1 repository).
The Release Progress viewer is available hereCAMARA Release Progress
API | Status/Comm | Comment | Risk |
|---|---|---|---|
Snapshot/r4.4 | Review comments provided (#70) 5 days ago - Eric to review | Medium | |
Snapshot/r4.3 | Stable API, changes requested (#284) - 4/7 done; RM review tbd | Medium | |
Planned/r4.4 | Still (2) updates required (#92) - work ongoing | High | |
Exceptions: |
|
|
|
Has done a partial M3. Planned/r4.4 | r2.3 expected soon to implement updates to the accesses API as per review findings. | Low | |
(M3 done in QoD repo) | Planned/r4.4 | Repo split out from QualityOn Demand - next rc with r4.4 in new repo tbd | Low |
M4 (sep 30 → oct 30) - API public releases
Beyond the delay in M3 reviews, the Commonalities release r4.4 needs to be done which requires adaptatons of impacted APIs (in a new release candidate)
Prompt teams for the missing M3 and M4 updates in next TSC.
Independent APIs (18 APIs / 18 repos)
4 repos published
3 repo snaphots: 1 has “change requested”, 2 need Release Management review
others not active - what action to take (to be discussed in next Release Management meeting) ?
Signal27 meta-release
M1 (oct 31) on schedule (see above ICM and Commonalities reports).
Specific Topic: ICM Lifecycle Management and API Compatibility Governance (Tanja de Groot)
The document was approved by ICM team on Aug 26. Release Management keeps the ownership of the document as focuses on versioning and releases, not on ICM technical content.
The document is under final review by Release Management team and will be published shortly. A shorter version focusing on day-to-day management will be created for the Release Management documentation.
Two followup issues have been created for putting in place the defined approach:
Specific Topic: Marketing WG - Whitepaper WoW (Alberto Ramos Monaga )
Marketing WG - Whitepaper WoW (draft) #63: formal process for whitepaper authoring in CAMARA. The current state is a draft proposal by Markus Kümmerle.
Anyone can propose a whitepaper idea to the Outreach Committee.
The Outreach Committee evaluates and decides whether a whitepaper shall be developed.
Relevant CAMARA groups are asked for support; if support is missing the proposal ends.
Contributors work in a new dedicated repository hosting all whitepaper work.
The TSC approves the document / content.
The Outreach Committee publishes it.
(This process is not yet formally adopted. It is shared here for awareness as background for the two documents below.)
Number Verification - Operator Token Acquisition (link) The Number Insights Sub Project has produced an informative (non-normative) companion
guide to CAMARA NV API 2.1. The document describes how to obtain the operatorToken on Android using the TS.43 / GMS path via the OpenID4VP Digital Credentials API — a gap that CAMARA NV 2.1 leaves unspecified. It covers the full end-to-end flow: carrier eligibility check, credential
acquisition via Android Digital Credentials API, token exchange through the Aggregator (Channel Partner), and the final CAMARA NV API call.The TSC is asked to approve this document so it can be published by the Outreach Committee:
The content was approved within the NumberInsights Sub Project. It is not a marketing whitepaper but a more technical paper which is just additional documentation within the NumberVerification repository. Content should stay on the technical details level (which means that it is not a marketing whitepaper).
FYI: GSMA published a blueprint for NumberVerification, which is more business oriented; no overlap with the technical paper above. Marketing Working Group can consider to promote it together with the technical paper (Markus Kümmerle )
CQM API introduction (link) The Connectivity Quality Management Sub Project has finalised an introductory whitepaper.The document explains the nine CQM APIs as defined in the Sync26 meta-release — covering discovery, on-demand QoS, provisioned QoS, and reservation-based connectivity quality. It uses a live-event illustrative journey, a comparative matrix, and guardrails for external readers. The whitepaper is non-normative, intended for API consumers, developers, and technical product people. It has been finalised based on feedback received in recent weeks.
The TSC is asked to approve this document so it can be published by the Outreach Committee:
Approved if there are no (new) objections until the TSC meeting of Oct 15th.
Regarding QoS Profile examples Mark Cornall will open issues in CQM repo to propose to replace current examples in QualityOnDemand by links to GSMA document with profile definitions.
Any Other Business
Open Source Summit in Prague, October 7th - 9th
CAMARA is represented with a booth
The booth is supported by Mark Cornall Rafal Artych Herbert Damker, Sunia Imran (DT), and Jill Lovato
Please drop by if you on the conference next week!
Next Meeting
Next TSC Meeting will be on October 15th, 15:00 UTC
Specific agenda topics backlog:
...
...