2025-08-21 TSC Minutes

Attendees & Representation

LF Staff: @Casey Cain

Agenda

• 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

  • MCP Whitepaper

• Any Other Topics

Minutes

Review and approval of previous meeting minutes

• Minutes of previous TSC meeting: 2025-07-17 TSC MinutesPreview

  • No comment.

Action Item Review

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

  • Marketing working group is planning a webinar to present/announce new set of APIs for the Fall25 meta-release (to be happen on or after September 19th), see 2025-08-19 Outreach Committee WG MinutesPreview

Governance & Project Management issues

• No specific issue

End User Council (@Nick Venezia)

• Nephio Collaboration opportunity with their upcoming Developer event taking place virtually and in person from Sep 25, 2025 to Sep 26, 2025

  • Register before Sep 15th at: https://linuxfoundation.regfox.com/r6-planning-developer-event-2025

  • Submit Sessions before Sep 5th (open to all): https://lf-networking.atlassian.net/wiki/x/AQCxIw

  • Event Info & Programming Committee: https://lf-networking.atlassian.net/wiki/x/AYCQIw

API Backlog (@Jorge Garcia Hospital)

• No new updates.

Commonalities (@Rafal Artych )

• Public release for Fall25 available: https://github.com/camaraproject/Commonalities/releases/tag/r3.3

  • Supporting documentation of changes: Analysis of Commonalities 0.6.0Preview

  • One relevant change, application in Fall25 is optional but will be suggested in M4 release reviews:
    Shortened Mandatory Description for date-time string format and updated template files

• Some open issues which will discussed in next meetings

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

    • Stick to the properties order status -> code -> message as defined in the guide for now.

  • Improvements of Security sections (proposed by @Axel Nennker ), yet to be discussed in Commonalities:

    • https://github.com/camaraproject/Commonalities/pull/512/files

    • https://github.com/camaraproject/Commonalities/pull/511

• Tooling:

  • Centralized linting prepared and roll-out started (Fall25 API repositories first), see below in Release Management

Identity & Consent Management (@Axel Nennker )

• Next ICM meeting we are going to discuss what to work on for Spring26.

  • Candidates:

    • More than one purpose using https://datatracker.ietf.org/doc/html/rfc9396

    • Better security e.g. PKCE, sender-constraint token e.g. DPoP

• Consent Info, release PR for M4 available: https://github.com/camaraproject/ConsentInfo/pull/33

• ICM release introduced JWT Bearer Flow for case where there is a need a three-legged token from a two-legged flow.

  • ICM should consider to create an implementor and end-user guide with recommendation to use which flows in which scenarios.

Release Management (@Tanja de Groot)

• M3 complete:

  • @Tanja de Groot sent the M3 announcement on Aug 1st.

  • API M3 review status: 45 reviews done

  • 3 APIs will skip Fall 25: NetworkAccessManagement, ClickToDial, SessionInsights

• M4:

  • Review issue template prepared, 12 review issue already created

  • Release PRs from all participating API repositories are expected until Aug 29, 2025

    • Reminder email will be sent tomorrow by @Kevin Smith

• Centralized linting roll-out:

  • PRs created within all API repositories participating within the Fall25 meta-release

    • Currently non-blocking (as linting was before as well)

    • Expectation of Release Management is that all linting errors are addressed outside of the M4 release PR (e.g. use the roll-out PR)

• https://github.com/camaraproject/ReleaseManagement/pull/275

  • The PR introduces a proposal to substantially rework the release workflow in CAMARA and introduce more automation

  • TSC participants are asked to review and provide feedback

MCP Whitepaper (@Jill Lovato , @Nick Venezia )

• Decisions Needed from TSC

  • Approve Structure & Plan: agreement on the proposed outline and timeline to lock in the path to completion.

    • Approved by TSC

  • Confirm need for Lead Author/Editor: A lead author is critically needed to drive the content phase and ensure a consistent narrative voice. Jill is actively sourcing candidates.

    • Need is confirmed, @Jill Lovato should go forward

  • Lock Appendix B Strategy: Agree to finalize the technical code examples and MCP tool mappings just before publication to ensure they are current and reflect the latest releases.

    • Need to have a view on planned content → to be presented in next TSC

    • Also depends on final content of meta-release

Any Other Business

• none

Next Meeting

• Next TSC Meeting will be on September 4th

• Specific agenda topics backlog:

  • Spring 26 outlook (all)

    • Release management improvements

    • Meta-release cadence

  • Feedback from customer engagement (@Nick Venezia)

Action items