2026-01-15 TSC Minutes

LF Staff:

• 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

• Any Other Topics

• Minutes of previous TSC meeting: 2025-12-18 TSC MinutesPreview

  • approved

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

  • No incomplete tasks

• EUC Representatives (@Casey Cain)

  • @Doug Makishima hasn’t run for the election for personal reasons but is available now again. There were no objections from TSC members, so we are welcome him back to the TSC as the third EUC representative.

• Zulip migration (@Casey Cain )

  • Channels exist for the working groups. Please move the discussion from Slack over to Zulip, and open topics in the existing channels as needed.

  • Sub Projects should contact support@camaraproject.org in case of any needs for their communication. Independent Sandboxes should consider using the existing channels by opening “topics” within the existing channels (e.g. #CAMARA_Discussions).

  • Join Zulip here: https://linuxfoundation.zulipchat.com/join/t4rkxuxcviaac6igbonx6v4h/

• MCP Whitepaper announcement: https://camaraproject.org/2026/01/12/camara-charts-a-path-for-network-aware-ai-applications-with-mcp/

  • Presented by Markus at the Unthinkable Lab event (London) - well received.

• Proposal for discussion: https://github.com/camaraproject/Governance/issues/210

  • Issue #210 presented by Herbert.

  • Security and Consent are important topics - proposed to be covered by ICM

  • Start small with Phase 0 for a set of pilot APIs (3 to 4 needed) - proposal can be changed as needed.

  • This pilot work should help guide API design guidelines extensions for MCP (expected to be not too hard)

  • TSC to decide on open points by next meeting. Please use the above issue #210 for discussion:

    • Agree on final set of pilot APIs

    • is the MCP activity still needed in TSC

    • Call for “sponsors” for the MCP workstreams to drive the work. Reporting to TSC will remain through the normal team reporting. Sponsors are expected to drive the work in the respective teams.

  • it is proposed to close the previous issue Governance #203 and use #210 for the next steps [Update: done]

  • The discussion in Commonalities (#554) can be use as a basis for creating supporting issues in Commonalities

• ReleaseManagement:https://github.com/camaraproject/ReleaseManagement/issues/357

  • Last steps of preparation in work, roll-out first to Spring26 API candidates (see below)

  • This rollout establishes the data foundation (release-plan.yaml in all repos) that will allow to replace the manual trackers within Wiki. It will be also the base for the automated release creation.

• There are no new APIs for TSC review.

• API Repositories onboarded: ConsentManagement, InHomeDeviceManagement, RainfallIntensity

• Unified Clean-up Process for Inactive Onboarding Trackers and Repositories: For already evaluated once we’ve created issues in APIBacklog:

  • #283 - [Repository Transition → Archived]: HomeDevicesQoD,

  • #284 - [Repository Transition → Archived]: SiteToCloudVPN,

  • #285 - [Repository Transition → Archived]: ShortMessageService

    • Status: The owners/maintainers were notified on December 4 via a Github issue, and a period of four weeks has been given for each member to raise objections, propose a specific evolution plan, or assume ownership of the API. No comments have been received for these APIs, so the recommendation is to transition to archiving them.

    • Decision: TSC supports the proposed archiving. The issues are to be closed after the archiving is done.

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

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

  • PR with sequence diagrams for both the simple and advanced flow variants under preparation

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

  • Presentation available: https://github.com/user-attachments/files/24644505/CAMARA_GroupManagementAPI-December2025.pdf

  • This is a medium/longer term activity (not for Spring26). It is to be discussed if a specific API is created or if to use a template approach and dedicated API updates. The latter could provide more flexibility.

    NEWhttps://github.com/camaraproject/Commonalities/issues/572 - new related issue proposing developing guidelines for:

    • Collections used for listing/pagination (representation concern, not a consistency boundary)

    • Invariant-bearing Resource Groups (true consistency boundaries where cross-resource invariants must hold)

    • Batch/bulk request patterns (single request to operate on many independent resources without persistent group semantics)

• ICM Spring26 meta-release status. Current progress stands at 75% completion after adding the new issue #338 to the scope as per WG decision. Significant milestones include the closure of the DPoP support strengthening issue (https://github.com/camaraproject/IdentityAndConsentManagement/issues/318) and the upcoming January 31 deadline for the release candidate. Remaining work focuses on Rich Authorization Requests (RAR) and Profile alignment with OAuth 2.1.

  • The group reached a consensus to explicitly document the implicit trust assumptions when using phone numbers as sub claims in the JWT Bearer flow to improve security clarity (Issue #338). Included in Spring26 scope.

  • Additionally, discussions started regarding a potential audience (aud) injection attack vulnerability (https://github.com/camaraproject/IdentityAndConsentManagement/issues/340) and how to handle non-backwards compatible security fixes in ICM within the release management framework (it may need to be addressed as part of ReleaseManagement/issues/351).

• OAuth 2.0 Token Exchange (Issue #337): This remains an open and debated topic. Although potential benefits have been identified, concerns remain about overlap with existing CAMARA flows, the risk that additional optional features will impact interoperability, and whether there is a real business need for it.

• Consent Info API evolution / Controlled Consent Capture Delegation.

  • Consent Management API: A new independent repository has been successfully established for the Consent Management API to handle Controlled Consent Capture Delegation.

    • As with the Consent Info API, this API will be under ICM supervision.

    • Announced in Zulip #camara-wg-icm > Consent Management API and in the ICM mailing list.

    • The initial API draft and updated README have been merged, and administrative setup (codeowners, initial tasks) is complete.

  • ConsentInfo API: The callback URL feature has been merged into the main branch, and the repository is preparing for the v0.2.0 release.

• Further details of the above items can be found at 2026-01-14 ICM MinutesPreview

• Spring26 meta-release (Spring26 meta-releasePreview )

• M2 (Jan 31)

• Target date is Jan 31, 2026 for the release-candidates of Commonalities & ICM.

• Both are well on track (81 and 75% respectively) to deliver their planned release-candidate for the M2 milestone.

• M3 (Jan 31)

  • Target date is Jan 31, 2026 for Spring APIs that have been granted participation:

    • Spring 26 participation: SessionInsights #350 

    • Spring26 participation: HighThroughputElasticNetworks #349

    • Spring26 participation: IoTSIMFraudPrevention #348 

    • Spring26 participation: NetworkInsights #344

    • Spring26 participation: ClickToDial #343 

    • Spring26 participation: Network Slice Booking #341

  • 1 API (NetworkSlideBooking) has submitted a release review request

• These Spring26 APIs will be the first candidates for the roll-out of the automated release process.

  • We need to finalize the new documentation ASAP.

• Fall26 meta-release  (Sync26 meta-release (ex-Fall26)Preview )

  Open

  

   

  • M0 (Jan 15): kick-off to be done on today’s TSC

  • All API Sub Projects can start to prepare their scope issue for Fall26.

    • they shall start using the Commonalities and ICM Spring26 release-candidate once available (M2).

  • M1 (Apr 30): API alpha versions for Fall26

  • Fall26 will be fully supported by the automated release process based on the release metadata.

• None

• None

• Next TSC Meeting will be on February, 5th, 09:00 UTC (10:00 CET / 01:00 PT)

• Specific agenda topics backlog:

  • Presentation by Nick on collaboration opportunities with other LFN projects