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 | |
Telefónica | Backlog Chair | 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 |
...
Community: Tanja de Groot Rafal Artych Lazlo Suto Markus Kümmerle Ravi Shekar Nick Venezia Pierre Close Toyeeb Rehman Aleksandar Brankovic Ricardo Serrano Gutierrez
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. |
...
- Proposal owner asked to postpone the two proposals from https://lists.camaraproject.org/g/tsc/message/139 to next TSC.
- Need additional work to harmonize both proposal.
- Info about Network Slice Booking (Herbert):
- Thorsten Lohmar (Ericsson) and Ricardo Serrano (Telefonica) joining as additional maintainers (cf. https://github.com/camaraproject/NetworkSliceBooking/pull/1)
- First regular meeting will be on March 15th, 16:30 Beijing Time (8:30 UTC, 9:30 CET), details will be on wiki page of Network Slice Booking
- Maintainer will be nominated by the TSC.
Commonalities (Rafal Artych )
- 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
- 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
Device
identification:- when another identifier is present in Access Token
- when multiple contradictory identifiers are provided
- what identifier should be mandatory or optional - Aggregator use case
...
- We agreed to concentrate our work on https://github.com/camaraproject/IdentityAndConsentManagement/pull/121
hot topics: OfflineAccess and Refresh Tokens, Purpose, Pairwise Pseudonymous Identifiers - 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
- 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
...