/
2025-11-06 TSC Minutes

2025-11-06 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

@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

 

@Nick Venezia

Centillion.ai

EUC Representative

 

@massimiliano.troiani

Verizon

EUC Representative

 

@Doug Makishima

Summit Tech

EUC Representative

 

George Glass

alt: @Olta Vangjeli

TM Forum

TM Form Representative

 

@Henry Calvert

alt: @Mark Cornall

GSMA

GSMA Representative 

X

Community members may use @name tag to mark their attendance

Community: @Rafal Artych

@Alberto Ramos Monaga @Jesús Peña García-Oliva Kamran Keykhosravi @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 - Draft for Review

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

Governance & Project Management issues

  • TSC Election

    • Nomination phase start will be announced by LF team asap [Update: done with https://lists.camaraproject.org/g/tsc/message/344 ]

    • Eligible to nominate and later vote are according to the ProjectCharter all Maintainers within Working Groups and within API Repositories which are part of a Sub Project. Currently in total 62 people.

    • Members of CAMARA GitHub org can see the list here.

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

    • Final approval of timelines for Spring26 and Fall26 including the guidance for APIs regarding participation within the Spring26 meta-release (as presented within last TSC and available on the preliminary wiki pages)

    • Specific guidance: APIs who want to release in Spring26 to prepare scope until December 15th (M1 milestone). The API team needs to first submit an issue in Release Management to request Spring26 participation

    • Decision: approved

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

    • Discussion & way forward to approval, depending on comments

    • Final review after comments are addressed until next Thursday

    • Request to have a view on the proposed candidates within the issue comments

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

    • Shortlist of name pairs from the issue discussion:

      • Spark YY / Anchor YY — start vs consolidation metaphor.

      • Foundation YY / Consolidation YY — descriptive, “build then steady” cycle.

      • Seed YY / Harvest YY — natural‐cycle metaphor: seed planted, then harvest reaped.

      • YYYYH1 / YYYYH2 — purely chronological halves, minimal metaphor, maximal clarity.

    • Proposed voting:

      • Voters: TSC Participants + Outreach Committee

      • Voting type: Condorcet IRV (combines pairwise comparison with ranked voting to fairly identify the option most preferred by the group)

    • Decision:

      • The short list is set.

      • Request to LF to set-up the vote process (@Casey Cain ) as soon as possible & ran for one week.

API Backlog (@Alberto Ramos Monaga )

  • There are no new APIs brought to the TSC for approval.

  • Other Topics:

    • CAMARA APIs - Functional Differences (Use-Case & Data Semantics Edition): A draft 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)

      • Issues opened within both sub projects concerned (NumberInsights, KnowYourCustomer) to draw attention

    • Provider Implementation - Energy Footprint Notification #262 - Provider implementation repository created (link)

Commonalities (@Rafal Artych )

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

  • Spring26 Meta-release: The ICM scope for the Spring26 meta-release will be finalized by the November 30th deadline (M1 milestone date), but candidate topics should be brought in earlier. The working group is already working on pull requests (PRs) that cover some of the scope topics:

    • Create a guideline for API consumers and API providers which flow to use when Issue #316 (Fixed by PR #320) ==> Ready to be merged by EOW

    • Strengthen DPoP Support in CAMARA ICM Security Profile Issue #318 ==> strengthening the DPoP implementation to protect against man-in-the-middle and replay attacks. New PR #325 was created this week to address this issue.

    • New issue included in scope to add JWT Bearer flow with Operator Token.

  • Other relevant updates on existing ICM issues/discussions from the last call:

  • ConsentInfo - New Feature & release strategy: The PR #41 introducing a callbackUrl is ready for final review. This feature eliminates the need for API Consumers to poll the outcome of the consent capture process, and could be significant enough to justify a new, independent API release targeting version 0.2.0. This follows the new strategy of releasing API updates outside of the main meta-release schedule (e.g. Spring26).

Release Management (@Tanja de Groot)

  • Approval by TSC of the proposed new meta-release time lines: yes (see above in Governance issues)

  • M1 (Nov 30)

  • M1 APIs (Dec 15 - by exception only)

    • APIs are recommended to skip Spring26 and target either a release outside the meta-release first or the Fall26 meta-release.

    • Some exceptions may be considered by Release Management:

      • The concerned APIs should submit an issue in Release Management to request Spring26 participation with a link to their release tracker.

      • NOTE: please be aware that the Spring26 schedule is very tight for APIs.

  • M2 (Jan 31st, 2026)

    • Target date for the release-candidate of Commonalities & ICM.

    • Base for Fall26 APIs.

  • Upcoming: automation of API release tracking

    • Introduce the concept of the release-plan.yaml files

      • beta test with a few APIs in the Spring26 meta-release timeframe

      • target full deployment done for Fall26 meta-release tracking.

    • Target to present the concept and what the API Sub Projects need to do in the AHC on November 13 (might be postponed to later)

MCP Whitepaper - Draft for Review (@Nick Venezia @Tanja de Groot )

Any Other Business

  • Demands are coming in to GSMA for solutions to using CAMARA APIs for IoT use cases. What needs to be done to facilitate this? - M Cornall

    • Open an issue in Commonalities and pointers within the IoT related repositories (incl. DeviceLocation) to this issue about implications @Mark Cornall (@Jose Luis Urien Pinedo will establish the contact with interested parties from DeviceLocation)

    • ICM is also impacted, regarding tokens for IoT devices and consent management

    • Might require a taskforce to sort the issues

Next Meeting

Action items

LF team to setup vote for https://github.com/camaraproject/Governance/issues/200 as defined in TSC meeting Nov 6th, vote to be concluded before next TSC meeting @Casey Cain Nov 12, 2025
Open an issue in Commonalities and pointers within the IoT related repositories (incl. DeviceLocation) to issue about CAMARA APIs for IoT use cases @Mark Cornall
Provide MCP whitepaper version for final review until next Thursday (November 13th) @Tanja de Groot Nov 13, 2025