DRAFT Online Notes (will be updated)
(parts in italics are from last meeting notes, just as reference/starting point of the discussion)
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff: na
Community: Jose Luis Urien Pinedo Andrew Wajs Rafal Artych Gervais-Martial Ngueko Akos Hunyadi Herbert Damker David Butler Eric Murray Joachim Dahlgren Emil Zhang P. Das
Agenda
- Antitrust Policy
- Review of previous meeting minutes
- Agreed
- General Topics
- Overall project
- New Issues
- Open PRs
- Existing Issues
- Any Other Topics
Minutes
Overall project
- David Butler (BBC Research and Development) new in the sub project
- is asking if TS 26.512 5GMS R18.0.0 (2023-12) 5G Media Streaming (5GMS); Protocols
See section 6.4.3 https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3647
- is asking if TS 26.512 5GMS R18.0.0 (2023-12) 5G Media Streaming (5GMS); Protocols
- Release v0.3.0 of Commonalities is available
- New issue for X-Correlator to be created → Herbert will create an issue
- Review of Linting rules implementation → Herbert will create an issue
- Other aspects covered by #244 and #245
- DT provided an update of its provider implementation in https://github.com/camaraproject/QualityOnDemand_PI1
- Based on v0.10.0-rc1, based on final release will follow
Open Pull Requests
- The three open PRs are currently in DRAFT mode, not ready for review (see respective issues below)
New Issues
- #267 Polling for statusInfo in GET /sessions/{sessionId} not possible
- Bug within v0.10.0,
- Two alternatives to resolve:
- Remove
statusInfofrom this note → would lead to v0.10.1 (change in documentation)- Herbert will prepare a PR against release-0.10.0 branch
- Add the
statusInfoto the GET /sessions/{sessionId} - response → will be done in v0.11.0
- Remove
- Document in issue Herbert Damker
Existing Issues (without backlog, order reversed)
- #101 List endpoint for active sessions of authenticated user
- At least two different use cases
- ...
- ...
- Continue the discussion within the issue
- At least two different use cases
- #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 by Emill
- Description of parameters/filters within the issue needed
- #194 Add Application Function Id (afId) or Sponsor Id
- OperateAPIs (Onboarding) has the concept of application
- No concept for applicationId yet in ICM?
- Action: Syed will open an issue within I&CM and refer to our issue
- Syed opened the issue under identity and consent management project camaraproject/IdentityAndConsentManagement#126
- ...
- #238 Updating the project scope in the ReadMe
- Change need to be communicated back to API Backlog, TSC, and OGW Product team to ensure a consistent communication
- Agreement: reopen PR for review after MWC is over
- ...
- #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
- Agreement: first do the split as agreed in #265
- Note from Eric: wildcard scope will not apply to Client Credentials
- #245 Update and enhance test definition file for QOD API
- Should consider https://github.com/camaraproject/Commonalities/pull/117
- Telefonica is working on test definitions, Orange is working in Device Location on it as well
- After it's done for these APIs, can contribute also for QoD
- Probably next week some issue will be opened in Commonalities (and TSC about GSMA Certification)
- #249 Duration in QosProfile and SessionInfo
- Keep "seconds" for duration within QoS createSession and align QoS Profile (at least min/max Duration)
- Rafal: Commonalities discuss "duration" in #137 (Commonalities) using RFC 3339 (value and unit in one string), will be used in OAS 3.1
- Remove the lower and upper limit from createSession, they are replaced by minDuration and maxDuration in QoS Profile definition
- #257 Error behaviour when session cannot be created due to "time cap" limitation
- Agreed within last call to be in scope of v0.11.0
- PR will be created by Jose
- #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
- Common schema should be defined only once in a common file, either in sub project of from Commonalities
- Process and script needed to create one bundled specification file for distribution (run after every merge)
- To be discussed: use of (which) released version from Commonalities
- Agreement in last meeting: to do the split
- Jose will prepare a PR next week, just the split without any further changes (incl. copying schemas, decision about common file later)
- Common schema should be defined only once in a common file, either in sub project of from Commonalities
Any other topics
- Next QoD will be on March 8th, at 14:00 CET / 13:00 UTC