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)

  • only little attendance last meeting (link)

• Action Items Review

  •  

• General Aspects

  • API Release Tracker should be per API, i.e. for each yaml spec.

  • We need to start preparing a release-candidate PR.

• Closed Pull Request:

  • Pull Request #26: Update Telefonica participant

    • Carlos has full codeowner rights

• Issues and Pull Requests:

  • Issue #22: Authorization and Scopes

    • Pull Request #23: Enhancing security features

      • Scope naming aligned with commonalities

      • Security schemes: OIDC (mandatory for CAMARA) and OAuth Client Credentials

      • CAMARA “Authorization and authentication“ boilerplate template

      • Device Object is optional within Accesses API

  • Issue #8: Scope of Dedicated Networks API version 0.1.0

    • Issue #21: dedicated-network-accesses.yaml missing device lifecycle

    • Issue #28: API Description / API Documentation

      • Pull Request #27: Proposals for info.description section

        • Proposal is to have a simplified description in the info.description section, which refers to a common API descriptions (describing the relations between the APIs).

      • Pull Request #29: General Dedicated Network description outside yaml

        • github markdown supports more format features like yaml markdown, like tables, mermaid, etc

        • Might be better to have an overall description, describing the relation between different APIs, in github API_documentation folder.

  • Issue #17: Correlating a Dedicated Network resource within a subsequent IoT Data Transfer Activation API call

Minutes

• Thorsten created new release trackers for the 3 APIs

  • All trackers point to same Scope issue (which is okay)

• Heads up that release candidate Pull request coming next week targeting M3 / Fall release 2025

• PR23:

  • Added schemes for OIDC and OAuth2: Several cases OAuth2 Client credentials are enough, OIDC discovery is non-essential complexity.

  • Decision: PR has been open, feedback is incorporate. Will merge offline once last pending approval is received.

• API Docs (PR27 and PR29) - moved content from yaml to Github: make easier to find technical details for developers who know the concept. A central place to find the concept across the API yaml files.

  • Comparison with other CAMARA APIs: Simpler, but still have pics in Github. (Using main from github, or links from external private repos)

  • Also contributed guidance to commonalities

  • The use of tables / html in the yaml is much harder than using the Github markdown approach

  • Need version control of the links etc. - remove hardcoded references. Will be done in a subsequent commit.

  • Suggested to combine the two PRs to one so everything goes to one commit. (Thorsten did it online in the call :))

  • Decision: No comments on the content of the PR. After offline approvals, merge can also be done offline (even before next meeting).

• Roles:

  • Discussion on Roles as documented in the Wiki page. Thorsten raised that HLD now has 3 roles defined, but description has 6. Some could ver overlapping and we could reduce the roles. Or we might be missing considerations. Need to check with @Stefano Brivio in a subsequent discussion. Current thinkign from Thorsten is that three roles may be enough. High level sequence diagram though has “Physical Network” and “Devices” which can be additional entities that need to be described. May be also need to separate providers based on which API they provide.

  • Rajat - editorial notes in the API descrition in Wiki need to be aligned with the description on Github.

• Comparison page in QoD WG to compare Dedicated Network, QoD Booking and/or other pages.

  • Thorsten will share link to the page when available. Needs to be discussed within DN WG thorughly.

  • Issue here: https://github.com/camaraproject/QoSBooking/issues/12

Action items