Merge pull request camaraproject#222 from eric-murray/main

Add minutes of meeting for Friday 22nd September

documentation/MeetingMinutes/MOM-2023-09-22.md

@@ -0,0 +1,97 @@
+# Camara QoD meeting - MOM-2023-09-22
+
+*Friday, September 22nd, 2023*
+
+## Attendees
+
+* Eric Murray (Vodafone, Moderator)
+* Rafal Artych (Deutsche Telekom)
+* Patrice Conil (Orange)
+* Akos Hunyadi (Deutsche Telekom)
+* Jose Luis Urien Pinedo (Telefonica)
+* Emil Zhang (Ericsson)
+* Thorsten Lohmar (Ericsson)
+* Andrew Wajs (Scenera)
+* Joachim Dahlgreen (Ericsson)
+* Syed A Rehman (Verizon)
+* Toshi Wakayama (KDDI)
+
+QoD minutes: [https://github.com/camaraproject/QualityOnDemand/tree/main/documentation/MeetingMinutes](https://github.com/camaraproject/QualityOnDemand/tree/main/documentation/MeetingMinutes)
+
+## Agenda
+
+* Open PRs
+* Open Issues
+* AOB
+
+## Discussion of Open PRs
+
+* [#216 Extend session duration](https://github.com/camaraproject/QualityOnDemand/pull/216) (Associated Issue [#220 Change duration of an active session](https://github.com/camaraproject/QualityOnDemand/issues/220))
+  * Submitted as a replacement for [#162 Add PATCH operation](https://github.com/camaraproject/QualityOnDemand/pull/162), which is now closed
+  * Based on feedback received, scope is limited to extending session durations only. PR remaned.
+  * Two discussion points remain open with the PR:
+    * New endpoint requires an associated security scheme (now agreed)
+    * Should extending session durations beyond the maximum allowed for a new session (currently 1 day) be allowed?
+  * **If participants have a view on whether sessions can be extended beyond 1 day maximum duration, please comment in the associated issue**
+
+* [#217 issue_194_PR](https://github.com/camaraproject/QualityOnDemand/pull/217) (Associated Issue [#194 Add Application Function Id (afId) or Sponsor Id](https://github.com/camaraproject/QualityOnDemand/issues/194)
+  * Two discussion points currently open
+    * Exact relationship between `applicationConsumerId` and the end user, API consumer and other actors in the API transaction is not clear. In particular, for three-legged authentication, should the `applicationConsumerId` be provided at the authorisation stage (in the same way as, for example, `phoneNumber`)?
+    * Should `applicationConsumerId` be a "top level" parameter in the `CreateSession` schema, or part of the `ApplicationServer` schema?
+    * **Syed to clarify exact scope of `applicationConsumerId`, and maybe consider renaming**
+    * **Participants with a view on either open point, or with additional open points, to comment in the associated issue before the next meeting**
+
+## Discussion of Open Issues
+
+### Issues For Next Release
+
+* [#221 Change event structure and notification according to Design Guidelines changes](https://github.com/camaraproject/QualityOnDemand/issues/221)
+  * A revised model for callbacks is close to being agreed within Commonalties (see Commonalities [#56](https://github.com/camaraproject/Commonalities/pull/56))
+  * The revised model must be adopted by QoD for release 0.10.0
+  * **Jose Luis volunteers to prepare the necessary PR**
+
+* [#173 Add support for DSCP markings for QoD sessions](https://github.com/camaraproject/QualityOnDemand/issues/173)
+  * Still not clear if the proposed new parameter is relevant for mobile networks
+  * Waiting for Randy to summarize the results of the discussion and make a specific proposal for required API changes and their impact on API behaviour
+
+* [#101 List endpoint for active sessions of authenticated user](https://github.com/camaraproject/QualityOnDemand/issues/101)
+  - Akos to update issue with DT's current view on this proposal now that they have feedback from developers
+
+* [#47 Include support for /PATCH sessions](https://github.com/camaraproject/QualityOnDemand/issues/47)
+  - Use case of refreshing OAuth token for callbacks remains open
+  - Jose to review new approach to callbacks being defined by Commonalities to see if this issue is covered there. If not, this requirement can continue to be discussed within the issue.
+
+* [#209 Add 400 - Bad Request for an invalid sessionId GET + DELETE /sessions/{sessionId}](https://github.com/camaraproject/QualityOnDemand/issues/209)
+  * Closed by PR [#210](https://github.com/camaraproject/QualityOnDemand/pull/210)
+
+* [#204 Move the "description" out of "allOf"-declaration](https://github.com/camaraproject/QualityOnDemand/issues/204)
+  * Closed by PR [#205](https://github.com/camaraproject/QualityOnDemand/pull/205)
+
+### Backlog Issues
+
+* [#51 Proposal of IpFlowDescription to allow asymmetric QoS flows and (re)introduce protocol definitions](https://github.com/camaraproject/QualityOnDemand/issues/51)
+  - Stale issue
+  - Akos to check on status within DT and whether this is still required
+
+* [#147 Extend the query capabilities for Qos Profiles](https://github.com/camaraproject/QualityOnDemand/issues/147)
+  - No updates on this issue
+
+* [#45 Need to support ability to configure fallback qos](https://github.com/camaraproject/QualityOnDemand/issues/45)
+  - No requirement for this capability yet identified
+
+* [#166 Extend QoS Profile queries to list profiles based on specific users or devices](https://github.com/camaraproject/QualityOnDemand/issues/166)
+  - No update on this issue 
+
+* [#31 Ensure secure handling of callback URL](https://github.com/camaraproject/QualityOnDemand/issues/31)
+  - To be reviewed when new callback approach is adopted. To remain open for now.
+
+
+## API Roadmap
+
+### Release 0.10.0
+
+* Not discussed
+
+## AOB
+
+* The next call will be on Friday October 6th, 14:00 CEST / 13:00 BST / 12:00 UTC