2026-06-12 Connectivity Quality Management Minutes
Community Attendees:
Herbert Damker Ben Hepworth Jose Luis Urien Pinedo Emil Zhang Surajj Jaggernath Murat Karabulut
Community Attendees:
Murat Karabulut Eric Murray Masaharu Hattori Randy Levensalor Thorsten Lohmar Hubert Przybysz Toshi Wakayama
LF Staff:
DRAFT AGENDA
Agenda
The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company’s legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
General
DedicatedNetworks (@Thorsten Lohmar, @Hubert Przybysz, @Stefano Brivio)
QualityOnDemand (@Herbert Damker, @Randy Levensalor, @Jose Luis Urien Pinedo, @Eric Murray)
QoSBooking (@Masaharu Hattori, @Jose Luis Urien Pinedo, @RAM RAMANATHAN)
AOB
Minutes
Previous Meeting Minutes
General Sub Project Topics
CQM new repositories (Herbert Damker )
QoSProfiles
Repo for an established, stable API.
Onboarding Tracker in APIBacklog: https://github.com/camaraproject/APIBacklog/issues/320
Codeowners from QualityOnDemand initially (split-out best practice, can be changed when the repo exists with PRs)
Move over of the code:
qos-profiles.yaml has been already changed since Fall25 release, ongoing PR to align with Commonalities 0.8.0 => recommendation to copy over with the r4.1 (1.1.0-rc.1 version)
“Area API”
New repository for a new API (currently dedicated-network-areas 0.1.0-alpha.1 released)
New Open Issue on CQM: Separate of dedicated-networks-areas API into its own repository (service-areas) · Issue #10 · camaraproject/ConnectivityQualityManagement
Action: Feedback on the issue until next Tuesday, June 16th
Name probably NetworkServiceAreas (for the repository)
Open issue in APIBacklog to be updated: https://github.com/camaraproject/APIBacklog/issues/295
Sync26 Timeplan and release process
Declaration of Sync26 participation until June 18th
release-plan.yaml: done for all three repositories
Scope issues
QualityOnDemand: draft created, needs discussion and potential trimming:
QoSBooking: existing scope issue
DedicatedNetworks: existing scope issue
Relevant date: M3 date is June 30 - expected is that all APIs deliver a pre-release with rc versions until then
Dashboard of Release Progress (updated once every 24 hours): CAMARA Release Progress
Alignment/Adaptation to latest Commonalities release (r4.3 - Spring26)
Relevant for all APIs in the three repositories
Expectation is that ALL errors and warnings from validation are addressed (or exceptions documented) and refs$ used
Draft PR for qos-profiles: https://github.com/camaraproject/QualityOnDemand/pull/575
DedicatedNetworks
https://github.com/camaraproject/DedicatedNetworks/issues/69
Functional issues addressed
Alignment with Commonalities.
Cleanup first, starting with ref$'s. Fix duplicated data types. That will inherit limitations and descriptions
Paginations
Parallel PRs
Issues and PRs which are cross Sub Project relevant and need alignment?
None so far.
QualityOnDemand
Issues and PRs which are cross Sub Project relevant and need alignment?
https://github.com/camaraproject/QualityOnDemand/issues/520
Agreement on the 2xx logic: a correct request will be answered with 2xx, but MAY already have the status UNAVAILABLE if the requested QoS can not be provided by the network or other business reasons.
A new statusInfo value will only be discussed if we have further breaking changes and plan a major version, but not alone as a reason for a breaking change (so for 1.2.0 we go with option (a), for a potential 2.0.0 with option (b)).
Application Server property in requests and responses (issues #513, #528, #529)
Eric Murray removing the DNS name option from PR #522, keeping arrays of IP addresses and the current option of single IP address (with subnet possibility). Keeping backward-compatibility
Issue https://github.com/camaraproject/QualityOnDemand/issues/475
Jose Luis Urien Pinedo revisit the discussion and provide a summary if there is something left to be addressed
Question from Randy Levensalor about QoSProfiles: should we address the hint about OperationId (non camelCase)?
Discussion result: Only if not a breaking change.
QoSBooking
Issues and PRs which are cross Sub Project relevant?
Murat Karabulut taking care of the alignment of sos-booking-and-assignment with Commonalities 0.8.0 (r4.3), addressing the warning
Murat Karabulut checking the issues in the scope issue if they are still in scope; addressing the comments on PR
AOB
Next meetings:
Next regular CQM: June 26th
Dedicated Networks Breakout: check schedule with @Thorsten Lohmar
CQM Breakout – API Alignment: check schedule with @Thorsten Lohmar