DRAFT AGENDA
...
| Representative | Organization | Role | |
|---|---|---|---|
Deutsche Telekom AG | TSC Chair, Active Maintainer | x | |
Deutsche Telekom AG | Active Maintainer | x | |
Ericsson | Active Maintainer | x | |
KDDI | Active Maintainer | x | |
Orange | TSC Deputy Chair, Active Maintainer | x | |
Radisys | EUC Representative | ||
Summit Tech | EUC Representative | ||
Telefonica | Active Maintainer | x | |
Telefónica | Active Maintainer | x | |
Verizon | EUC Representative | ||
Vodafone | TSC Deputy Chair | x | |
Vodafone | Active Maintainer | x | |
| Chris Howell | Vonage | Active Maintainer | |
| George Glass | TM Forum | TM Forum Representative | |
| Olta Vangjeli | TM Forum | TM Forum Representative | x |
GSMA | GSMA Representative | x | |
GSMA | GSMA Representative | x | |
Airtel | Active Maintainer |
LF Staff:
Community: Tanja de Groot Rafal Artych Lazlo Suto Markus Kümmerle Ravi Shekar Nick Venezia Pierre Close Toyeeb Rehman Aleksandar Brankovic Ricardo Serrano Gutierrez Ramesh Shanmugasundaram Ramit Chawla (airtel)
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. |
...
- Issue #133 Adopt RFC 9457 error response format
- Slides presented by Lyle Bertz : 20240304-CAMARA-Issue 133 - RFC 9457 URN Option.pdf
- The issue will be closed with opening 2 more detailed issues for discussion in Commonalities:
- Adding a parameter to the current response format that would provide link to detailed error documentation
- Adopting RFC 9457 for error response format →Adopting RFC 9457 for Error Handling · Issue #157 · camaraproject/Commonalities (github.com). This is a 'burning' issue in term of impact of release.
- Herbert Damker indicated that companies have to interact on these if they want change, elsewhere we will keep as it.
- Issue #149 Consolidated issue for subscription discussion
- the list of issues, based on previous discussions in Commonalities and subprojects
- separated issues will be created to discuss each topic
- Issue #127 Which error send back when Device Identifier not supported by API Server? includes questions on
Deviceidentification:- when another identifier is present in Access Token
- when multiple contradictory identifiers are provided
- what identifier should be mandatory or optional - Aggregator use case → Should be discussed but we need to have another issue to discuss this.
- Rename the issue to avoid confusion (Ludovic Robert ) and continue to explore UC.
- Jose Luis Urien Pinedo reminded that the device model cames from QoD and was not challenged by other projects.
- Create a new issue about device identifier management/interoperability (diego.gonzalezmartinez ). Mark Cornall agrees on the criticality of this point regarding interoperability.
- Rename the issue to avoid confusion (Ludovic Robert ) and continue to explore UC.
Identity & Consent Management ( Axel Nennker )
- Herbert Damker provided update
- We agreed to concentrate our work on on https://github.com/camaraproject/IdentityAndConsentManagement/pull/121
hot topics: OfflineAccess Offline Access and Refresh Tokens (under review - will got in the profile), Purpose (have a dedicated parameter vs keep it is the scope as of today), Pairwise Pseudonymous Identifiers- Other points will be delayed to future release
- To keep the discussion on PRs more focused we agreed to create new issues for controversial discussion points.
...
- Initial infos by Herbert Damker (as Samuel isn't able to join)
- Release Process
- Release process will contain about 17-22 weeks
- Target to have first meta release in September => we have soon to kick-off
- Use Open Source Summit event in Vienna
- Good timing to have implementation for MWC25
- first milestones will include definition of Commonalities & ICM releases
- more details with a review of the release process and milestones within next TSC
- Lyle Bertz informed the CAMARA board that TMUS is working on a replacement for Marouane Balmakhtar as community release manager
- Release Process
GSMA certification of CAMARA APIs (Mark Cornall Toyeeb Rehman )
- ...
Any Other Topic
- ...
Next Meeting
...