DRAFT AGENDA
Attendees & Representation
...
| Representative | Organization | Role | |
|---|---|---|---|
| Herbert Damker | Deutsche Telekom AG | TSC Chair, Active Maintainer | x |
| Shilpa Padgaonkar | Deutsche Telekom AG | Active Maintainer | x |
| Jan Friman | Ericsson | Active Maintainer | x |
| Toshi (Toshiyasu) Wakayama | KDDI | Active Maintainer | x |
| Ludovic Robert | Orange | TSC Deputy Chair, Active Maintainer | |
| Adnan Saleem | Radisys | EUC Representative | |
Doug Makishima | Summit Tech | EUC Representative | |
| Diego González Martínez | Telefonica | Active Maintainer | x |
| Jose Luis Urien | Telefónica | Active Maintainer | x |
| Mahesh Chapalamadugu | Verizon | EUC Representative | |
| Eric Murray | Vodafone | TSC Deputy Chair | x |
| Kevin Smith | Vodafone | Active Maintainer | x |
| Chris Howell | Vonage | Active Maintainer | x |
| George Glass | TM Forum | TM Form Representative | |
| Henry Calvert | GSMA | GSMA Representative | x |
...
David del Val took over the role of Juan Carlos García as voting representative of Telefonica
- We have now two nominated Community Release Managers
- Samuel Adeyemo nominated by Nokia
- Marouane Balmakhtar nominated by T-Mobile US
- Markus Kümmerle elected as Chair of the CAMARA Outreach Committee
- formerly known as Marketing Working Group ... now merged
...
- Update on important topics and request of actions
- Update from Rafal:
- Preparing next release (v0.3) with linting rules and API testing guidelines (see last meeting minutes)
- Discussion about error response format:
- Current format defined in Design Guidelines, a change would break all API following this format
Proposal to use RFC 9457 Problem Details for HTTP APIs for error responses
- Lot of examples (e.g. from cloud providers) of different error response schema
- Question: keep current definition or change towards RFC based schema
- Proposal: request company opinions within the issue. If no consensus raise it to TSC for a vote.
- Eric will close the current issue and open a new one with the summary of current positions. There comments should be raised.
- Issue #128 API Design : UNAUTHENTICATED 401 API format issues with some gateway implementations, e.g. having no control over error schema
...
- Two Release Managers nominated and onboarded, see above
- Weekly working group meetings (see Release Working Group Minutes)
- Work on release process started (see CAMARA Release Process)
GSMA certification of CAMARA APIs (Mark Cornall , tbc)
- [Placeholder for presentation from Mark]
- GSMA would like a global standard, which includes authorisation flow even if local regulation allows alternative authorisation flows
- Chris requested extended discussion on common testing issues at next meeting
...