Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Community: Herbert Damker Ben Hepworth Jose Luis Urien Pinedo Randy Levensalor Eric Murray Masaharu Hattori

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

...

Overall topics

...

New Issues

...

  • #362 Support of Multi-SIM lines in QoD APIs

    • Previous minutes:

      • Target: define a common behaviour across operators (which all operators can implement)

      • Secondary MSISDNs: not known to users/developers, can't be used in 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, but 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

      • Documentation of expected behaviour also relevant for a Fall24 patch release

    • Discussion to be continued within the issue (@all)

      • Differentiate between short-term clarification in API documentation

      • Long-term solution (within next release?)

  • #361 Authorization and Authentication section need to be aligned with ICM 0.2.0 text

    • Previous minutes

      • PR to be created (can go now into main)

      • In scope of Spring 25 if not already within a Fall25 patch release (see above)

  • #359 Add explanation on why there is a "POST /retrieve-sessions" instead of GET

    • Previous minutes:

      • Create one sentence and propose also to Commonalities to add to the Guideline

      • To be discussed first within the issue

      • In scope of Spring 25 if not already within a Fall25 patch release (see above)

    • See also new issue #366 which indicates that there is a need for clarification how to get all profiles

    • Randy Levensalor to prepare a PR, across all three APIs

  • #341 Add user story for QoS Profiles

    • see PR #367

  • #337 Potential enhancement of booking feature for qod-provision

    • new comment with use case draft available: https://github.com/camaraproject/QualityOnDemand/issues/337#issuecomment-2391997666

    • Masaharu Hattori offered to propose a state diagram, as started to discussed in the issue.

    • Eric Murray propose to have also a user story which describes the value of the feature

    • An important question if the “booking” comes with reservation of resources (a commitment that the session will be available at the requested time) or only a scheduling of the session/provisioning creation

      • a reservation would require to also provide the geographic region, to allow the network operator to check/reserve resources

  • #147 Extend the query capabilities for Qos Profiles

    • Previous meeting minutes

      • Application-profile as potential input, returning fitting qos-profiles

        • Challenge: application-profile is a resource which need first to be created

      • Use of application-profile API is also discussed in other Sub Project (e.g. EdgeCloud)

      • Potentially related: Commonalities/issues/179

  • #173 Add support for DSCP markings for QoD sessions

    • Previous meeting minutes:

      • Refining use case as next step

      • DSCP to matching an IP flow? 

      • Use of L4S in context of a QoS profile as one potential user story

  • #302 Providing developers with alternate to QoS profile

    • Previous meeting minutes:

      • potential via #147 instead as a direct parameter within the quality-on-demand API

      • evaluate relation to new QualityByDesign concept

  • Remaining issues (#45, #194, #243, #286, #304, #317) to be checked (off-line) regarding closing / taking into scope

...

  • Next QoD meeting will be on October 18th, at 14:00 CEST / 12:00 UTC, Randy Levensalor will take preparation and moderation.

Action items