2025-11-03 Dedicated Networks (Breakout) Minutes
Community Attendees:
@Thorsten Lohmar @Hubert Przybysz @Masaharu Hattori @Stefano Brivio
Community Attendees:
LF Staff:
Agenda & Minutes
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)
Admin
Issues and Pull Requests:
Thorsten’s thinking to start with a Ball-Park, but define an Error Code. It can be seen as an API provider policy, how many more devices are allowed, e.g. 10% more or even 0% (hard limit) more.
Stefano, we many need to think about admission control at run time (run time == network is activated). Thorsten, there is also the ToC, which can make the responsibilities for the ASP clear.
We need to separate between the admission control and access control. → We need to make this clear in the API description.
Should update the DedicatedNetworks_GeneralDescription.md including the usage of Device Groups. AP, create a separate PR
New PR in Commonalities to extend Status Code 409 with a WRONG_STATE. This wrong WRONG STATE seems more generic and can be applicable for other APIs.
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