2025-05-15 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 | Deutsche Telekom AG | Maintainer |
|
@Jan Friman | Ericsson | Maintainer | x |
@Toshi Wakayama | KDDI | Maintainer | x |
@Ludovic Robert | Orange | Maintainer |
|
@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 | x |
@Nick Venezia | EUC Representative | x | |
@massimiliano.troiani | Verizon | EUC Representative |
|
@Doug Makishima | Summit Tech | EUC Representative | x |
George Glass alt: @Olta Vangjeli | TM Forum | TM Form Representative | x |
@Henry Calvert alt: @Mark Cornall | GSMA | GSMA Representative | x |
Community members may use @name tag to mark their attendance
Community:
@ALI IQBAL @Jesús Peña García-Oliva @Rafal Artych @Pierre Close @Artur Krukowski
Action Item Review
LF Staff: @Casey Cain
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
MCP Evaluation activity - first results
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/106528769
No comments.
Action Item Review
See home page Technical Steering Committee for current list of open action items
“All Sub Projects with stable versions in Spring25 to update their test statement issues until April 29th”
There were no new updates until or after April 29th.
Proposal is to keep the issues open for now as valid information, but at max until the Fall25 release candidates are available
TSC action to be closed
“All TSC participants to review the new API Design Guides within the main branch of Commonalities (see minutes)”
Proposal to close together with the approval of r3.1 of Commonalities (see below)
“@Tanja de Groot to check the project governance and release guidelines for consistency regarding skipping a meta-release for API repositories”
Ongoing issue #202 within release management
“Gary Clift report on the new setup of End User Council within next TSC Meeting on May 15th”
Gary has no longer the ability to support the EUC due to a job change.
@Nick Venezia @massimiliano.troiani @Doug Makishima to decide how to proceed
@Nick Venezia and @Doug Makishima volunteered to report in the TSC.
Governance & Project Management issues (@Casey Cain @Herbert Damker )
No updates this time.
Please remember to submit support requests to support@camaraproject.org
API Backlog (@Jorge Garcia Hospital)
No new API proposed for this session.
→ Open discussion on how to manage VPN related APIs, from current Site-to-Cloud-VPN to MultiPoint VPN proposal. Will update in TSC as soon as clarified.
Proposal how to manage stale API proposals and Sandbox API repositories in work
Standby/archived proposal will be included to manage those proposals and sandbox that are proposed but not “used”.
Commonalities (@Rafal Artych )
Approval of Commonalities r3.1 with 0.6.0-alpha.1 for Fall25 M1
Release PR for r3.1 [Update: Release r3.1 done 2025-05-16: https://github.com/camaraproject/Commonalities/releases/tag/r3.1]
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/113803450
No objections to release the alpha version, M1 deliverable achieved.
Pending issues as indicated in https://github.com/camaraproject/Commonalities/issues/423
second turn of improving documents clarity
error definitions
subscription APIs
x-correlator format change and clarifications
For the open issues solutions are preferred which are not impacting the APIs, and especially not imply breaking changes.
Identity & Consent Management (@Jesús Peña García-Oliva on behalf of @Axel Nennker)
Approval of IdentityAndConsentManagement r3.1 with 0.4.0-alpha.1 for Fall25 M1
https://github.com/camaraproject/IdentityAndConsentManagement/pull/292
No impact on existing API specifications expected for now.
Release management review done and addressed.
Ready for release r1.1 with the alpha version, M1 deliverable achieved.
[Update: release done 2025-05-16: https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r3.1 ]
The scope of the Fall25 meta-release is now closed and would only change for high-priority topics/bug fixes, always with the appropriate WG consensus.
There are no more significant updates from the previous TSC call. The last ICM call was cancelled.
Main discussions focused on CIBA Privacy and JWT bearer flow. No consensus has been reached yet.
Consent Info API. A first draft version has been created and work is now underway to finalise the API functional scope and consent status vocabulary.
@Jesús Peña García-Oliva Please create a release tracker for the ConsentInfo API [Update: done with https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/122519652]
Release Management (@Tanja de Groot)
Fall25 meta-release (here)
Currently 36 APIs proposed for the meta-release
18 new APIs
18 updated APIs
7 stable APIs (no new stable APIs, all are updates)
For infomation, the new APIs are:
qos-booking 0.1.0
qa-assistant-service v0.1.0
qa-assistant-manage v0.1.0
Optimal Edge Discovery v0.1.0
NetworkAccessManagement v0.1.0
knowledge-base-manage v0.1.0
high-throughput-elastic-networks v0.1.0
energy-footprint-notification v0.1.0
device-data-volume 0.1.0
dedicated-network-profiles v0.1.0
dedicated-network-accesses v0.1.0
dedicated-network v0.1.0
data-volume-subscriptions 0.1.0
click-to-dial v0.1.0
blockchain-public-address-validation v0.1.0
Application Endpoint Registration v0.1.0
Application Endpoint Discovery v0.1.0
Session Insights v0.1.0
Fall25 M1: declaration of Fall25 M1 milestone
Approval from TSC requested for the alpha releases of Commonalities and ICM:
approved with the release of Commonalities and ICM r1.1.
Fall25 M2: release-candidate of Commonalities and ICM - June 7
Fall25 M3: first release-candidates of APIs - Jun 21
Proposal how to ensure release reviews of API Repository release PR (see also ReleaseManagement/issues/195) to avoid merging a not yet approved API release:
A (small) team release-management_reviewers will be defined as codeowners of the CHANGELOG.md file in all repositories
With that the team will be automatically assigned to all PRs which are changing the CHANGELOG.md, which should usually be only release PRs (but also exceptions might be worse to be shortly reviewed and approved by the team)
With that these PRs can only be merged with an approval by a member of the release-management_reviewers team, avoiding accidental early merges of release PRs
Prerequisites:
The release-management_reviewers team must have write access to all (API) repositories (can be defined on CAMARA organization level), this is a restriction from Github (all CODEOWNERS must have write access), but they will be codeowners only of CHANGELOG.md files
In every CODEOWNERS file an additional line has to added
Comments / support for the proposal?
No objections, proposal can be implemented.
MCP Evaluation activity - initial results and work items (@Herbert Damker )
Presented (draft) slides:
Meetings of the group are currently weekly on Mondays at 14:00 UTC. Link to register / join.
Slides will be discussed again on next Monday, to get an agreed version for the Board meeting on May 22nd.
Comments are welcome, via direct mail, in Slack, on the TSC mailing list, or on Monday in the meeting.
Any Other Business
...
Next Meeting
Next TSC Meeting will be on June 5th, 09:00 UTC
Specific agenda topics backlog:
...
...