Community Attendees:

@Thorsten Lohmar , @Rajat Kandoi , @Steve Vickers @Masaharu Hattori @Alejandro Palmier , @Hubert Przybysz , @Surajj Jaggernath , @Stefano Brivio , @Fadime Demirer , @Barath K

Agenda

Antitrust Policy

• Agreement of last minutes (Link)

• Action Items Review

  • Participants Page Link

  • New Pull Request #24: Removing API Design Considerations document :

• Meta Release Fall 25

  • Meta Release Fall 25 : Meta-release Fall25 - CAMARA Project - CAMARA Project

  • Release Tracker: dedicated-networks v0.1.0 - CAMARA Project - CAMARA Project

  • API Readiness Checklist: ReleaseManagement/documentation/API-Readiness-Checklist.md at main · camaraproject/ReleaseManagement

• API Descriptions

  • API Highlevel Description : Dedicated Networks APIs High Level Description - CAMARA Project - CAMARA Project:

  •  

• Issues and Pull Requests

  • Issue #22: Authorization and Scopes

    • Pull Request #23: Enhancing security features

    • Scope Naming: Commonalities/documentation/API-design-guidelines.md at main · camaraproject/Commonalities

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

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

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

  • Issue #20: Application Developers use cases

• API Descriptions

  • CAMARA API Description https://lf-camaraproject.atlassian.net/wiki/pages/createpage.action?spaceKey=cam&title=DedicatedNetworks%20API%20Description&linkCreation=true&fromPageId=96239844

     

Minutes

PR #23

• PR #23 - explained the security scopes - suggested to use Oauth2 client credentials in the API spec

  • Related to the scope of the initial public release - goal is to keep it simple and workable - but these views might different in the group

Meta release

• Start aiming for initial public release if we want to be part of Fall release

• Need release candidate APIs by 21 June

• No requirement to be part of Fall25 release - but the ambition is to be part (at least as good practice)

POST vs PUT - especially for device accesses, however challenge with batch of devices

Question from Thorsten to full group

• Should we use “terms and conditions” instead of agreements, and contracts in the documentation?

• RK: Yes, can do that in the next phase.

Device accesses states - separate meeting offline and findings to be presented in bi-weekly meetings.

Action points

• Sub project participants requested to updated the Participants page with the right roles

• Issue #20: Application Developers use cases - to be updated by @Stefano Brivio

• Review - https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/93061121

• High level description - continue work offline but also create PRs for the 3 spec

• POST vs PUT discussion - suggestion to create new issue, (@Stefano Brivio )