2025-01-16 TSC Minutes
- Herbert Damker
- Tanja de Groot
- Casey Cain
DRAFT 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 | x |
@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 | x |
@Nick Venezia | EUC Representative | x | |
Massimiliano Troiani | Verizon | EUC Representative | ย |
@Doug Makishima | Summit Tech | EUC Representative | x |
George Glass | TM Forum | TM Form Representative | ย |
@Henry Calvert | GSMA | GSMA Representativeย | x |
Community members may use @name tag to mark their attendance
Community: @Jorge Garcia Hospital @Kevin Smith @Mark Cornall @Ming Hui Foo @G. Murat Karabulut @Pierre Close @Rafal Artych @Thorsten Lohmar @Artur Krukowski
ย
ย
ย
LF Staff: @Casey Cain @Evan Harrison
Agenda
The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company 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
na
Any Other Topics
Minutes
Review and approval of previous meeting minutes
Minutes of previous TSC meeting: 2024-12-19 TSC Minutes
Minutes were approved at 15:05 on 1/16/25
Action Item Review
See home page Technical Steering Committee for current list of open action items
Issue(s) within Governance for the next steps to execute the Sandbox / Incubated approach see below, action done
Governance & Project Management issues
Sandbox / Incubated Approach
Issue with next steps: https://github.com/camaraproject/Governance/issues/170
PR to update the API-Onboarding.md document by @Jorge Garcia Hospital:
https://github.com/camaraproject/Governance/pull/171PR to update the Template_API_Repository:
https://github.com/camaraproject/Template_API_Repository/pull/14
New issue in Governance: https://github.com/camaraproject/Governance/issues/172
Proposed action Item: @Herbert Damker Review open issues within Governance and propose way forward for them (if not in work) Jan 30, 2025
API Backlog (@Jorge Garcia Hospital @patricia.serranogonzalez@telefonica.com )
Please review https://github.com/camaraproject/Governance/pull/171
New proposal(s) from APIBacklog working group:
QoSBooking, supported by KDDI and TEF, to be create in a new API Repository in context of the QualityOnDemand sub project
Original Issue #154
Proposal approved, Sandbox API Repository (using mailing list of QoD), and wiki page under Sandbox API Repositories
Inclusion of Participants pages per API repository for companies to express their interest in the developed APIs. Templates to be included.
Commonalities (@Rafal Artych )
Error 429
https://github.com/camaraproject/Commonalities/issues/372
GENERIC_429_QUOTA_EXCEEDED:
description: Request is rejected due to exceeding a business quota limit
value:
status: 429
code: QUOTA_EXCEEDED
message: Either out of resource quota or reaching rate limiting.
GENERIC_429_TOO_MANY_REQUESTS:
description: API Server request limit is overpassed
value:
status: 429
code: TOO_MANY_REQUESTS
message: Either out of resource quota or reaching rate limiting.
Analysis: Error 429
Kevin: statement about to original purpose of 429, better option for business quota?
x-correlatorpattern - https://github.com/camaraproject/Commonalities/pull/373Open a new issue about the breaking change implied by minimum length of 1 (breaking potentially lot of API Clients) @Herbert Damker Jan 17, 2025
Release Candidate.1 - preparation of r2.2
After Commonalities meeting on 20.01.2025
In preparation:https://lf-camaraproject.atlassian.net/wiki/x/AYC3Aw
Please review to ensure that it is correct and complete
Identity & Consent Management (@Axel Nennker )
Quick, adhoc update by Eric and Diego:
Working on release candidate for Spring25
Probably no direct impact on API definition
Changes (exact wordings see PRs within ICM):
DPoP support approved, optional for API providers to support, API provider can require the use, see table
Relevant progress, agreement almost reached:
JWT tokens, agreed lifetime must not beyond 300 seconds
Authorization request in auth code flow are recommended to be signed
Login_hint in Auth code flow optional parameter, but recommended to be ignored
Error codes for error scenarios
Release Management (@Tanja de Groot @Samuel Adeyemo )
Spring25 meta-release: 40 APIs - 16 new + all Fall24 APIs (24) are listed
M3 date (2025-01-17):
40% of the release PR review requests (9 out of expected 23 repositories) so far, so M3 deadline will not be met by all APIs.
Commonalities and ICM will likely be available next week.
proposal to shift M3 by 1 week to 2025-01-24 (or do we need 2 weeks ?)
Decision to go with the proposal to shift deadline for M3 Pull Requests to 2025-01-24.
Any Other Business
none
Next Meeting
Next TSC Meeting will be on February, 6th, 9:00 UTC (10:00 CET)
Specific agenda topics backlog:
none yet, feel free to propose via the tsc@lists.camaraproject.org mailing listย