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 | x |
| Adnan Saleem | Radisys | EUC Representative | |
Doug Makishima | Summit Tech | EUC Representative | x |
| Diego González Martínez | Telefonica | Active Maintainer | x |
| Jose Luis Urien | Telefónica | Active Maintainer | |
| Mahesh Chapalamadugu | Verizon | EUC Representative | |
| Eric Murray | Vodafone | TSC Deputy Chair | x |
| Kevin Smith | Vodafone | Active Maintainer | x |
| Chris Howell | Vonage | Active Maintainer | |
| George Glass | TM Forum | TM Form Representative | |
| Henry Calvert | GSMA | GSMA Representative | x |
...
- Update given by Diego
- Important updates:
- Documentation update with securitySchemes final agreement.
- Issue: https://github.com/camaraproject/IdentityAndConsentManagement/issues/57. Text already agreed, scope/solution chosen will not be rediscussed
- PR: https://github.com/camaraproject/IdentityAndConsentManagement/pull/93. Comment by Eric to be considered as an addition, Client Credentials have to appear as an option
- Release 0.1.0 to be made available once former point is merged
- Documentation update with securitySchemes final agreement.
- See comment from Shilpa below about relation of CAMARA and GSMA OGW, e.g. lack of free access to GSMA GitHub
- Documentation is being duplicated between GSMA OGW and CAMARA. OGW github is restricted access.
- Herbert: Documentation needs to be public as APIs may be used outside of OGW
- Diego: OGW documentation will eventually be public. Our preference is to have Flows and Access Control in GSMA as are OGW specific, while APIs are potentially for OGW and not for OGW
- Shilpa: CAMARA documentation should not reference private OGW documentation
- Henry: Need to better define scope of OGW and CAMARA to avoid conflicts. Identity & Consent should be in CAMARA. Interconnection and routing should remain in OGW.
- Where should OpenId Connect "profiles" be defined? OGW or CAMARA?
- Herbert: OpenId Connect profiles should remain in CAMARA
- Shilpa: Even OGW profiles should be defined within CAMARA
- Henry: OGW agree to adopt CAMARA commonalities / identity & consent agreementsDiego: As OIDC will be OGW specific it better fits in GSMA. Anyway this should be decided related to resolution to duplication of information.
- AGREEMENT: OpenId Connect profiles to be defined in CAMARA and adopted by OGW
- Documentation is being duplicated between GSMA OGW and CAMARA. OGW github is restricted access.
...
- New API Proposals as distributed and explained by joseantonio.ordonezlucena in https://lists.camaraproject.org/g/tsc/message/79
- SMS API
- TSC approve the proposal, but backlog WG need to finalise naming & maintainers before creating new sub-project
- Region User Count
- TSC approve the proposal. New sub-project to be created "RegionUserCount".
- Dynamic People Density Information
- TSC approve the proposal, but needs further discussion in Backlog WG
- ConnectivityInsights is not the right sub-project for this. Neither is DeviceLocation. Needs new sub-project.
- API should be renamed, as current proposal is confusing. Kevin suggests "Population Density Prediction".
- Device Visit Location
- Not yet approved
- This API can only be implemented in certain countries, as some states (e.g. EU) prohibit storing of the required data
- Legal situation needs to be clarified. GSMA to provide guidance on best practice.
- Home Location Verification
- Not yet approved
- Toshi: Does not think KYC can accommodate this API, and does not think it anyway fits that sub-project
- Agreed that KnowYourCustomer is not the correct sub-project for this
- Kevin: API is not really verifying customer's home location, so name is misleading
- Needs further discussion in API Backlog WG
- SMS API
- Short presentation to explain the differences between "Region User Count" and "Dynamic People Density Information":
View file name TSC - drop3 density & user count APIs.pptx height 150
Release Management
- All release management issues have now been moved from Commonalities into the new Release Management sub-project
- Feedback from Release Management Trainings?
- Release Cadence & potential events for announcements in 2024
- Request from Governance Board to TSC
...