DRAFT AGENDA
...
- PR #295 Add required security scheme and scopes by Eric Murray
- ...
- From last meeting:
- Eric will update the PR with documentation for the following points:
- Endpoints which have different behaviour with 2-legged vs 3-legged
- Endpoints which don't require 3-legged token (no user resource involved)
- The dependency of the Device object on the used authentication will be documented in a separate PR (after decision in Commonalities #171)
- Eric will update the PR with documentation for the following points:
- PR #306 Add HTTP-status-codes for better Error Handling
- PR for new issue #305
- Add additional HTTP status codes 405, 406, 429
- Supersedes also the (draft) PR #297 Add error 429 QUOTA_EXCEEDED?
- ...
- PR #299 New API QOD Provision
- ...
- From last meeting:
- Jose introduced the proposed API
- Eric: Does the API still allow to have multiple provisions per device? Or should it be restricted to one, and enhance the complete traffic of the device (would simplify the API a lot)
- Jose: all traffic is only one possible use case (hence 'applicationServer' is proposed to be optional)
- Open: Are there use cases to provision QoD for specific flows (defined by applicationServer)? - Jose will ask on product side
Closed issues
- #310 Remove terms of service and contact from APIs
- Done with PR #311
...
- #302 Providing developers with alternate to QoS profile
- new enhancement proposal by Mahesh Chapalamadugu
- discussion to be continued within the issue
Issues relevant for v0.11.0
...
- #302 Providing developers with alternate to QoS profile
- new enhancement proposal by Mahesh Chapalamadugu
- discussion to be continued within the issue
Any other topics
- Next QoD meeting will be on June 28th, at 14:00 CEST / 12:00 UTC
...