DRAFT AGENDA

...

Type @ and your name to indicate your attendance

LF Staff: na

Community:   Herbert Damker Jose Luis Urien Pinedo Akos Hunyadi Eric Murray Jorge Garcia Hospital Rafal Artych Ramesh Shanmugasundaram Toshi Wakayama Syed Rehman Thorsten Lohmar, Joachim Dahlgren, Randy Levensalor, Masaharu Hattori

Agenda

• Antitrust Policy
• Review of previous meeting minutes
  • ...Agreed
• General Topics
  • Overall project
  • New Issues
  • Open PRs
  • Existing Issues
• Any Other Topics

...

• GSMA (Toyeeb Rehman) presented in TSC a list of issues identified during certification of CAMARA API implementations. Worth to read and consider. (add)
• Release v0.3.0 of Commonalities and action points from it:
  • New issue for X-Correlator to be created → Herbert will create an see issue #271
  • Review of Linting rules implementation → Herbert will create an issue, see PR #270 below
• Release process and milestone plan for a CAMARA "meta" release in work. Will be relevant also for QualityOnDemand (new Commonalities & ICM releases, own scope definition for this release)

...

• PR #270 Adding configuration for linting ruleset
  • Created by Rafal Artych based on the agreed and tested configuration within Commonalities 0.3.0
  • Merge before doing #265 (split of APIs) ?- yes
  • Ready for final review by code owners.
• PR #269 Patch of documentation to address #267 (lack of statusInfo in SessionInfo)
  • Created by Herbert Damker as agreed for issue #267
  • To be discussed if we want to have this as a patch or rather add the missing statusInfo directly as patch towards 0.10.1
• PR #255 Updating the project scope in the ReadMe
  • Reopened for review after MWC as agreed.
• PR #228 and #217 still in draft mode.

New Issues

...

• #271 X-Correlator required within OAS definition of QualityOnDemand API
  • ...
• #268 Provision mode for QoD
  • Enhancement or even new API - would a discussion in API Backlog make sense?
  • ...

Existing Issues (without backlog, reverse order)

• #101 List endpoint for active sessions of authenticated user
  • At least two different use cases
    • As described originally within the issue: API consumer wants to get a list of open sessions across different subscribers
      • within result would be only session created by the API consumer itself
      • Herbert: in this case the API consumer will not get additional (personal) information from this endpoint which they haven't received already earlier (during session creation). Potentially possible with 2-legged token?
    • Use case added by Jose: API consumer wants to get a list of sessions which are (potentially) already opened for a specific device
      • Would require a 3-legged token and potentially consent from end-user?
  • Discussion to be continued within the issue
• #166 Extend QoS Profile queries to list profiles based on specific users or devices
  • Discussion updated by Emil and Jose
  • #265 to be done first (split of APIs)
  • More clarifications on subscription will be added by Emil
  • Description of parameters/filters within the issue needed
• #194 Add Application Function Id (afId) or Sponsor Id
  • Syed opened the issue under identity and consent management project camaraproject/IdentityAndConsentManagement#126
• #238 Updating the project scope in the ReadMe
  • PR will be reopened after MWC (see previous minutes)
• #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
  • #265 to be done first (split of APIs)
• #245 Update and enhance test definition file for QOD API
  • Work in Device Location ongoing. Probably next week some issue will be opened in Commonalities (and TSC about GSMA Certification)
• #249 Duration in QosProfile and SessionInfo
  • See previous minutes.
  • #265 to be done first
• #257 Error behaviour when session cannot be created due to "time cap" limitation
  • PR will be created by Jose.
• #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
  • Jose will prepare a PR next week, just the split without any further changes (incl. copying schemas, decision about common file later)
• #267 Polling for statusInfo in GET /sessions/{sessionId} not possible
  • Bug within v0.10.0,
  • Two alternatives to resolve:
    • Remove statusInfo from this note → would lead to v0.10.1 (change in documentation)
      • Herbert will prepare a PR against release-0.10.0 branch
      • But we will wait with a patch release in case there will be further issues and/or clarifications of documentation for v0.10.x
    • Add the statusInfo to the GET /sessions/{sessionId} - response → will be done in v0.11.0
  • Document in issue Herbert Damker 

Any other topics

• Next QoD will be on March 22nd, at 14:00 CET / 13:00 UTC.
• Please be aware the US will change to summertime on March 10th, so this specific meeting will be there one hour later as usual (e.g. 06:00 PDT, 09:00 EDT)
• The first meeting in EU summertime will be on April 5th at 14:00 CET / 12:00 UTC

...