Page History

...

• Summary of the open pull requests presented within issue #260 Proposal to create RC2 of v0.10.0
• The following PR were merged during the call:
  • #259 New example for DurationOutOfRangeForQoSProfile
  • #256 Added a note to maxDuration parameter within qosProfile about the limit of 86400 seconds
  • #252 feat: move "basePath" /qod/v0 to "url"-property
• PR #258 Added clarification of notifications to be sent and added StatusInfo "DELETE_REQUESTED" to address #241 was discussed but not merged:
  • The PR addressed two issues
    • #254 Send notifications for all qosStatus changes
    • #241 Extend the QoD API documentation with details as to what happens when qosStatus changes from available to unavailable
  • Open point is the period of time in
    "NOTE: in case of a `QOS_STATUS_CHANGED` event with `qosStatus` as `UNAVAILABLE` and `statusInfo` as `NETWORK_TERMINATED` the resources of the QoS session are not directly released, but will get deleted automatically only 360 seconds after the event"
  • With this formulation it is too restrictive for implementations.
  • Herbert stated that API consumers need a defined time period in case they want to poll to QoS session status instead of using notifications
  • Agreement: the statement should only define the time minimum period in which the QoS session resource is still available, but leave it up to implementations when the resources will be released after this period

• •  Herbert will update the PR and then ask for final reviews

...