2025-11-20 TSC Minutes

Attendees & Representation

LF Staff:

Agenda

• Review and approval of previous meeting minutes

• Action Items Review

• General Topics

  • Governance & project management issues

  • API Backlog

  • Commonalities

  • Identity & Consent Management

  • Release Management

• Specific Topics

  • MCP Whitepaper - Final Review status & planning

  • Recommended LF projects for CAMARA participation …

• 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/306970684

  • Approved

Action Item Review

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

  • All three action items from TSC on 2025-11-06 were done

Governance & Project Management issues (@Casey Cain @Herbert Damker )

• TSC Election - Status of nominations

  • 12 nominations for Sub Project / Working Group representatives: all 10 current Sub Project representatives plus two additional nominees (Ben Hepworth from CableLabs and Kevin Smith from Vodafone)

  • @Herbert Damker has created https://github.com/camaraproject/Governance/issues/206, with the question if this proposal can get the needed support (2/3 of voting TSC participants)

    • Opening a vote on the proposal: yes - via approval on https://github.com/camaraproject/Governance/pull/207
      [Update 2025-11-21: The PR got 9 approvals from TSC participants plus the one from the PR author and had with that the needed super majority of at least 9 TSC participants. The PR is merged and with that the ProjectCharter is updated]

    • Prolong the nomination phase: yes - until end of Thursday November, 26th
      @Casey Cain to send out an update information regarding the change from 10 to 12 seats for Maintainer representatives and prolongation of the nomination phase Nov 21, 2025

• https://github.com/camaraproject/Governance/issues/200 - Status of vote

  • 11 out of 22 TSC / Outreach Committee Voting representatives have voted

  • The result is very tight, no winner in Condorcet Round (one to one comparisons, winner would need to beat all), in Instant Run Off round, “YYYYH1 / YYYYH2” got the majority finally. Nevertheless this options was also ranked lowest four times:

  • Conclusion: we take the winner as working title but ask Marketing Working Group for potential better proposal(s), we might vote again.

  • Open

    

  • https://github.com/camaraproject/Governance/issues/197

    • @Casey Cain Proposal to vote on: Shall the TSC Migrate to Zulip from Slack?

    • @Herbert Damker sees a channel per Sub Project (if they want to have one) and Working Group as a prerequisite

      • @Casey Cain will evaluate the options, to create channels at least for the Working Groups, and most active Sub Projects

      • Based on the result the TSC will vote

  • https://github.com/camaraproject/camara-landscape/pull/195

    • second_path information has been updated. We are no moving forward with developing a new page for the website to highlight these changes. A draft will be made available before publishing.

    • Responsibility is with the Marketing Working Group

API Backlog (@Alberto Ramos Monaga )

1 new API for approval.

