General Updates

Working Groups

Sub Projects & Sandbox API Repositories

• 1359 people from 483 companies have joined CAMARA

• Logos see landscape

• New Premier / General Member: Hayo

• New Associate Member:

• New Participating Organizations: Vonage

Updated: Jun 9, 2026 

@Markus Kümmerle 

• If you require support or meeting changes, please send an email to support@camaraproject.org

• Landscape Enrichment Update

  • The CAMARA Ecosystem Landscape enrichment effort is complete. Updates to the landscape are pending a creative services request to finalize the website changes.

  • If your organization has additional updates to your listing, you can submit them by opening a pull request at https://github.com/camaraproject/camara-landscape or sending your request to adm@camaraproject.org.

• Reminder, please use support@camaraproject.org for help with LF adminstrative tasks, and https://support.linuxfoundation.org for LF IT / Infrastructure Support

• A draft new All Hands template is in the works to improve the collection of project updates. Expect more information prior to the next all hands.

• Marketing updates

  • New whitepaper: “CAMARA APIs Functional Differences”

  • TM Forum’s DTW Ignite (June 23-25) Copenhagen: CAMARA (Markus, Herbert, and Jill) will join with a booth adjacent to GSMA Open Gateway

  • Outreach team has reviewed the API descriptions  - there are are some issues with the visuals that accompany the descriptions, so  we're now in the process of both creating instructions on how to create a better visual, and also getting help from LF Creative Services on some visual options (like icons).

  • Open Source Summit Europe

    • CFP Deadline: Wednesday, 24 June at 23:59 CEST (UTC +2) / 14:59 PDT (UTC -7)

Updated Jun 11, 2026 

@Casey Cain @Evan Harrison 

• Slack-to-Zulip migration:

  • Please join Zulip if you haven't already

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

    • Login Information: You'll use Linux Foundation Single Sign-On (SSO) to access Zulip. If you don't already have a Linux Foundation account, create one at https://openprofile.dev

      • Need Help?

      • Zulip Help Center: https://linuxfoundation.zulipchat.com/help/

      • Linux Foundation SSO Help: https://docs.linuxfoundation.org/lfx/sso/sign-in-with-sso

      • Linux Foundation Support: support@camaraproject.org

      • If you don't hear back within a day, feel free to ping Casey or Evan directly in the #camara-support channel on Zulip.

        We look forward to seeing you on Zulip!

• Release automation roll-out:

  • Release Automation and Validation roll-out is done, see below.

  • All releases going forward should be done with the new process.

• MCP Enablement Program:

  • TSC: MCP Enablement Program – Phase 0

  • Demo from Orange presented on Mar 23, 2026 Recording

  • Next session on Apr 20, 2026 15:00 UTC

  • Register via LFX Meetings or the Community Calendar

  • Contributors beyond regular Commonalities and ICM participants are explicitly welcome, especially MCP experts from participating organization

Updated Apr 9, 2026

@Herbert Damker 

• …

Updated: Mar 11, 2025 

@massimiliano.troiani
@Nick Venezia

• Marketing materials:

  • CAMARA Onepager and the CAMARA Presentation are updated

  • Whitepaper “CAMARA APIs: Functional Differences“ is published

• Events

  • Recent:

    • API Days Singapore

    • AECC Member Summit Gothenburg

    • Network X Dallas

    • DSC London

  • Upcoming:

    • Vivatech - Anthony

    • DTW Copenhagen - Herbert & Markus

  • Focus: Show progress in CAMARA and emphasize important tasks in the ecosystem

  • 2026 planning: See list of events

• Website:

  • API descriptions published on website, are updated with Spring26 meta release (3 APIs)

  • Upcoming:

    • Quality check for text / pictures: Outreach team is in progress to review (and opens issues in the API repos)

      • Findings in API description, Use Cases, Benefits: Update API description wiki page and open issue in Marketing repo that Outreach team updates the website

      • Findings in picture: Propose instructions how to create a attractive visual, put it in the wiki page too below the existing visual. Outreach team will ask LF creative team to create nice visuals.

      • Findings in right column (with links): Outreach team will correct the findings

  • We plan to remove the Participating Organizations from the CAMARA home page and create a new sub page showing all member and Participating Organization logos in a ecosystem role structure

Updated: Jun 9, 2026 

