2023-12-07 TSC Minutes

Attendees & Representation

TSC Members may indicate their attendance by marking an X in the column to the right.

Community members may use @name tag to mark their attendance below the table. 

LF Staff:

Community: Dinesh Muthukumar, Pierre Close, Rafal Artych, Nick OtterPilot, Rajneesh, Ramit Chawla, Olta Vangjeli, Ming Hui Foo, Ramesh Shanmugasundaram, Fan Yang

Agenda

• Roll Call
• Action Items Review
• Agenda Bashing
• General Topics
  • Commonalities
  • Identity & Consent Management
  • API Backlog
  • Release Management
• Any Other Topics
  • Meetings on Dec 21st and Jan 4th
  • Disclaimer on all Working group API on page Camara Project – Linux Foundation Project

Minutes

Action Item Review

Commonalities

• Update given by Rafal
• Important updates:
  • Design guidelines has been updated for CloudEvents feedbacks & X-Correlator Management
  • notification-as-acloud-event.yaml has been also merged. This is a generic openAPI yaml of CAMARA notification (Commonalities/artifacts/notification-as-cloud-event.yaml at main · camaraproject/Commonalities (github.com))
  • Release v0.2.0 of CAMARA documents and artifacts to be available soon
• Call for action (mains)
  • Alignment of Device schema across all our API Alignment of Device schema · Issue #105 · camaraproject/Commonalities (github.com)
  • Need to move forward on the Test Case as this is the major missing asset in a lot of API. Community needs to provide feedbacks on Test definitions - implementations guidelines and artifacts · Issue #94 · camaraproject/Commonalities (github.com)

Identity & Consent Management

• 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
• 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 agreements
    • AGREEMENT: OpenId Connect profiles to be defined in CAMARA and adopted by OGW

API Backlog

• New API Proposals as distributed and explained by JOSE ANTONIO ORDOÑEZ LUCENA  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
• Short presentation to explain the differences between "Region User Count" and "Dynamic People Density Information":
  • 

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

AOB

• AGREEMENT: Future meetings will be 90 minutes
• Next steps regarding LF tool use (see comment from Shilpa below)
  • Information and education sessions to start in January
  • Wiki already available for sub-project minutes
• TSC meetings on Dec 21st and Jan 4th  - please vote here:
  • Should we have or have not a TSC meeting on Dec 21st, 2023?
    • Will be kept.
  • Should we have or have not a TSC meeting on Jan 4th, 2024?
    • Will be cancelled.
• Have a similar disclaimer on all Working group API on page Camara Project – Linux Foundation Project
  • As of now depending on the API there is "restrictive" disclaimer (see simswap here Sim Swap – Camara Project) while for other there is nothing (see device location here: Device Location – Camara Project)
  • Could be tackled by Commonalities ? 

Action items