Scope for Spring25 release (in preparation)

[hdamker]

Problem description

This issue should describe the scope for the next versions of the APIs within the QualityOnDemand, targeting the Spring25 meta-release.

Expected action

Target versions (tbd)

• quality-on-demand 1.0.0
• qos-profiles 1.0.0
• qos-provisioning 0.2.0

Targets for Spring25 (proposed/to be discussed)

• "Stabilisation", with target to release the first stable version (Prio1)
  • Correction of flaws in the definition
  • Clarification and improvement of documentation
  • Incorporation of feedback from implementations
  • Alignment with Commonalities & ICM changes for Spring25
• Enhancements (Prio2)

Issues with fixes in Spring25 scope:

• Fixes in scope of Scope for potential patch release r1.3 (v0.11.1/v0.1.1) #368
  • Authorization and Authentication section need to be aligned with ICM 0.2.0 text. #361
  • Local links within API documentation have to be release specific #363
  • Add user story for QoS Profile #341
• Support of Multi-SIM lines in QoD APIs #362 Description of current to be expected behavior within patch release (Add guidance for multi-SIM scenarios #378)
• Add explanation on why there is a "POST /retrieve-sessions" instead of GET #359 (potentially already addressed already within patch release of Fall24)

Issues currently under discussion, potentially in scope:

• Support of Multi-SIM lines in QoD APIs #362 - Long-term solution based on guidance from Commonalities (not yet available)
• Add support for DSCP markings for QoD sessions #173 - refinement of use case(s) needed
• Extend the query capabilities for Qos Profiles #147 - option to address Providing developers with alternate to QoS profile #302
• Review Attribute Descriptions with References to External Specifc #286 - see comment below
• Rework definition of QoS flow(s) #243 - see comment below

Potential new API qod-booking (separate repository)

• Potential enhancement of booking feature for qod-provision #337 - issue to be created in API Backlog first

Backlog issues not in Spring25 scope (to be decided which of them can get even closed):

• Application IPs are not shared by OTT for QOD API #317 - discussion, no expected changes defined yet
• Potential alignment of duration format between quality-on-demand and qos-profiles #304 - not in scope of Commonalities for Spring25?
• Providing developers with alternate to QoS profile #302 - potentially indirectly addressed by Extend the query capabilities for Qos Profiles #147
• Add Application Function Id (afId) or Sponsor Id #194 - obsolete, as access tokens are application provider specific?
• Need to support ability to configure fallback qos #45 - potentially indirectly addressed by Extend the query capabilities for Qos Profiles #147?

Additional context

[RandyLevensalor]

#243 was discussed to be included in the release. At the minimum to revise the documentation to clarify the attributes and usage, though breaking changes were discussed as well.

#286 will likely be included in this release. This is a documentation change and will be discussed further in Jan/Feb 2025 timeframe in a dedicated meeting.

[hdamker]

#286 will likely be included in this release. This is a documentation change and will be discussed further in Jan/Feb 2025 timeframe in a dedicated meeting.

@RandyLevensalor who will setup the meeting? QoD group or Commonalities?

[hdamker]

(comment added originally to the wrong issue):

We need to add the changes coming from Commonalities and ICM to the scope:

• error definitions
• changes for (implicit) subscriptions
• update of info.description texts
  Concrete issues to be created when the alpha releases of Commonalities and ICM are available.