2025-10-20 Dedicated Networks (Breakout) Minutes
Community Attendees:
Community Attendees:
LF Staff:
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.
Agreement of last minutes (link)
TSC agreed, that the Dedicated Networks API is continued under the umbrella of the QoD Working group. See 2025-09-18 TSC Minutes - CAMARA Project - CAMARA Project
Daylight saving change on 26th October.
AP: Ask CAMARA support to adjust the meeting time (since UTC TZ anchored) to keep the same timeslot (i.e. 1000h (CEST) → 1000h (CET)).
Spring 26 Meta-Release: Spring26 meta-release (preliminary) - CAMARA Project - CAMARA Project
M3: 31st January, 2026
M4: 31st of March, 2026
Closed Pull Request
Issues and Pull Requests:
The PR was submitted during the meta release finalization work. so far, no comments. From lazy consensus perspective it seems agreeable.
The PR introduces the usage of PATCH operations, while CAMARA is not (yet) using JSON PATCH. There is no commonalities guidelines around PATCH operation.
How does an API invoker obtain the total number of devices within the Network Reservation?
Quota Management (Max Number of Device): The API provider function many need to check the total number of devices and act, when exceeding.
Quota Management is actually a separate issue, as we need to clarify the current APIs.
Should update the DedicatedNetworks_GeneralDescription.md including the usage of Device Groups. AP, create a separate PR
To be consistent with other DN resource identifiers, the NetworkProfileId should be UUID formatted. a NetworkProfileName could be added to support human readable names (see QOD QoSProfileName).
AP Hubert: Create a PR
Adds a new Error Coder 409 with Wrong State. We should make it clear in Issue #46, that Code 422 is not usable for Non-Device related identifiers.
No comments on PR #81. Can wait until next meeting.
New PR in Commonalities to extend Status Code 409 with a WRONG_STATE (AP for Thorsten). This wrong WRONG STATE seems more generic and can be applicable for other APIs.
New PR to Commonalities: New 409 error code called WRONG_STATE by tlohmar · Pull Request #550 · camaraproject/Commonalities
Should be clarified in ICM. Consistency around usage OAuth Client Credentials grant flow · Issue #284 · camaraproject/IdentityAndConsentManagement
Since the last comment is older than a month, we need to revive the thread.
Current API spec seem to be inline with commonalities, i.e. no requirement on property naming. Brought as a discussion to commonalities.
Direction of Commonalities still unclear, since CloudEvents is following a different id naming principle than other APIs. The existing API seem to be still inline with commonality rules.
[Accesses API] x-device Header clarifications · Issue #39 · camaraproject/DedicatedNetworks
To be brough to commonalities: (A) can we continue using GET with a header and (B) is there a benefit of harmonizing using of device object in header. Two approaches: Either create individual headers for each device object property (as done in simple edge discovery) or serialize the device object (as done in Dedicated Networks)
Open
Application Developers use cases · Issue #20 · camaraproject/DedicatedNetworks