General Updates

Working Groups

Sub Projects & Sandbox API Repositories

• 1357 people from 483 companies have joined CAMARA

• Logos see landscape

• New Premier / General Member: FocusData

• New Associate Member:

• New Participating Organizations:

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)

Casey Cain Evan Harrison 

• Release automation roll-out & new validation:

  • One of the main activity driven both within Commonalities (guidelines, artifacts, templates) and Release Management (process, tooling, workflows)

  • Status: quite stable v1-rc of Release Automation and new Validation workflow, enabled in all API repositories

  • Previous pr-validation v0 disabled and no longer supported, workflows can be deleted (or will be later in a bulk actions)

  • Main change for API codeowners:

    • Common components (schema, parameters, headers, responses) can and should be referenced from the code/common/CAMARA_*_common.yaml files in the API repository

    • Full support of Commonalities 0.8.0 (r4.3 for now, r4.4 in preparation)

    • Warnings are more visible and MUST be addressed (see rules for Sync26 below)

• End User Councial:

  • CAMARA Board is working on a new setup, most probably under supervision of the Board, not longer combined with the TSC itself (similar concept like CNCF)

Herbert Damker 

• …

massimiliano.troiani
Nick Venezia

• Marketing materials:

  • CAMARA Onepager and CAMARA Presentation in progress to be updated

• Events

  • Recent:

    • Vivatech - Anthony

    • DTW Copenhagen - Herbert & Markus

  • Upcoming:

    • CASA26 Amsterdam

    • FutureNet Asia Singapore

    • API Days London

    • LF OSS Prague

    • NetworkX Vienna

  • 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

  • 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

Markus Kümmerle 

Jill Lovato

Spring26 meta-release (Spring26 meta-release)

• The Spring26 meta-release was closed (M6) on June 23

• Spring26 meta-release content:

  • ICM r4.2 (v0.5.0)

  • Commonalities r4.3 (v0.8.0)

  • Release Management r4.1 (v0.5.0)

  • APIs (exceptionally):

    • ClickToDial r1.4

    • NetworkSliceBooking r2.3

• This meta-release introduces many new features to facilitate API releases:

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

  • the 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

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

  • The Spring26 meta-release provides the Commonalities and ICM releases for the Sync26 APIs.

  • Most Fall25 APIs are participating in Sync26

    • Today 58 APIs across 36 repositories - 22 in snapshot state

    • 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

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

  • Sync26 participation rules for APIs:

    • Use the new automated release process

    • Use the bundling mechanism (external $ref to CAMARA common artefacts)

    • Resolve all Validation Errors

    • Resolve all Validation Warnings (may have some unresolved Validation Warnings when documented with justification for later resolution)

    • May have some unresolved Validation Hints when justified

Automated validation and release process

• The automated release process has been onboarded to all repositories. Adoption is now complete.

• The Validation v1 (rc) process has replaced the previous Megalinter validation workflow (v0), 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 (until Signal27). Exceptionally, the related changes are not considered breaking changes for the API

    • referencing definitions in CAMARA_common.yaml is supported and recommended for Sync26 APIs

• ICM lifecycle and API compatibility governance

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

Documentation links

• PPT: 2026-03-05_CAMARA_Automated_Release_Process_Update.pptx

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

• ReleaseManagement/documentation (note the Wiki documentation still needs to be updated).

• Tanja de Groot

• The Spring26 Public Release (r4.3) is available - to be used in API release plans

• Following the release, new issues have been identified (mainly releated to common artifacts consumption in API definitions):

  • https://github.com/camaraproject/Commonalities/issues/663 - Recommendation: use local Error Response definitions - the CAMARA_common.yaml Error Responses can be referenced with particular care to avoid altering in the API definition.

  • https://github.com/camaraproject/Commonalities/issues/659- Recommendation for subscription APIs: use local Config schema definition with API-specific subscriptionDetail.

• MCP Enablement

  • https://github.com/camaraproject/Commonalities/issues/661 - the direction for MCP Enablement in API definitions (to be used by pilot APIs)

  • Break-out sessions suspended for holiday period - topic will be covered within regular Commonalities meetings

• Documents

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

  • Accepted API proposals stored here. 

• Discussion

  • New APIs Proposals under discussion: 

    • Eligibility-Info/Pre-flight API #323 (AT&T, T-Mobile, Verizon): Pre-check mechanism before initiating a CAMARA API flow. The consumer submits the subscriber identifier, requested scopes and purpose; receives a per-scope eligibility decision. Avoids authorization calls that would fail due to unsupported subscriber, provider, or scope/purpose combinations.

    • Network Outage API #327 (BT): Enables devices, apps, and support channels to check whether a customer is affected by a known mobile network outage, service degradation, or planned maintenance event.

• Other topics:

  • (Onboarding Tracker) NetworkServiceAreas #328: CQM Sub Project proposes splitting dedicated-network-areas into its own repo (NetworkServiceAreas, service-areas) to address the common need for network service area discovery across APIs. DedicatedNetworks retains the three interdependent APIs (dedicated-network, dedicated-network-accesses, dedicated-network-profiles).

  • (Onboarding Tracker) Create QoSProfiles repository by splitting qos-profiles from QualityOnDemand #319: CQM Sub Project proposes splitting qos-profiles into its own repo (QoSProfiles). QualityOnDemand retains quality-on-demand and qos-provisioning, which remain closely related.

  • (Onboarding Tracker) MCPEnablement_PI1 #318: New repo to host Orange's MCP server implementation under the CAMARA MCP Enablement initiative. Provider implementation only — no new CAMARA API or normative MCP spec.

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

Jesús Peña García-Oliva

fabrizio moggio 

Herbert Damker Thorsten Lohmar Masaharu Hattori