@Markus Kümmerle 

@Jill Lovato

Spring26 meta-release (Spring26 meta-release)

• The Spring26 meta-release (M5) was declared this week.

• Spring26 ICM and Commonalities public releases are available (M4 May 21):

  • ICM r4.2 (public release of v0.5.0)

  • Commonalities r4.3 (public release of v0.8.0)

  • Delays on M5 was due to the introduction in Commonalities of

    • the new, automated release process removing tedious task from the API Sub Projects

    • the new automated validation tools improving the quality of the API releases

    • the bundling feature, allowing APIs to reference Commonalities- provided assets and use automated resolution to deliver self-contained API definitions without copy/paste

• Spring26 APIs

  • Due to the transition to the new process, exceptionally the Spring26 meta-release did include 3 APIs (2 repositories) which have been announced on the CAMARA website by the Marketing team:

    • ClickToDial r1.4

    • NetworkSliceBooking r2.3

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

  • In line with the new process, the Spring26 meta-release provides the Commonalities and ICM releases for the Sync26 APIs.

  • All Fall25 APIs are expected to participate in Sync26

    • NOTE: All new (initial) APIs are required to first do a release on the Independent track (TSC decision on March 19), before participating in a meta-release.

  • Sync26 M1 (May 31) is passed

  • DEADLINE: June 18 for Sync26 participation

    • We raise the attention to the API Sub Projects that Sync26 participation needs to be declare latest by June 18 (by updating the release-plan.yaml which is a small effort).

  • Sync26 M3 (June 30): APIs are expected to have a RC snapshot ready for review

  • Sync26 participation rules

    • APIs must use the new automated release process

    • APIs must use the bundling mechanism (external $ref to CAMARA common artefacts)

    • APIs must document unresolved Validation Warnings

    • A more detailed email will be sent to codeowners

Automation of release process

• Progress of the adoption of the automated release process:

  • 51 of 62 APIs have been onboarded (validation & automation active); 11 have the onboarding PR open

• The Release Management & tooling support for PR validation and bundling is rolled out

  • Validation v1 (rc) replaces the current Megalinter validation workflow, being faster and more comprehensive. It supports

    • Commonalities r3.4 (Fall25, v0.6.1) with the related Spectral rule set

    • Commonalities r4.3 (Spring26, v0.8.0) with an extended rule set

      • the new OWASP security rules will create only warnings yet (until Signal27)

      • referencing definitions in CAMARA_common.yaml is supported (and recommended)

• ICM lifecycle and API compatibility governance

  • Proposal is available for review here: ICM lifecycle and API compatibility governance - ReleaseManagement PR #545

• Details on the automated release process for the API teams.

  • PPT: 2026-03-05_CAMARA_Automated_Release_Process_Update.pptx

  • Recording: 2026-03-05 Automated Release Process Update

• All documentation is here: ReleaseManagement/documentation (note the Wiki documentation still needs to be updated).

Updated: Jun 11, 2026 

• @Tanja De Groot (Nokia) 

Commonalities Spring26 status

• The Spring26 Public Release (0.8.0 version) is available at: Commonalities Release 4.3 (published on May 22, 2026).

  • Main features/topics covered

    • Enhancements in Error 409 codes

    • Business Level outcome guidance

    • Improvement in event notifications securization. Defined PRIVATE_KEY_JWT mechanism to allow for requesting a new access token when current one used in the communication is expired.

    • OWASP API Security Top 10 applicability for API design guidelines (i.e. enhancements in stringand integer formats) and Linting rules

    • Update of pagination guidelines

    • Refactor of Commonatilites artifacts folder driven by the new model of Specs Bundling and enhancements in Release Automation workflows Commonalities Consumption and Bundling Design

• Wiki page (scope analysis): Analysis of Commonalities 0.8.0

  • Changes in rc.1 no highlighted

  • Changes in rc.2 are highlighted in green

  • Changes in public release are highlighted in blue

Next work

• Following the release, minor issues have been identified:

  • docs: minor grammar issue in 'Identifying the device form the access token' · Issue #636 · camaraproject/Commonalities

  • sinkCredential in response schemas contradicts Event Guide §2.2.3 · Issue #638 · camaraproject/Commonalities

  • docs: minor aligment in `accessTokenType` attribute description · Issue #639 · camaraproject/Commonalities

  • Editorial corrections and alignments in Spring26 testing Artifacts · Issue #641 · camaraproject/Commonalities