• IMEI Fraud Check API (#PR254 & #Issue63): Enables enterprises to query operator IMEI registries to see if a device is authorized, blacklisted (e.g. stolen / fraudulent) or under investigation. It leverages MNO systems (NEF + EIR or GSMA IMEI DB) to block activation of stolen devices, validate devices in resale/insurance/repair journeys, and strengthen fraud and risk controls.

  • API family owner: xFlow Research

  • Repository: Independent Sandbox repository within Device Indentifier subproject group (Agreement reached with @Eric Murray that IMEI fraud could (or would be discussed) during the same meetings as Device Identifier, but would have a separate repository - API Owner agrees with Eric’s proposal on how to align and communicate with the Device Identifier group).

  • Repository name discussion: Avoid using IMEI in the repository name. The owner suggests alternatives such as: “Mobile Device Fraud Check” or “Cellular Device Fraud Check,” to reflect a broader scope of device-related fraud validation.

    • Decision: approved, repository name: MobileDeviceFraudCheck

    • If there are better proposals for the name please go to https://github.com/camaraproject/APIBacklog/issues/279

Other topics:

• Consent Info API – Controlled Delegation evolution (scope enhancement #Issue276): Adds an optional Controlled Delegation mode so trusted developers can capture consent inside their own apps using operator-provided texts and parameters, while the operator keeps full responsibility for storing, auditing, exposing and revoking consent. The goal is to reduce UX friction, enable in-app/backend consent capture and support (re)consent campaigns, while remaining backward compatible with current AuthCode and CIBA flows. Work is already underway in the ICM group. (The work remains with the groups involved)

• CAMARA APIs - Functional Differences (Use-Case & Data Semantics Edition): A white paper is in work for publication on the CAMARA website to explain in detail what problem each API solves, what data it delivers, how to interpret it, and how to combine them in risk and error-prevention policies (Audience: Non-telco experts) APIs covered: SIM Swap · Device Swap · Tenure · Number Recycling - (link) - Under review

• Provider Implementation - IoT Network Optimization #278

• Schedule additional API Backlog Working Group meetings #274 - @Shilpa Padgaonkar A new recurring meeting series was proposed to improve participation from colleagues based in U.S. time zones. Proposed slot: 1st & 3rd Wednesdays, 15:00 PST (23:00 UTC / 00:00 CET next day).

  • Participants don’t want to add more backlog meetings because it would fragment discussions and complicate coordination with the TSC. As a compromise, they’re open to moving the existing second backlog meeting to a later time (around 17:00–18:00 UTC) so it’s still workable for Europe but also accessible for North American colleagues.

  • See comment from @Shilpa Padgaonkar below on the page, proposing to keep current time slot.

Commonalities (@Rafal Artych )

• https://github.com/camaraproject/Commonalities/issues/556

  • Request to all TSC participants to review and comment on the issue due to its far reaching consequences

• https://github.com/camaraproject/Commonalities/issues/555. Discussion in https://github.com/camaraproject/Commonalities/pull/557

  • distinguished cases of “limited success” and “no success”

  • tends to be API-specific

  • @Herbert Damker a check of current stable APIs and their approaches could be helpful

• https://github.com/camaraproject/Commonalities/issues/560

  • networkAccessIdentifier (3GPP external id) was foreseen as an identifier for IoT use cases in Device object

Identity & Consent Management (@Jesús Peña García-Oliva )

• Spring26 Meta-release Readiness: The ICM scope for the Spring26 meta-release is currently 45% complete. The Working Group is pushing to finalize candidate topics before the M1 deadline on November 30. No new big topics will be accepted after this date unless critical.

  • Main update: Issue #316 Create a guideline for API consumers and API providers which flow to use when (Fixed by PR #320) ==> MERGED

  • With the shift to an annual ICM meta-release cycle, it would make sense to target a stable version of the ICM Guidelines for Spring26, similar to the approach taken for Commonalities. This will be opened for discussion within the Working Group.

• Issue #318 Strengthen DPoP Support in CAMARA ICM Security Profile => strengthening the DPoP implementation to protect against man-in-the-middle and replay attacks. Discussions continue on using server metadata versus specific security schemes for DPoP extensions in PR #325.

• Issue #326 JWT Bearer flow with Operator Token => A PR (#334) providing a high-level example/diagram of the JWT bearer flow using an operator token (temporary token) has been created.

• ConsentInfo - callbackUrl: The PR #41 adds an optional callbackUrl so that API consumers can regain control after the consent capture journey ends. The main pending debate is whether to mandate pre-registration and strict validation of the callback URL (more secure but higher barrier to entry) versus recommending it.

  • The group agreed to set a deadline to make a final decision on this topic at the next ICM meeting. This PR has been around for several weeks already, and the goal is to close it before the Christmas break.

• A proposal for "Controlled Delegation" (allowing delegated consent capture for trusted API consumers) has been introduced.

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

  • https://github.com/camaraproject/ConsentInfo/issues/42

Release Management (@Tanja de Groot)

• Spring26 meta-release (https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/268500993 )

  • M1 Commonalities & ICM (Nov 30):

    • Cut-off date to close the Commonalities and ICM scopes for Spring26 (will be also base for Fall26 APIs)

    • No alpha releases are planned by this date.

  • M1 APIs (Dec 15):

    • Cut-off date for API Sub Projects to create an issue e.g. “Request for Spring26 participation: <api-repo-name>” in Release Management here.

  • M2 (Jan 31, 2026): ongoing according to (new) plan.

  • M3 (Jan 31, 2026): ongoing according to (new) plan.

• Release Management automation

  • Test of automation procedures will be rolled out shortly to some API projects. Once OK, the intent is to apply this to all APIs for the Spring26 meta-release.

  • Ongoing: the update of the Release Management process documentation in line with the automation. This should make the processes simpler for both API Sub Projects and for the Release Management team

MCP Whitepaper - Final Review status & planning (@Tanja de Groot )

• MCP white paper near-final draft available here: https://lf-camaraproject.atlassian.net/wiki/x/IQC4Eg

  • Received comments have been integrated - thanks to all !

  • Remaining comments to be addressed with/by the editor.

• Request for TSC for

  • approval of the paper and the go-ahead with MCP work in CAMARA: yes

  • delegation of final approval of the edited whitepaper to the MCP activity team tentatively on Nov 22 (or later, when final version is available): yes

Recommended LF projects for CAMARA participation and provide alignment on collaboration priorities (@Nick Venezia )

• https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/237207863

Any Other Business

• ...

Next Meeting

• Next TSC Meeting will be on December, 4th, 9:00 UTC

• Specific agenda topics backlog:

  • Ecosystem Analysis of LF projects (@Nick Venezia)

  • ... 

Action items