2025-03-06 TSC Minutes

Attendees & Representation

LF Staff:

Agenda

• Review and approval of previous meeting minutes

• Action Items Review

• General Topics

  • Governance & project management issues

  • Release Management

  • API Backlog

  • Commonalities

  • Identity & Consent Management

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: 2025-02-20 TSC Minutes

  • no comments

Action Item Review

• See home page Technical Steering Committee for current list of open action items

  • none

Governance & Project Management issues (@Casey Cain @Herbert Damker )

• Update of Wiki structure (@Casey Cain)

  • work in progress, not yet completely done

• Incubating API repositories: update of README.md as part of M4 release PRs

• https://github.com/camaraproject/Governance/issues/181

  • Info: Raised within the CAMARA Board meeting and asked for support

• https://github.com/camaraproject/Governance/issues/184

  • Mail not yet send (to avoid MWC time),

  • Action for @Herbert Damker to send mail to all mailing list with general information, and specific mail to the 32 maintainers/codeowners with disabled 2FA.

Release Management (@Tanja de Groot )

• Spring25 M4

  • All 19 API repositories have submitted their public release PR for M4 review.

  • 11 reviews have been done by release management so far - most of these look OK to be released

  • Target for finalizing the reviews is March 14.

  • Latest API public release publishing targeted for March 19.

  • REMINDER: all APIs that want to release as stable must provide at least one test statement in the issue created for this purpose. It can mention implementation done, but the actual tests may happen after M4. TSC will decide on whether the provided information is sufficient to go for a stable API publication.

• Meta-release Spring25 M5:

  • Target declaration of M5 by TSC on March 20

• Meta-release Fall25

  • Kickoff (M0) to be prepared (March 31).

  • Commonalities and ICM have started work on scope definitions.

  • DedicatedNetworks and SimpleEdgeDiscovery are first candidates.

API Backlog (@Jorge Garcia Hospital)

4 new API proposal(s) from APIBacklog working group.

Note: as “special” TSC meeting due to MWC week, APIs will only get approval this time if enough TSC quorum is reached.

• IoT Network Optimization, supported by TIM.

  • Proposal to enable specific IoT services (e.g. energy saving) for certain set of IoT devices connected to a edge application instance.

  • Original Issue 143; IoT Network Optimization template

  • Comments:

    • none

  • TSC conclusion: approval of TSC will be requested in vote

• Network Health Assessment, supported by China Unicom.

  • Proposal to provide health score for networks (not individual terminal connections).

  • Original Issue 127; Network Health Assessment template

  • Comments:

    • @Jorge Garcia Hospital API should be not be restricted to private networks

    • @Kevin Smith how does it apply to public networks

    • @Tanja de Groot should apply also to “dedicated networks”, so “private” networks in a sense

    • Conclusion: not intended to be applied to the public network

    • Q @Jan Friman difference to ConnectivityInsights

      • A @Jorge Garcia Hospital Connectivity and Session Insight are focused on analysing an specific device connection, while these two proposals are meant for a whole network

  • TSC conclusion: description to be reworked, conclusion next time

• Network Traffic Analysis, supported by China Unicom.

  • Proposal to provide statistical information of the network traffic (not individual terminal connections).

  • Original Issue 128; Network Traffic Analysis template

  • Comments:

    • @Jorge Garcia Hospital API should not be restricted to private networks

    • see discussion above

  • TSC conclusion:description to be reworked, conclusion next time

• Dynamic Predictive Connectivity Data, supported by Telefonica and DT.

  • Proposal to provide network coverage information in certain area/volume for a future period of time, allowing to predict whether network coverage will be available e.g. for a drone on certain sky sector.

  • Original Issue 163; Dynamic Predictive Connectivity Data template

  • Comments:

    • none

  • TSC conclusion: approval of TSC will be requested in vote

• Update on consent URL API proposal:

  • I&CM (minutes) agreed in a way forward for this API proposal, actions pending on repository creation (under ICM working group).

Commonalities (@Rafal Artych )

• Public release of version 0.5.0 published on Feb 21, 2025 available at: https://github.com/camaraproject/Commonalities/tree/r2.3

• https://github.com/camaraproject/Commonalities/issues/423

  • Review of pending issues and propositions of new topics expected before M0.

  • Objective is to align with the proposed timeline for Fall25, to give sub-projects time for alpha-release preparation and proper testing.

• Discussion:

  • @Herbert Damker Is there a discussion to reach a stable version within the next meta-release.

    • @Rafal Artych path to stable should be described, maybe another initial release with few changes, heading towards stable

Identity & Consent Management (@Axel Nennker )

• https://github.com/camaraproject/IdentityAndConsentManagement/issues/275

  • @Axel Nennker reaching stable still difficult, as the current ICM definitions are a sub-set of OIDC and OAuth 2.0, some defined restrictions are under discussion

• https://github.com/camaraproject/IdentityAndConsentManagement/pull/266
  ”Next steps include bring ICM conclusion to TSC to ask for API approval and for repository creation (or subproject management) with ICM as parent group and clarifying release management implications in future updates.”

  • @Herbert Damker proposes to create an API Repository “ConsentInfo” under supervision of the ICM working group:

    • To define API(s) which will allow API consumers to (*):

      • determine the need for Consent: Evaluates whether user Consent is necessary according to the specified parameters and relevant legal requirements.

      • get the current Consent status: If Consent is required, the API returns the current status (e.g., active, revoked, expired...) so the API Consumer can understand the current User's consent status.

      • get a Consent Capture URL: If the user has not provided the necessary Consent, the API supplies an API Provider's Consent capture URL where the user can easily complete the Consent process.

    • The repository follows the rules of API Repositories as defined in https://github.com/camaraproject/Governance/blob/main/ProjectStructureAndRoles.md

    • Maintainers of the API repository will be the maintainers defined in https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/MAINTAINERS.MD

    • Initial code owners will be the code owners of IdentityAndConsentManagement (can be changed by the Working Group)

    • The scope of the API repository will be detailed by writing appropriate user stories

    • The name of the repository can be changed at a later point of time if the APIs are more detailed

    • This proposal replaces https://github.com/camaraproject/APIBacklog/pull/67 (New API Proposal - Consent URL API)

  • Conclusion: The decision of the TSC on the proposal will be taken in a vote

• https://github.com/camaraproject/IdentityAndConsentManagement/pull/268

  • Important issue to get understanding of the consequences of the current definition of CIBA in CAMARA

Any Other Business

• @Kevin Smith Please provide feedback to the tooling activity in https://github.com/camaraproject/tooling/discussions/4

Next Meeting

• Next TSC Meeting will be on Thursday, March 20th, 15:00 CET

  • Main point will be the approval of the Spring25 M5

• Specific agenda topics backlog:

  • ...

  • ... 

Action items