2024-10-03 TSC Minutes

Attendees & Representation

TSC Members attendance to be indicated in the table with an X in the far column.

Representative	Organization	Role
@Herbert Damker	Deutsche Telekom AG	TSC Chair, Active Maintainer
@Shilpa Padgaonkar	Deutsche Telekom AG	Active Maintainer
@Jan Friman	Ericsson	Active Maintainer	x
@Toshi 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
@diego.gonzalezmartinez	Telefonica	Active Maintainer	x
@Jose Luis Urien Pinedo	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
George Glass	TM Forum	TM Forum Representative	x
@Olta Vangjeli	TM Forum	TM Forum Representative	x
@Henry Calvert	GSMA	GSMA Representative
@Mark Cornall	GSMA	GSMA Representative	x

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

Community:

LF Staff:

Communities: @Jorge Garcia Hospital @Pierre Close @Tanja de Groot @Pedro Díez García @Ramit Chawla Ramesh Shanmugasundaram

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.

Antitrust Policy

Review and approval of previous meeting minutes
Action Items Review
General Topics
- Governance & project management issues
- API Backlog
- Commonalities
- Identity & Consent Management
- Release Management
Specific Topics
- Arazzo Specification discussion
Any Other Topics

Minutes

Review and approval of previous meeting minutes

Minutes of previous TSC meeting: 2024-09-19 TSC Minutes
- No comment - Approved

Action Item Review

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

Governance & Project Management issues

TSC Election (@Casey Cain)
- TSC Election process documentation has been updated and is available at: https://lf-camaraproject.atlassian.net/wiki/x/Snje
  - TSC should review and approve
  - Question for @Casey Cain does current TSC member are eligible to be re-elect?
- Please also confirm the list of eligible nominees and voters found here:
  - Maintainers
  - End User Council
- @Casey Cain will confirm TSC approval of the Election process and initiate the nomination period today, Oct 3, 2024
  - The process is approved by TSC
  - Now it’s up to @Casey Cain to trigger election process start.
Wiki migration done
- If you experience oddities or issues, please contact support@camaraproject.org
  - @Toshi Wakayama reports that he has issue with RM WG for the meta-release diagram - @Tanja de Groot explained that it was fixed.
  - Other problems are the links update but fixed in most cases by LF team.
Sandbox/Incubated/Graduated approach
- Draft PR for changes of ProjectCharter and ProjectStructureAndRoles available in https://github.com/camaraproject/Governance/pull/161
  - Reviews and feedback already welcome
- TBD: creation of API-Onboarding-and-Lifecycle document (update of current API-Onboarding.md with the new approach)

API Backlog (@Jorge Garcia Hospital @patricia.serranogonzalez@telefonica.com )

Repository for DedicatedNetwork created (as decided last meeting), TelcoIndex naming still under discussion along supporters.
New API proposals brought to TSC (2):
- See informative message https://lists.camaraproject.org/g/tsc/message/230
- Scope Enhancement for Network info:
  - Supported by Vodafone and DT. Filled template: link. Original issue: 66.
  - Meant for including more information on current Device Status API, including Network Type (e.g.2/34G, 5GNSA/SA, non-3GPP..)
  - Decision: Not for decision, only informative as already agreed in both backlog and subproject. Already included into Device Status group scope, as agreed in issue 143 and PR 8.
- Consent URL API:
  - Supported by Telefonica and KPN. Filled template: link. Original issue: 68. Additional material: link
  - Meant for providing an out-of-band consent gathering mechanism that can be triggered in a separated moment (apart from API authentication phase) and in an arbitrary device (not only the API-targeted device), enhancing current mechanisms tied to Authcode or CIBA token flows.
    - Discussed with ICM work Group in particular to define the relationship between this API & ICM
  - Decision: (not to be treated as no all the affected participants can attend today)

Commonalities (@Rafal Artych @Pedro Díez García )

An issue for the scope version 0.5.0 : Commonalities/issues/273
- All issues from the scope are marked with Spring25 label
- Critical issues are additionally marked with priority label
- Clean up and redesign of API Design Guidelines Commonalities/issues/306 - to be done after implementing changes in the guidelines
Maintenance release (0.4.1) needed to resolve # 301 Broken link to dpv document
- Issue with commonalities version specified in all yaml (still 0.4.0). We are reluctant to update all the yaml as it not really needed.
- We need to solve this problem for future. For example in the yaml we can indicate only the commonalities release major number (without the minor) like r1.

Identity & Consent Management (@Axel Nennker )

Release r0.2.1 which fixes some links has been released. This is a patch only fixing documentation and not requiring any code change !
- @Tanja de Groot suggests that we add in the patch description an indication about code change impact.
Should we include in the yaml the ICM version as we do for Commonalities? and then what about the patch version?

Release Management (@Tanja de Groot @Samuel Adeyemo )

Spring25 M0: the meta-release kick-off can be done in today’s TSC meeting. An email to all mailing list will be sent to inform the community. The meta-release plan is available here: Meta-release Spring25.
- M0 is declared by the TSC Oct 3, 2024
Spring25 M1: Due to delays in the Fall24 meta-release, the M1 date is slightly impacted and shifted from Oct 15th to Oct 31st.
- Exceptionally, the M1 will not yet have an alpha release available for Commonalities and ICM, but the relevant set of PRs covering the scope of the upcoming release shall be made available for Sub Project team review as follows:
  - PRs for critical issues must be created by Oct 15th (not necessarily merged)
  - PRs for other issues must be created by Oct 31st (not necessarily merged)
  - Alpha releases will be created as fast as possible after that and an M1 update announcement shall be sent at that point.
Info for Sub Projects: the API release tracker content for Spring25 is being updated, so please DO NOT create new API release trackers for Spring25 yet. Fall24 API release trackers SHALL NOT be copied. The new version will be available shortly.
Fall24 M6: The date is slightly delayed. Feedback is being integrated in the process and artefacts. This has no impact on the Spring25 content progress and should be finished latest by Oct 31st.

Arazzo Specification discussion (@Kevin Smith)

An introduction to the recently-released Open API Initiative ‘Arazzo’ specification, for TSC consideration:
- Question from @Eric Murray to use Arazzo to improve user story (for example for QoD)
- Question from @Mark Cornall about difference with Cucumber/Gherkin/Postman
  - Probably the industry will follow this as it comes from OpenAPI so we can expect some update from Postman
  - Worth to explore Arazzo for CAMARA test definition.
- Comment from @Mark Cornall about fraud UC where we can trigger several APIs but do we want to “camarize” the workflow?
  - There are domains where it make sense like for QoD, Carrier Billing, OTP where severals API call are involved.
- Discussion should continue on Commonalities (@Kevin Smith will create an issue there to continue the discussion….)

CAMARA Project