2024-01-12 Quality on Demand - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: na

Community: @Herbert Damker, @Eric Murray, Akos Hunyadi, @Andrew Wajs, Emil Zhang, Guy Vidal, Patrice Conil, @Rafał A. (Unlicensed), @Ramesh Shanmugasundaram, Randy Levensalor, @Syed Rehman, Thorsten Lohmar, @Toshi Wakayama

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

- Antitrust Policy

Roll Call
Action Items Review
Agenda Bashing
General Topics
- Open PRs
- New issues
- Open Issues - relevant for release v0.10.0
- Open Issues - planned for v0.11.0
Any Other Topics
- ...

Minutes

Action Item Review

Open/New PRs

#253 Update READMEs for new meeting link and meeting minutes in wiki
- New PR, merged
#252 feat: move "basePath" /qod/v0 to "url"-property
- New PR, fixes issues #251, discussion see below
#228 draft for issue #101, no update
#217 draft for issue #194, no update

New Issues

Check if relevant for v0.10.0 or later

#254 Send notifications for all qosStatus changes
- Relevant for v0.10.0
- No change to API definition, documentation only
- Action: PR to be created
#251 Update the "server"-section to align with other CAMARA specifications
- Thorsten will propose another default apiroot (with an example base path) or extend the description
- Relevant for v0.10.0 (to be aligned with other APIs, e.g. Device Status and Device Location)
#249 Duration in QosProfile and SessionInfo
- Agreement: For v0.10.0 we will add a note within the documentation/comment in the qosProfile maxDuration, that the maximum duration should not exceed 86400 seconds
- The restriction of the maximum duration will be revisited for v0.11.0
- Action: PR to be created @Herbert Damker Jan 19, 2024
#247 Clarification: Behaviour when requested duration < minDuration
- Action: PR with dedicated 400 error to be done (Who)

Open Issues - planned for v0.11.0

#245 Update and enhance test definition file for QOD API
- DT plans to work on it
- Guidelines currently under discussion Commonalities to be considered (PR #117)
#244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
- Discussion in Commonalities/ICM not finally closed, but the the direction is agreed:
  - OIDC to be used for all operations
  - We need to decide about the scope names for each operation (with format defined in ICM)
  - Text to be included within the YAML introduction about the rules for the actual authorization flows, as defined in https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md#camara-api-specification---authorization-and-authentication-common-guidelines
#243 Rework definition of QoS flow(s)
- No update
- Dependency on #244
#166 Extend QoS Profile queries to list profiles based on specific users or devices
- No update
- Dependency on #244
#101 List endpoint for active sessions of authenticated user
- No update
- Dependency on #244

Any other discussion

Final release of v0.10.0 → decision will be taken in next call, if there are no new issue relevant for the release

CAMARA Project