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)

• Action Items Review

• Closed Pull Request:

  • Adding 3GPP Release information to API Description by tlohmar · Pull Request #51 · camaraproject/DedicatedNetworks

  • Clarification on Accesses API usage. by tlohmar · Pull Request #53 · camaraproject/DedicatedNetworks

  • Clarification of QOS Profiles by tlohmar · Pull Request #54 · camaraproject/DedicatedNetworks

  • Clarification of Device Object usage by tlohmar · Pull Request #55 · camaraproject/DedicatedNetworks

  • Aligning QosProfileName definition with QualityOnDemand by tlohmar · Pull Request #59 · camaraproject/DedicatedNetworks

  • Reduce indentation in Gerkin files to align with centralized linting … by rkandoi · Pull Request #67 · camaraproject/DedicatedNetworks

• Admin Pull Requests

  • admin: migrate to centralized linting workflows by hdamker-bot · Pull Request #65 · camaraproject/DedicatedNetworks

• Issues and Pull Requests:

  • Figure not readable in DedicatedNetworks_GeneralDescription.md · Issue #63 · camaraproject/DedicatedNetworks

    • Improving Figure readability for different browser appearance themes … by tlohmar · Pull Request #66 · camaraproject/DedicatedNetworks

      • Browser-based Mermaid colors

  • Heads-up: New qos-booking-and-assignment API overlaps with dedicated-networks scope · Issue #62 · camaraproject/DedicatedNetworks

    • Suggestion to join the QOD working group

  • Adjust Gerkin test cases to reduce size to align with central linting by rkandoi · Pull Request #68 · camaraproject/DedicatedNetworks

  • Remove `oAuth2` security scheme · Issue #56 · camaraproject/DedicatedNetworks

  • [Profiles API] NetworkProfileId is a string but format is not yet specified · Issue #47 · camaraproject/DedicatedNetworks

  • [Accesses API] Improve error handling when access is requested at incorrect time · Issue #46 · camaraproject/DedicatedNetworks

  • [API Design Guideline] Potential usecases / reuse of DeviceResponse Object · Issue #44 · camaraproject/DedicatedNetworks

  • [API Design Guideline] Does an API not implementing OIDC Discovery make it non-CAMARA compliant · Issue #43 · camaraproject/DedicatedNetworks

  • [API Design Guideline] "id" could be more descriptive in payload · Issue #42 · camaraproject/DedicatedNetworks

  • [Accesses API] POST operation is synchronous - may be there are use cases for async. · Issue #40 · camaraproject/DedicatedNetworks

  • [Accesses API] x-device Header clarifications · Issue #39 · camaraproject/DedicatedNetworks

  • dedicated-network-accesses.yaml missing device lifecycle · Issue #21 · camaraproject/DedicatedNetworks

  • Application Developers use cases · Issue #20 · camaraproject/DedicatedNetworks

  • Scope of Dedicated Networks API version 0.1.0 · Issue #8 · camaraproject/DedicatedNetworks

    • r1.2 for version 0.1.0 (Fall'25 M4) by rkandoi · Pull Request #64 · camaraproject/DedicatedNetworks

    •  

• Scope for next release

•  

Minutes

• Walk through of the updates

• No objections raised to joining with Quality on Demand Working Group as proposed by Thorsten and Herbert

  • We will need to join the Friday QoD working calls, and if needed, we can schedule meetings for Dedicated Networks as needed

  • Likely Monday calls are no longer needed if the above proposal is accepted

  • Masa suggested that any clarity on WoW depends on future discussions, but clarified that all discussions on QoS Booking APIs are under the QoD WG and no separate calls are arranged

  • For the moment, DN group suggested to keep the slot until we are confident Dedicated Network related issues have enough time in the QoD WG sessions

  • If everything works out smoothly, DN WG will join the QoD WG call on Sep-5 (Friday)

• Stefano requested to have an ramp-up training on QoD APIs

  • Thorsten suggested that we will ask the QoD to do this on Sep-5

• PR related to Gerkin issues reviewed in the call and approved + merged

• Issue #47 deemed non-critical for Fall’25 release. Moved to subsequent release.

Action items