/
2025-12-04 TSC Minutes

2025-12-04 TSC Minutes

Attendees & Representation

TSC Members may indicate their attendance with an X in the far column

Representatives

Organization

Role

 

@Ben Hepworth

CableLabs

Maintainer

x

@Herbert Damker

Deutsche Telekom AG

Maintainer

x

@Jan Friman

Ericsson

Maintainer

x

@Toshi Wakayama

KDDI

Maintainer

x

@Ludovic Robert

Orange

Maintainer

x

@Tanja de Groot

Nokia

Maintainer, Release Manager

x

@Shilpa Padgaonkar

T-Mobile US

Maintainer

 

@diego.gonzalezmartinez

Telefonica

Maintainer

x

@Jose Luis Urien Pinedo

Telefónica

Maintainer

x

@Eric Murray

Vodafone

Maintainer

 

@Kevin Smith

Vodafone

Maintainer

X

@Mahesh Chapalamadugu

Verizon

Maintainer

 

@Nick Venezia

Centillion.ai

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

Surajj Jaggernath

Vodafone

 

 

Community members may use @name tag to mark their attendance

Community: @Alberto Ramos Monaga @Rafal Artych @Artur Krukowski @ALI IQBAL @Pierre Close

 

 

 

 

 

 

 

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

  • Action Items Review

  • General Topics

    • Governance & project management issues

    • API Backlog

    • Commonalities

    • Identity & Consent Management

    • Release Management

  • Specific Topics

    • MCP Whitepaper

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

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

  • TSC Election (@Casey Cain )

  • Migration to Zulip (@Casey Cain)

    • @Herbert Damker creation of channels for working groups possible (ICM and ReleaseManagement done, Commonalities not yet)

    • @Kevin Smith well used in IETF.

    • No objections, @Casey Cain should go forward with the migration.

  • https://github.com/camaraproject/Governance/pull/201

    • Ready to merge [done]

    • For already evaluated once @Alberto Ramos Monaga will create issues in APIBacklog

API Backlog (@Jorge Garcia Hospital)

  • There are no new topics from backlog

  • Reminder: CAMARA APIs - Functional Differences (Use-Case & Data Semantics Edition): A white paper has been produced 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)

Commonalities (@Rafal Artych )

Identity & Consent Management (@diego.gonzalezmartinez on behalf of@Jesús Peña García-Oliva )

  • Spring26 meta-release status. The scope for ICM within Spring26 is now closed (M1 reached). The overall scope is currently 45% complete. The working group has issued a Call to Action for members to take ownership of remaining issues to meet the M2 (Release Candidate) deadline of January 31st.

    • Security profile update: DPoP additional recommendations for implementers. Proposal to strengthen DPoP support (Issue #318 / PR #325) is nearly ready. Discussions focused on naming conventions (e.g., removing “x-” prefix from certain claims), defining a recommended DPoP proof lifetime (e.g. 300s), and clarifying JTI reuse error-handling.

    • JWT-Bearer flow using Operator Token. The proposed flow (Issue #326 / PR #334) in under discussion. Notably, the GetSubscriberDeviceInfo step is considered optional (depending on the operator implementation). The working group agreed to treat internal steps as implementation-specific rather than normative. PR text will be updated accordingly.

  • Consent Info API evolution / Controlled Consent Capture Delegation.

    • The next version of the ConsentInfo API (target v0.2.0) is not bound to Spring26.

    • The PR adding an optional callbackUrl parameter feature in Consent Info API has been merged.

    • Meanwhile, Telefónica has provided a proposal that suggests managing Consent Capture Delegation via two distinct APIs rather than overloading the existing API. That proposal is under review and waiting for feedback.

    • Release of 0.2.0 ConsentInfo API will happen in next weeks (based on Fall25 Commonalities)

    • New API for Consent Capture Delegation will go into a later release

Further details of the above items can be found at https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/395116550

Release Management (@Tanja de Groot)

  • Spring26 meta-releasehttps://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/268500993

    • M1 Commonalities & ICM (Nov 30)

    • M1 APIs (Dec 15) - Spring26 is not recommended for APIs

      • A reminder has been sent to codeowners list that requests for Spring26 participation are to be done through a GitHub issue in Release Management. However it is preferred that APIs target Fall26 or do a release earlier outside the meta-release.

    • M2 (Jan 31, 2026) Release-candidate of Commonalities & ICM.

    • M3 (Jan 31, 2026) Release-candidate for Spring26 APIs.

    • Release Management automation activity is progressing (cudos to Herbert)

    • Topic from the GSMA OGWTG from aggregator need on making API releases more independent from ICM releases, e.g. forward compatibility from ICM rx.y. Tanja to create an issue in Release Management.

MCP Whitepaper (@Tanja de Groot)

Any Other Business

  • @Ludovic Robert present at APIDays Paris next week

Next Meeting

  • Next TSC Meeting will be on December 18th, 15:00 UTC (7:00 PT, 16:00 CET)

    • Skipping January, 1st instance.

  • Specific agenda topics backlog:

    • Ecosystem Analysis of LF projects (@Nick Venezia) → Dec 18th

    • ... 

Action items