A patch release will be considered once additional issues are discovered.

• Documents

  • Live table for API backlog available here. Updated version including new information.

  • Accepted API proposals stored here. 

• Discussion

  • New APIs Proposals under discussion: 

    • User Experience Insights #315: Enable AF/application developers to subscribe to real-time notifications when a user’s network experience degrades or changes significantly, leveraging NWDAF capabilities exposed through NEF.New Scope Enhancements:

    • Support pre-deployment viability discovery in OED #311: Introduce an Edge Deployment Planning API to assess rollout feasibility before deployment, allowing developers to identify viable edge zones, available operators or cloud providers, and estimated performance metrics for a target area and application profile.

• Other topics:

  • (API Backlog Management) Proposal to refresh API Backlog CODEOWNERS and MAINTAINERS based on sustained participation #307: The API Backlog CODEOWNERS and MAINTAINERS lists were updated to reflect sustained participation and distribute review work more effectively. The final CODEOWNERS are @eric-murray, @albertoramosmonagas, @FrimanJan, and @caubut-charter. The Maintainers list now includes Christopher Aubut, Noel Wirzius, Mark Cornall, Reg Cox, Gilles Renoux, Jorge Garcia, Alberto Ramos, Eric Murray, and Jan Friman.

    (API Backlog Management) Strengthen API Backlog templates to require explicit CAMARA scope alignment #308: New proposals often reach the API Backlog without a clear explanation of how they align with CAMARA scope. Although scope validation is already required by the Project Charter and onboarding process, the templates do not explicitly request this justification, causing scope-fit discussions to happen too late during backlog reviews.

  • (Onboarding Tracker) ConnectivityQualityManagement repository 317: The Connectivity Quality Management repository has been created and is available at camaraproject/ConnectivityQualityManagement. It is being used for cross-API collaboration on a whitepaper that explains the portfolio to a non-telco audience.

  • (Onboarding Tracker) MCPEnablement_PI1 #318: Create a repository for Orange’s MCP server provider implementation under the CAMARA MCP Enablement initiative. It will not define a new CAMARA API or normative MCP specification. The README must document its scope, capabilities, limitations, and relationship with other CAMARA MCP activities.

  • (API Backlog Management) Split qos-profiles out of the QualityOnDemand repository #319: Create a dedicated QoSProfiles repository so the stable qos-profiles API can evolve independently from QualityOnDemand. The new repository will start from the Fall25 release, inherit the existing Codeowners and Maintainers, and require a new onboarding tracker.

Updated: Jun 11, 2026 

@Jorge Garcia Hospital @Alberto Ramos Monaga

• ICM Spring26 meta-release status.

  • Spring26 The Spring26 Public Release r4.2 (0.5.0 version) is available at https://github.com/camaraproject/IdentityAndConsentManagement/tree/r4.2

  • Active issues/discussions:

    • PRIORITY https://github.com/camaraproject/ReleaseManagement/pull/545

      • ICM lifecycle - open issues (WIP)

      • Proposal remains under review; all participants are requested to provide feedback.

      • Open issues to be reviewed offline and commented via the PR/wiki.

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

      • Fixed by https://github.com/camaraproject/IdentityAndConsentManagement/pull/359

      • This change requires coordination with Commonalities to update the corresponding artifacts.

  • New issues/discussions:

    • NEW https://github.com/camaraproject/IdentityAndConsentManagement/issues/360

  • Consent Info API

    • There are no relevant updates regarding this API. The repository is quiet

  • Consent Management API

    • NEW v0.1.0-rc.1 The first API release candidate is now available at https://github.com/camaraproject/ConsentManagement/releases/tag/r1.1

      • https://github.com/camaraproject/ConsentManagement/issues/17 ==> CLOSED

        • Fixed by https://github.com/camaraproject/ConsentManagement/pull/29 ==> MERGED

          • This could serve as a useful reference for other API sub-projects on how to adapt the API spec to the Spring26 Commonalities.

  • Further details of the above items can be found at 2026-06-03 ICM Minutes

Updated: Jun 10, 2026

@Jesús Peña García-Oliva

Updated: May 4, 2026 

@fabrizio moggio