...
Community: Herbert Damker , Eric Murray Ben Hepworth , Randy Levensalor Toshi Wakayama , Jose Luis Urien Pinedo , Thorsten Lohmar , Masaharu Hattori , Konstantinos Fragkos , Joachim Dahlgren , Akos Hunyadi , efezhan Surajj Jaggernath , Jorge Garcia Hospital
Agenda
- Antitrust Policy
- Review of previous meeting minutes
- Overall Topics
- Regular Topics
- Closed PRs and Issues
- Open Pull Requests
- New Issues
- Open Issues
- Any Other Topics
...
- Fall24 - closing #292
- will be closed
- Patch release for Fall24?
- Currently only #361? (Authorization and Authentication section need to be aligned with ICM 0.2.0 text.)Other candidates
- Make local links release specific → new issue for potential patch release (Herbert Damker to create it)
- Swagger / Redoc do not pick up relative links, therefore relative links wouldn't work
- Links to images have to go to the release tag
- Going forward: automation within release creation?
- Spring25 Release
- Scope Issue to be created
...
- #362 Support of Multi-SIM lines in QoD APIs
- Target: define a common behaviour across operators (which all operators can implement)
- Secondary MSISDNs: not know to users/developers, can't be used public
- Just using the "main" device not sufficient (way to notify the application about the chosen device/SIM missing)
- Enabling all devices with same MSISDN?
- Maybe an option, only in combination with a selected application (IP) flow
- Request to those who have implemented to share their current solution
- Target: Derive some guideline/documentation update for the current version
- #361 Authorization and Authentication section need to be aligned with ICM 0.2.0 text
- #359 Add explanation on why there is a "POST /retrieve-sessions" instead of GET
- Still needed?Create one sentence and propose also to Commonalities to add to the Guideline
Open Issues
- https://github.com/camaraproject/QualityOnDemand/issues
- #341 Add user story for QoS Profiles
- Draft for next call Randy Levensalor - Ben Hepworth will be helping with this.
- no PR yet (Randy Levensalor ) Not required for release. Will create PR next week.
- #337 no update in this meeting
- #147
- application-profile as potential input (returning fitting qos-profiles?)
- application-profile API is also discussed in other Sub Project (e.g. EdgeCloud)
- maybe related: #179 in commonality
- #173
- Refining use case as next step
- Matching an IP flow?
- Use of L4S in context of a QoS profile as one potential user story
- #302
- potential via #147 instead as a direct parameter within the quality-on-demand API
- evaluate relation to new QualityByDesign concept
- to be checked off-line regarding closing / taking into scope https://github.com/camaraproject/QualityOnDemand/issues
Review possible scope and time plan for Spring Release
- #337 Potential enhancement of booking feature for qod-provisioning
- Masaharu Hattori proposed this to be considered for Spring25 release
- Jose Luis Urien Pinedo Suggested we clarify the use case, including evaluating user notification process for delayed provisioning.
- #147 Extend the query capabilities for Qos Profiles
- #173 Add support for DSCP markings for QoD sessions
- #302 Providing developers with alternate to QoS profile
- #341 Add user story for QoS Profile
...