Community Attendees:

@Thorsten Lohmar @Hubert Przybysz @Surajj Jaggernath @Barath K @Tanja de Groot @Stefano Brivio

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)

• Action Items Review

  •  

• Closed Pull Request:

  • Pull Request #24: Removing API Design Considerations document

• Issues and Pull Requests:

  • Pull Request #26: Update Telefonica participant

    • Carlos need to accept the invite.

  • 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

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

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

Minutes

• Comments on agenda no comments.

• Very few participants due to various bank holidays, same agenda will be base for next meeting.

• Discussion on Pull Request #27.

  • Question for Commonalities WG to provide guidelines on documentation with how much information needs to go into API yaml file versus other document. yaml markdown has more limitations when to comes to tables, mermaid flows, links to figures, etc.

Action items